netdev - Re: bug in arp handling 2.6.20

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <46E0A683.4030902@hp.com>
Date:	Thu, 06 Sep 2007 18:16:51 -0700
From:	Rick Jones <rick.jones2@...com>
To:	Joseph Southwell <joseph@...oserve.com>
Cc:	netdev@...r.kernel.org
Subject: Re: bug in arp handling 2.6.20

Joseph Southwell wrote:
> scenario
> Machine A
> eth0 is plugged  into network.
> 192.168.1.201
> eth0:1
> 192.168.1.2
> 
> 
> Machine B
> eth1 is plugged into network.
> 192.168.1.101
> eth0 is not plugged into network. so I can test locally before  
> switching the wire.
> 192.168.1.201
> eth0:1
> 192.168.1.2
> 
> arp request for 192.168.1.2 is responded to by eth1 on machine B.  That 
> seems buggy to me. 

Does it still do so if you set either "arp_ignore" or "arp_filter" (I 
can never keep those two straight)?  Could be the "weak-end-system" 
design of the stack at work here.  That allows any interface in the 
system to respond to an ARP request for any of the IP's assigned to any 
of the interfaces.

> worse, it continues to do it after  unconfiguring 
> eth0:1 and eth0.

As in simply marking it "down?"

rick jones
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html