| 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
| ||
|
Message-ID: <F2B6B9EAC551DA4AA8833629D55D9CA8482D4C@orsmsx418.amr.corp.intel.com> Date: Fri, 14 Dec 2007 17:11:52 -0800 From: "Gosney, JeremiX" <jeremix.gosney@...el.com> To: <linux-kernel@...r.kernel.org> Cc: "Peters, Gordon" <gordon.peters@...el.com>, "Sy, Dely L" <dely.l.sy@...el.com> Subject: ARP Bug? 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? Jeremi M Gosney Enterprise Linux Engineer DIJIC, Intel Corporation Work: 253-371-4849 Mobile: 253-495-4254 -- 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