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: <200701262329.l0QNTo22025513@death.nxdomain.ibm.com>
Date:	Fri, 26 Jan 2007 15:29:49 -0800
From:	Jay Vosburgh <fubar@...ibm.com>
To:	"JUNG, Christian" <christian.jung@...rstahl.com>
cc:	"'netdev@...r.kernel.org'" <netdev@...r.kernel.org>
Subject: Re: bonding: bug in balance-alb mode (incorrect update-ARP-replie s) 

JUNG, Christian <christian.jung@...rstahl.com> wrote:

>> Jay Vosburgh <fubar@...ibm.com> wrote:
>> 
>> 	Is your test occuring on an isolated network, and is there other
>> concurrent network traffic that might be affecting things?
>
>The problem still persists as long as the box is connected to our Ciscos.
>
>I tried to simulate it with a dumb switch with my two boxes connected only.
>But there were no unsolicited ARP-replies anymore.

	I'm using Cisco switches as well.  I don't see the regular,
periodic ARP replies being generated as you describe, but I do see the
bonding driver issuing ARP replies for some or all of the elements of
the rx hashtable when certain events occur (slaves coming on/off line,
ARP requests coming from the local system, ).

>On the Ciscos I sometimes see ARP-replies with a destination MAC of
>00:00:00:00:00:00 (!) from some Linux-boxes which are using bonding.
>Currently I don't have a clue from where they're coming...

	I also saw one of those; I don't know where it came from,
either.

>The boxes are receiving around 200 ARP-replies a minute - so yes, there's
>concurrent network traffic :-)

	Well, I meant other traffic that causes the ARP replies to be
generated (i.e., concurrent traffic with the system).

	There are some other issues with the rx hashtbl that have come
up from my poking around, largely that it never, ever removes an entry
from the table.  After a sufficient number of different clients have
connected, the table will be filled with stale entries.  That's not
necessarily a problem in of itself, but it can lead to pathological
cases wherein regular ARP traffic induces update storms for peers that
are no longer interested.

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
-
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ