Package: radvd Version: 1:1.6-1.1 I can confirm this behaviour. I have a similar setup with two interfaces on two different subnets. Assume eth0 (which is not connected but ifup'ed on boot) should announce subnetE and wlan0 subnetW.
On wlan0, both subnets are announced and accepted by a client. This unfortunately breaks IPv6 connectivity for the client on subnetE, because the address from subnetE takes precedence over the address from subnetW upon source address selection. However, the wlan0 interface has only an IPv6 address on subnetW and therefore the connection will timeout. My workaround: Instead of configuring the explicit prefix (e.g. 2001:db8::/64) in radvd.conf, I use the special prefix ::/64 (for both interfaces). With this setting, the behaviour is gone and the client receives only announcements for the proper subnet. Thanks for looking into this. Nicolas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
