Hi,

I just ran into this, and fixed it as follows:

## begin patch
--- /etc/network/if-pre-up.d/.vlan.dist 2014-04-01 09:32:05.000000000 +0000
+++ /etc/network/if-pre-up.d/vlan 2016-04-17 22:26:55.956729712 +0000
@@ -7,6 +7,10 @@
   *:*)
     exit 0
   ;;
+  vlan0)
+    vconfig set_name_type VLAN_PLUS_VID_NO_PAD
+    VLANID=0
+  ;;
   vlan0*)
     vconfig set_name_type VLAN_PLUS_VID
     VLANID=`echo $IFACE|sed "s/vlan0*//"`
@@ -31,6 +35,12 @@
     VLANID=`echo $IFACE|sed
"s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g"`
     IF_VLAN_RAW_DEVICE=`echo $IFACE|sed
"s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/"`
   ;;
+  *.0)
+    # Silently ignore interfaces which we do not (know how to) support
+    [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0
+    vconfig set_name_type DEV_PLUS_VID_NO_PAD
+    VLANID=0
+  ;;
   *.0*)
     # Silently ignore interfaces which we do not (know how to) support
     [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0

## end patch

I was trying to bring up vlan0, and the scripts kept using the name
vlan0000 causing it to fail.

I realize that vlan 0 is not technically a VLAN, but that's no reason not
to support this usage (and yes, for my usage, it's actually *required* that
I use 0).

Can we please get this fixed, since the changes required are trivial?

-- 
Ryan Castellucci https://rya.nc/

Reply via email to