Public bug reported:
System Ubuntu 12.04 LTS (precise), network-manager 0.9.4.0-0ubuntu4.1
I have the following configuration in /etc/network/interfaces:
auto lo
iface lo inet loopback
# The primary network interface
#auto eth0
auto eth0.1
The nm-applet shows this connection as "ifupdown(eth0.1)" correctly,
although this can of course not be edited.
However, when activating this connection, network-manager activates eth0
instead of eth0.1, which of course does not work. Here is the relevant
syslog:
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0)
starting connection 'Ifupdown (eth0.1)'
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> (eth0): device state
change: disconnected -> prepare (reason 'none') [30 40 0]
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0) Stage
1 of 5 (Device Prepare) scheduled...
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0) Stage
1 of 5 (Device Prepare) started...
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0) Stage
2 of 5 (Device Configure) scheduled...
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0) Stage
1 of 5 (Device Prepare) complete.
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0) Stage
2 of 5 (Device Configure) starting...
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> (eth0): device state
change: prepare -> config (reason 'none') [40 50 0]
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0) Stage
2 of 5 (Device Configure) successful.
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0) Stage
3 of 5 (IP Configure Start) scheduled.
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0) Stage
2 of 5 (Device Configure) complete.
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0) Stage
3 of 5 (IP Configure Start) started...
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> (eth0): device state
change: config -> ip-config (reason 'none') [50 70 0]
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0)
Beginning DHCPv4 transaction (timeout in 45 seconds)
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> dhclient started with
pid 4487
Jul 26 08:11:48 LaptopMB NetworkManager[32517]: <info> Activation (eth0)
Beginning IP6 addrconf.
[...]
Jul 26 08:11:50 LaptopMB NetworkManager[32517]: <info> Policy set 'Ifupdown
(eth0.1)' (eth0) as default for IPv4 routing and DNS.
Jul 26 08:11:50 LaptopMB NetworkManager[32517]: <info> Activation (eth0)
successful, device activated.
Jul 26 08:11:50 LaptopMB NetworkManager[32517]: <info> Activation (eth0) Stage
5 of 5 (IPv4 Commit) complete.
As you can see, it is really not activating eth0.1 as written in
/etc/nbetwork/interfaces but eth0, although network manager 0.9.4 should have
support for vlan configurations.
If I am doing something wrong, please tell me what and how it should be
done instead.
Thank you very much.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: vlan
--
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:
Network manager doesn't read /etc/network/interfaces correctly
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
