netdev - Re: Bonding and Neighbour Discovery on IPv6-only devices

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

Message-ID: <20080915180015.GB1078@havoc.gtf.org>
Date:	Mon, 15 Sep 2008 14:00:15 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Alex Sidorenko <asid@...com>
Cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Bonding and Neighbour Discovery on IPv6-only devices

On Mon, Sep 15, 2008 at 01:35:16PM -0400, Alex Sidorenko wrote:
> Hello,
> 
> I suspect that there are some problems while switching slaves manually on 
> IPv6-only bonds. I have tested that this does not work on 2.6.18 kernel 
> (RHEL5). I looked at recent sources (2.6.26) and even though there were 
> multiple changes in bonding code, I still don't see how this could work.
> 
> Testing setup
> -------------
> 
> Two ethernets enslaved (eth2 and eh3), active-backup bond has IPv6-only 
> address (no IPv4)
> 
> Everything works fine, but if we switch the slave doing
> 
> # ifenslave -c bond0 eth3
> 
> the incoming ping6 to this host stops for up to several minutes (waiting until 
> the switch updates its caches).

We _just_ put in an IPv6 fix, FWIW...

	Jeff



--
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