Re: [reSIProcate] addTransport and interfaces with equal IP
Can you propose how you are going to change the interface on the list
before you go ahead and make the changes? Something to consider is how
to make this work on other operating systems such as win32. Backward
compatibility with the current interface would be nice as well.
Just so I understand the situation, you have multiple VPN interfaces
on the same box that are all bound to the same exact IP address?
Thanks
Jason
On 2/28/07, Fredrik Skoog <fs@xxxxxxxxxxx> wrote:
Ok, I need the functionality to bind to an interface, so I will try
to implement it. Do you see any problems doing it?
Best regards,
Fredrik
27 feb 2007 kl. 15.14 skrev Byron Campen:
> The name of the fifth parameter of SipStack::addTransport,
> ipInterface, is misleading. The function expects an IP-address
> there, and not an interface-name. I will put this on my list of
> things to fix.
>
> Best regards,
> Byron Campen
>
>> Hi!
>>
>> I'm building a system with a lot of VLAN-interfaces and most of the
>> interfaces have the same IP. When I'm doing addTransport I can
>> specify a interface-name, but it seems like it's binding to an IP
>> anyway. I was expecting a setsockopt-call with a SO_BINDTODEVICE-
>> parameter, but could not find it. Is it working anyway? or is it
>> something I have to implement? and do you see any problems
>> implementing it?
>>
>> Best regards,
>>
>> Fredrik
>>
>>
>> _______________________________________________
>> resiprocate-devel mailing list
>> resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
>> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel