The idea is to make it transparent. You could make much the same argument
for why you don't need an ethernet bridge...
Having to setup multiple routes is very kludgy I think even on the server
side. Having multiple IP's for the server is also messy because the
clients then have to know which one to connect to.
It strikes me the cleanest way to do it is to just fix the way arp is
handled so that it remembers what interface the arp request came on and
sends out the arp reply on the same one. As for asking for arp's, either
send them on all interfaces, or send them on just one and assume the
switch will send it to the rest.
-Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu