Package: bridge-utils
Version: 1.5-3
Followup-For: Bug #673490
I have another concern with bridge-network-interface. When I rebooted my
system today, suddenly name resolution didn't work. /etc/resolv.conf was
empty.
auto br0
iface br0 inet dhcp
up ip route add 172.16.2.0/24 via 172.16.1.208
down ip route del 172.16.2.0/24 via 172.16.1.208
dns-search lan.metrics.net dmz.metrics.net
bridge_ports lan
bridge_stp off
bridge_fd 2
bridge_maxwait 20
(More ports get added later for kvm vhosts)
I use resolvconf, which should have filled that stuff in. But the boot
order goes udev -> local fs -> resolvconf -> networking, and the
resolvconf init script clears all the resolvconf info. Shouldn't be a
problem, as resolvconf does this before interfaces are brought up.
Well, or at least it is supposed to be. But instead the udev rule
brought up the interface, way too early in the boot process.
I fixed it by changing '--allow auto' to '--allow hotplug' in
bridge-network-interface. (I have no idea how, or if, resolvconf works
with non-bridge hotplug interfaces...)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
