Package: vde2 Version: 2.2.2-3 Severity: normal On this system, I noticed that a vde interface fails to come up at boot, but ifup/ifdown by hand works when the system is running.
I found that this is a timing issue. ifup starts the switch process, then fires off an ifconfig, but occasionally the tap interface has not been created yet at that point and ifconfig fails. Afterwards, the tap is created, so you end up with a switch process running and an unconfigured interface. On my system, I choose the dirty fix of putting a "sleep 2" after start-stop-daemon in the vde2 script. The clean solution would be to have vde_switch not background itself until the tap interface exists. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (600, 'stable'), (400, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-bpo.2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages vde2 depends on: ii adduser 3.110 add and remove users and groups ii libc6 2.7-18lenny2 GNU C Library: Shared libraries ii libpcap0.8 0.9.8-5 system interface for user-level pa ii libvdemgmt0 2.2.2-3 Virtual Distributed Ethernet - Man ii libvdeplug2 2.2.2-3 Virtual Distributed Ethernet - Plu vde2 recommends no packages. Versions of packages vde2 suggests: pn kvm <none> (no description available) pn qemu <none> (no description available) pn vde2-cryptcab <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
