Package: bridge-utils Version: 1.5-9 Severity: minor I'm seeing these messages when doing ifup on bridge device between two VLAN devices: WARNING: Could not open /proc/net/vlan/config. Maybe you need to load the 8021q module, or maybe you are not using PROCFS?? Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config WARNING: Could not open /proc/net/vlan/config. Maybe you need to load the 8021q module, or maybe you are not using PROCFS?? Added VLAN with VID == 1 to IF -:eth0:- WARNING: Could not open /proc/net/vlan/config. Maybe you need to load the 8021q module, or maybe you are not using PROCFS?? Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config WARNING: Could not open /proc/net/vlan/config. Maybe you need to load the 8021q module, or maybe you are not using PROCFS?? Added VLAN with VID == 2 to IF -:eth0:-
Waiting for br0 to get ready (MAXWAIT is 32 seconds). I also get the following messages when bringing the device down: WARNING: Could not open /proc/net/vlan/config. Maybe you need to load the 8021q module, or maybe you are not using PROCFS?? Removed VLAN -:eth0.1:- WARNING: Could not open /proc/net/vlan/config. Maybe you need to load the 8021q module, or maybe you are not using PROCFS?? Removed VLAN -:eth0.2:- There isn't a need to load a 802.1Q module, the support is built into this kernel. ifupdown itself deals with this setup just fine, it is only if I try using bridge-utils to handle the bridging that these messages show up. The good news is everything appears to work, so I'll rate this as minor. I'm not 100% certain this is due to bridge-utils, but bridge-utils looks like the obvious candidate right now. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
