linux-kernel - RE: ARP Bug?

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>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0712191929430.12329@fbirervta.pbzchgretzou.qr>
Date:	Wed, 19 Dec 2007 19:30:05 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	"Peters, Gordon" <gordon.peters@...el.com>
cc:	"Gosney, JeremiX" <jeremix.gosney@...el.com>,
	linux-kernel@...r.kernel.org, "Sy, Dely L" <dely.l.sy@...el.com>
Subject: RE: ARP Bug?


On Dec 19 2007 09:47, Peters, Gordon wrote:

>Call me crazy,

For top-posting, yes. :)

> but if I have 2 NICs in a system and all the traffic is
>going through one of them and then that one NIC cable gets pulled, the
>other NIC, that half of the traffic should have been going through in
>the first place, should still work. However, with this type of
>functionality, it does not. Effectively both NICs are now dead even
>though the cable has only been pulled from eth0. Once you pull the cable
>to that "primary" NIC, all traffic stops; even when the "secondary" NIC
>is up and working fine. That in my professional opinion is broken.

I think you should finally reveal your interface configuration
otherwise it's all smoke and mirrors.
--
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/