On Fri, Sep 02, 2016 at 02:25:42PM +0000, David Laight wrote: > From: Marcelo Ricardo Leitner > > Sent: 02 September 2016 14:47 > ... > > > Consider the following network: > > > > > > ----+---------------+----------------------+--------- > > > | | | > > > x.x.1.1 x.x.1.2 y.y.1.2 > > > 10.1.1.1 10.1.1.2 10.1.1.2 > > > | | | > > > ----+---------------+ +--------- > ... > > > I'm not at sure whether it is possible to setup listener(s) on x.x.1.1 > > > that can accept connections from both x.x.1.2 and y.y.1.2. > > > > You mean without an explicit bind()? > > You might be able to bind one socket to x.x.1.1 and a second to 10.1.1.1 > and x.x.1.1 so that connections to x.x.1.1 are only offered x.x.1.1 and > those to 10.1.1.1 are offered both addresses. > > But you can't make the init-ack responses for connections to x.x.1.1 > depend on whether the connect came from x.x.1.2 or y.y.1.2. > > If the source and destination ports are fixed (as they usually are for M3UA) > you can sit trying to make an outward connection, relying on the init > collision > code to work properly. Far from ideal!
Ahh yes, I see now. Yep.. Marcelo
