Ian,
: It doesn't work as given for connections that are port forwarded from
: the Linux router to machines inside the local network (e.g. to a web
: server).
True, the multiple uplinks is for exactly that, uplinks! Or, in other
words, outbound connectivity, only.
: With port forwarding in
Ian! D. Allen wrote:
I suspect the fix is somehow to mark the port forwarded packets with
a flag indicating on which interface they arrived at the Linux router,
and then preserve this flag into the answer packets on the web server.
On the Linux router I can then make sure that appropriately flagged
The fine document:
http://lartc.org/howto/lartc.rpdb.multiple-links.html
works nicely to make sure that answers to packets incoming to the
Linux router from a particular provider go back out again over the
same provider.
It doesn't work as given for connections that are port forwarded from the
The fine document:
http://lartc.org/howto/lartc.rpdb.multiple-links.html
works nicely to make sure that answers to packets incoming to the
Linux router from a particular provider go back out again over the
same provider.
It doesn't work as given for connections that are port forwarded from the
