Re: [reSIProcate] addTransport and interfaces with equal IP

[Byron Campen <bcampen@xxxxxxxxxxxx>]

	How should this impact how tcp connections are formed if the tcp  
listen port is bound in this way? Wouldn't we need to bind the  
connection sockets to the same interface (at least, to have  
everything function as expected)? This would require keeping some new  
state around, I think.

Best regards,
Byron Campen

> 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

Attachment: smime.p7s
Description: S/MIME cryptographic signature