Re: Renamed interfaces / VLANs brokenness

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 15, 2004 at 09:34:04AM -0800, Simon Kirby wrote:

> Contents of /proc/net/vlan/config:
> 
> VLAN Dev name    | VLAN ID
> Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
> eth4.99        | 99  | eth4
> eth1.139       | 139  | eth4
>...
> eth1.139       | 139  | eth1

Ok, I tracked this down to a little pebcak and a little VLAN issue.
I had done the interface rename without rebooting and accidentally missed
the removal of the 139 VLAN from the old eth1 before renaming it to eth4. 
This caused the master to change names to eth4, but the VLAN name was
still eth1.139.

A bug in the VLAN code then allowed a second "eth1.139" to be created
which resulted in the above confusion.  (This is a bug because there
should never be two devices with the same name, and so "eth1.139" could
only be removed once.)

Simon-
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux