*** This bug is a duplicate of bug 353835 ***
https://bugs.launchpad.net/bugs/353835
> You just configure the vlan in /etc/network/interfaces like:
> iface eth0.1 inet dhcp
>
> When you then enter 'ifup eth0.1', the system configures eth0
> and then sets on top the virtual interface eth0.1
> Afterwards it starts the dhclient on the virtual interface.
It's /etc/network/if-pre-up.d/vlan that does all this. It takes
'eth0.1' and extracts 'eth0' as the raw device name.
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/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"`
Then it ups eth0 and creates eth0.1.
ip link set up dev $IF_VLAN_RAW_DEVICE
vconfig add $IF_VLAN_RAW_DEVICE $VLANID
Then ifup runs dhclient for eth0.1.
This sort of trickery works with ifupdown but it doesn't surprise me
that it confuses NetworkManager.
This person gives instructions for creating ethX.Y on the command line
and then letting NM configure it:
http://ubuntuforums.org/showthread.php?t=703387
Someone reported a similar issue at superuser.com:
http://superuser.com/questions/287443/ubuntu-network-manager-and-
vlan
And finally, an earlier Launchpad bug report, bug #353835, with which
I've merged this report. :)
** This bug has been marked a duplicate of bug 353835
NetworkManager lacks 802.1Q/VLAN tagging support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029273
Title:
NetworkManager tries to configure eth0 instead of eth0.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1029273/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
