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
| ||
|
Date: Tue, 12 Jul 2011 18:36:02 +0200 From: David Lamparter <equinox@...c24.net> To: Tomasz Chmielewski <mangoo@...g.org> Cc: David Lamparter <equinox@...c24.net>, netdev@...r.kernel.org Subject: Re: bonding and IPv6 "doesn't work"? On Tue, Jul 12, 2011 at 06:25:16PM +0200, Tomasz Chmielewski wrote: > It's a virtual machine. > So, a bridge of the host. Just a bridge? No bonding device? You need to set it up on both sides... > >> bond0: IPv6 duplicate address 2a01:4f8:120:14c4::1247 detected! > > [...] > >> However if I start bonding with just one interface, add IPv6 address to > >> it, then use ifenslave to add a second interface, I'm able to reach the > >> hosts in the internet. > > > > Yeah, when you add the IPv6 address, IPv6 ND does its job and announces > > your presence/does DAD. > > Shouldn't this disable DAD? Or am I confusing something here? > > net.ipv6.conf.eth0.accept_dad = 0 > net.ipv6.conf.eth1.accept_dad = 0 Yes, you would need to set net.ipv6.conf.bond0.accept_dad = 0 because eth0 and eth1 are not actually participating in the IPv6 stack. (I'd recommend setting disable_ipv6=1 for them too) However, you should not be getting that DAD error at all, it indicates that broadcast/multicast packets that go out on eth0 are looped back on eth1 (and vice versa). Your bonding setups on the host and the VM don't seem to match each other. -David -- 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