Package: vlan Version: 1.9-3.2 Severity: important Tags: patch Dear Maintainer,
* What led up to the situation? I configured an interface named 'vlan25' instead of 'vlan025' to use a local network with an 802.1Q vlan ID==25. * What exactly did you do (or not do) that was effective (or ineffective)? ifup vlan25 failed. * What was the outcome of this action? The vconfig command failed because the id was 'vlan25' instead of '25'
diff -u vlan-1.9/debian/changelog vlan-1.9/debian/changelog --- vlan-1.9/debian/changelog +++ vlan-1.9/debian/changelog @@ -1,6 +1,14 @@ -vlan (1.9-3.2) unstable; urgency=medium +vlan (1.9-3.3) unstable; urgency=medium * Non-maintainer upload. + * debian/network/if-pre-up.d/vlan: fix type-o in script that seds + "vlan0" out when "vlan" was the string matched. This prevented + using an interface name of 'vlan25' properly. + + -- Clint Byrum <spam...@debian.org> Fri, 10 Jul 2015 11:04:06 -0700 + +vlan (1.9-3.2) unstable; urgency=medium + * Don't exit when we're called by bridge-utils. -- Andrew Shadura <andre...@debian.org> Tue, 01 Apr 2014 09:42:56 +0200 diff -u vlan-1.9/debian/network/if-pre-up.d/vlan vlan-1.9/debian/network/if-pre-up.d/vlan --- vlan-1.9/debian/network/if-pre-up.d/vlan +++ vlan-1.9/debian/network/if-pre-up.d/vlan @@ -13,7 +13,7 @@ ;; vlan*) vconfig set_name_type VLAN_PLUS_VID_NO_PAD - VLANID=`echo $IFACE|sed "s/vlan0*//"` + VLANID=`echo $IFACE|sed "s/vlan*//"` ;; eth*.0*|bond*.0*|wlan*.0*) # Silently ignore interfaces which ifupdown handles on its own