netdev
[Top] [All Lists]

RE: [2.4 PATCH] bugfix: ARP respond on all devices

To: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [2.4 PATCH] bugfix: ARP respond on all devices
From: Daniel Gryniewicz <dang@xxxxxxxxxxx>
Date: 19 Aug 2003 14:30:26 -0400
Cc: Richard Underwood <richard@xxxxxxxxxxxxxxxxx>, "'David S. Miller'" <davem@xxxxxxxxxx>, Stephan von Krawczynski <skraw@xxxxxxxxxx>, willy@xxxxxxxxx, carlosev@xxxxxxxxxxxx, lamont@xxxxxxxxxxxxxxxx, davidsen@xxxxxxx, bloemsaa@xxxxxxxxx, Marcelo Tosatti <marcelo@xxxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, layes@xxxxxxxxx, torvalds@xxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <1061296544.30566.8.camel@dhcp23.swansea.linux.org.uk>
References: <353568DCBAE06148B70767C1B1A93E625EAB57@post.pc.aspectgroup.co.uk> <1061296544.30566.8.camel@dhcp23.swansea.linux.org.uk>
Sender: netdev-bounce@xxxxxxxxxxx
On Tue, 2003-08-19 at 08:35, Alan Cox wrote:
> You increase it and you shortcut on shared lans. Thats really a seperate
> issue to the question of which source is used. If you loopback someone
> elses address on your own lo device I'm not suprised weird shit happens,
> put the alias on eth0 where it belongs.

Only if you are on a shared lan.  If you are not on a shared lan, then
it will *ONLY* work if linux is on the other end.  No other system will
work.  And, you don't need an alias on loopback.  Merely changing the
default route will result in this.  Change default route from gw 1.1.1.1
on eth0 to gw 2.2.2.2 on eth1 (making sure that 2.2.2.2 doesn't have an
arp entry), and linux will say, on eth1:
whohas 2.2.2.2 tell 1.1.1.2
where 1.1.1.2 is the address on eth0.  No one will respond to this, so
all communication from beyond a directly connected network will now
fail.

-- 
Daniel Gryniewicz <dang@xxxxxxxxxxx>

<Prev in Thread] Current Thread [Next in Thread>