Hi, On Mon, Mar 24, 2014 at 11:34:47PM +0100, Michael Rasmussen wrote: > After the patch has been applied fixing bug #705456 breaks configuration > which worked and was perfectly correct before. Applying a patch to fix a > problem should never cause valid uses of the package before suddenly > stop working. Yes, I am sorry,
I got new packages to be uploade since 5 years or so, but my sponsor got scared. This one has been NMU'd. > > Prior to vlan version 1.9-3.1 the following config worked as intended: > # The vlan carrying interface > auto eth1 > iface eth1 inet manual > > auto vmbr20 > iface vmbr20 inet static > address 172.16.2.60 > netmask 255.255.255.0 > bridge_ports eth1.20 > bridge_stp off > bridge_fd 0 > bridge_maxwait 5 Hmmm, actually I am a little bit surprised that the mere mentioning of eth1.20 in the bridge configuration automagically creates eth1.20. I would suspect that the first 2 lines should be: auto eth1.20 iface eth1.20 inet manual As that would create an eth1.20 in the up state. Actually, that's how I do it ;-). On the other hand, the bridges should either not get created at all, or created without ports, or somewhere in between. If it attaches eth1 instead of nothing at all, that would be a grave bug. Regards, Ard -- .signature not found -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
