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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4769844F.4030902@redhat.com>
Date:	Wed, 19 Dec 2007 15:51:27 -0500
From:	Chuck Ebbert <cebbert@...hat.com>
To:	"Gosney, JeremiX" <jeremix.gosney@...el.com>
CC:	linux-kernel@...r.kernel.org,
	"Peters, Gordon" <gordon.peters@...el.com>,
	"Sy, Dely L" <dely.l.sy@...el.com>
Subject: Re: ARP Bug?

On 12/14/2007 08:11 PM, Gosney, JeremiX wrote:
> We've noticed the 2.6-based Linux systems in our test lab are
> experiencing some "ARP flux"-like symptoms.  
> 
> The systems reply with eth0's hardware address to all ARP requests,
> regardless of the IP being queried.  Because of this, the system will
> only send and receive packets on eth0; if eth0 is brought down, the
> system is unreachable even though it still has several active
> connections.  With eth0 unplugged, none of the other interfaces are
> reachable (this is presumably a side-effect caused by the switch ARP
> cache.) Failover routes are defined in the routing table, but the system
> still will not send/receive packets out those interfaces.
> 
> Can anything be done to correct this behaviour?
> 
> 

Offtopic here, but anyway look at http://linux-ip.net/html/ch-ether.html

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ