Am Montag, 14. Januar 2002 02:07 schrieb David S. Miller: > From: Gregor Jasny <gjasny@wh8.tu-dresden.de> > Date: Mon, 14 Jan 2002 01:42:04 +0100 > > Is there a patch to correct this 'misbehaviour' ? > > Use source based routes on the Linux machine so that you're telling it > exactly what you want. > With the current setup: ./ip route 141.30.225.0/24 dev eth2 proto kernel scope link src 141.30.225.254 141.30.221.0/24 dev br0 proto kernel scope link src 141.30.221.2 127.0.0.0/8 dev lo scope link default via 141.30.225.1 dev eth2 Whats wrong with this config? The majority of the arp requests is fine: 03:08:07.626268 arp who-has 141.30.225.1 tell 141.30.225.254 03:08:07.626712 arp reply 141.30.225.1 is-at 0:60:5c:5e:82:d1 just some show this behaviour. Does it make a difference if I've set up with the old (ifconfig, route) tools? BTW: The route for eth2 was set up by ifconfig. - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
