Package: radvd Severity: wishlist Tags: ipv6 upstream Hi,
currently, radvd fails if it is started for an interface that is not yet present or not yet up. This leads to network failures if radvd is started on an interface that appears dynamically, such as VLAN interface or a bridge. In the bridge case, kernel behavior was recently changed that brX only changes to the UP state when the first interface is added to the bridge. The kernel developers think that it is a good idea to mimic a phyiscal interface in that regard. In the very common virtualization case, this means that the bridge won't be in an UP state until the first VM is booted and attaches itself to the network. This behavior has been verified for both Virtualbox and KVM setups. On the netdev mailing list, I received the answer that the kernel's new behavior is fine and that the applications should hang around and wait for the interface to become usable. So we need to change the applications. Greetings Marc -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.4-zgws1 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
