| 2012-05-05 17:00:50 |
David |
bug |
|
|
added bug |
| 2012-05-06 19:26:56 |
Launchpad Janitor |
network-manager (Ubuntu): status |
New |
Confirmed |
|
| 2012-05-22 09:32:28 |
Georg Müller |
bug |
|
|
added subscriber Georg Müller |
| 2012-05-22 15:54:12 |
Carl Young |
bug |
|
|
added subscriber Carl Young |
| 2012-05-25 14:05:48 |
Carl Young |
bug |
|
|
added subscriber Mathieu Trudel-Lapierre |
| 2012-05-25 19:54:38 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu): importance |
Undecided |
High |
|
| 2012-05-25 19:54:40 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (mathieu-tl) |
|
| 2012-06-15 18:09:48 |
Mathieu Trudel-Lapierre |
nominated for series |
|
Ubuntu Precise |
|
| 2012-06-15 18:09:48 |
Mathieu Trudel-Lapierre |
bug task added |
|
network-manager (Ubuntu Precise) |
|
| 2012-06-15 18:09:58 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu Precise): status |
New |
Confirmed |
|
| 2012-06-15 18:10:01 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu Precise): importance |
Undecided |
High |
|
| 2012-06-15 18:10:05 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2012-06-15 18:10:08 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu Precise): assignee |
|
Mathieu Trudel-Lapierre (mathieu-tl) |
|
| 2012-10-10 21:27:37 |
Mathieu Trudel-Lapierre |
description |
To reproduce:
- Download ubuntu-12.04-alternate-amd64.iso, sha256sum: f8d54df0afbab6a6248f6e2bcab3e68f01c04d52b0bb1f889d880ad3bc881ccb
- Burn it to a USB flash drive from a completely up-to-date Ubuntu 10.04 LTS with UNetbootin
- Install on a machine with both IPv4 and IPv6 connectivity
- Log in to the newly installed system
Current behaviour:
- There is no IPv4 connectivity
- NetworkManager doesn't show the wired interface in its dropdown
Expected behaviour:
- There is IPv4 connectivity
- NetworkManager does show the wired interface in its dropdown
Thoughts:
I suspect this is because during the install my /etc/network/interfaces was created like so:
---BEGINS---
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto
---ENDS---
Then network-manager-0.9.4.0/debian/ifblacklist_migrate.sh mutates the file to comment out a single line like so:
#NetworkManager#iface eth0 inet dhcp
i.e. the line
iface eth0 inet6 auto
remains intact
This means that the /etc/network/interfaces file gives me IPv6 connectivity but not IPv4 connectivity. Furthermore, because there is an uncommented iface eth0 inet6 line, NetworkManager doesn't show me the interface in its dropdown.
To fix:
- The regular expression needs to be changed so that the iface eth0 inet6 auto line is also commented out |
[Impact]
IPv6 is becoming increasingly popular and installations on IPv6-ready networks are becoming more frequent; this issue affects installations of the Desktop image from the alternate image (or using d-i in any other way) when IPv6 autoconfiguration or DHCPv6 is used. These installations will fail to recognize that the interface should be managed by NetworkManager after the installation because only the "iface X inet dhcp" line would be commented out, leaving another valid "iface X" line for "inet6" causing NetworkManager to ignore the device. The solution was to comment out all lines in /etc/network/interfaces pertaining to interface X: "auto X", "iface X inet", and "iface X inet6".
[Test Case]
1a) With IPv6 autoconfiguration (for example, using radvd) or DHCPv6 available on the network:
1b) With no IPv6 available on the network:
2) Install Ubuntu from the alternate CD; or using d-i via a netboot image.
3) After the installation:
a) Verify that NetworkManager properly handles all interfaces.
b) Verify that the network interfaces configuration is commented out in /etc/network/interfaces.
[Regression Potential]
Untypical configurations may find devices that should be ignored by NetworkManager to be handled by it. Standard installations could fail to comment the necessary information from /etc/network/interfaces to allow for NetworkManager to do is job; or the file could be mangled to remove the "lo" interface, which would make unrelated services fail.
---
To reproduce:
- Download ubuntu-12.04-alternate-amd64.iso, sha256sum: f8d54df0afbab6a6248f6e2bcab3e68f01c04d52b0bb1f889d880ad3bc881ccb
- Burn it to a USB flash drive from a completely up-to-date Ubuntu 10.04 LTS with UNetbootin
- Install on a machine with both IPv4 and IPv6 connectivity
- Log in to the newly installed system
Current behaviour:
- There is no IPv4 connectivity
- NetworkManager doesn't show the wired interface in its dropdown
Expected behaviour:
- There is IPv4 connectivity
- NetworkManager does show the wired interface in its dropdown
Thoughts:
I suspect this is because during the install my /etc/network/interfaces was created like so:
---BEGINS---
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto
---ENDS---
Then network-manager-0.9.4.0/debian/ifblacklist_migrate.sh mutates the file to comment out a single line like so:
#NetworkManager#iface eth0 inet dhcp
i.e. the line
iface eth0 inet6 auto
remains intact
This means that the /etc/network/interfaces file gives me IPv6 connectivity but not IPv4 connectivity. Furthermore, because there is an uncommented iface eth0 inet6 line, NetworkManager doesn't show me the interface in its dropdown.
To fix:
- The regular expression needs to be changed so that the iface eth0 inet6 auto line is also commented out |
|
| 2012-10-10 21:31:12 |
Mathieu Trudel-Lapierre |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-10-16 22:43:27 |
Chris Halse Rogers |
network-manager (Ubuntu Precise): status |
Confirmed |
Fix Committed |
|
| 2012-10-16 22:43:30 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
| 2012-10-16 22:43:33 |
Chris Halse Rogers |
tags |
|
verification-needed |
|
| 2012-11-29 22:36:55 |
Adam Stokes |
bug |
|
|
added subscriber Adam Stokes |
| 2013-01-11 17:34:40 |
Mark Russell |
tags |
verification-needed |
verification-done |
|
| 2013-01-11 18:49:43 |
Mark Russell |
bug |
|
|
added subscriber Mark Russell |
| 2013-01-14 12:04:13 |
Colin Watson |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2013-01-14 12:05:14 |
Launchpad Janitor |
network-manager (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2013-05-06 20:30:57 |
Launchpad Janitor |
branch linked |
|
lp:~network-manager/network-manager/ubuntu.precise |
|
| 2013-11-06 03:24:37 |
Mathieu Trudel-Lapierre |
description |
[Impact]
IPv6 is becoming increasingly popular and installations on IPv6-ready networks are becoming more frequent; this issue affects installations of the Desktop image from the alternate image (or using d-i in any other way) when IPv6 autoconfiguration or DHCPv6 is used. These installations will fail to recognize that the interface should be managed by NetworkManager after the installation because only the "iface X inet dhcp" line would be commented out, leaving another valid "iface X" line for "inet6" causing NetworkManager to ignore the device. The solution was to comment out all lines in /etc/network/interfaces pertaining to interface X: "auto X", "iface X inet", and "iface X inet6".
[Test Case]
1a) With IPv6 autoconfiguration (for example, using radvd) or DHCPv6 available on the network:
1b) With no IPv6 available on the network:
2) Install Ubuntu from the alternate CD; or using d-i via a netboot image.
3) After the installation:
a) Verify that NetworkManager properly handles all interfaces.
b) Verify that the network interfaces configuration is commented out in /etc/network/interfaces.
[Regression Potential]
Untypical configurations may find devices that should be ignored by NetworkManager to be handled by it. Standard installations could fail to comment the necessary information from /etc/network/interfaces to allow for NetworkManager to do is job; or the file could be mangled to remove the "lo" interface, which would make unrelated services fail.
---
To reproduce:
- Download ubuntu-12.04-alternate-amd64.iso, sha256sum: f8d54df0afbab6a6248f6e2bcab3e68f01c04d52b0bb1f889d880ad3bc881ccb
- Burn it to a USB flash drive from a completely up-to-date Ubuntu 10.04 LTS with UNetbootin
- Install on a machine with both IPv4 and IPv6 connectivity
- Log in to the newly installed system
Current behaviour:
- There is no IPv4 connectivity
- NetworkManager doesn't show the wired interface in its dropdown
Expected behaviour:
- There is IPv4 connectivity
- NetworkManager does show the wired interface in its dropdown
Thoughts:
I suspect this is because during the install my /etc/network/interfaces was created like so:
---BEGINS---
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto
---ENDS---
Then network-manager-0.9.4.0/debian/ifblacklist_migrate.sh mutates the file to comment out a single line like so:
#NetworkManager#iface eth0 inet dhcp
i.e. the line
iface eth0 inet6 auto
remains intact
This means that the /etc/network/interfaces file gives me IPv6 connectivity but not IPv4 connectivity. Furthermore, because there is an uncommented iface eth0 inet6 line, NetworkManager doesn't show me the interface in its dropdown.
To fix:
- The regular expression needs to be changed so that the iface eth0 inet6 auto line is also commented out |
[Impact]
IPv6 is becoming increasingly popular and installations on IPv6-ready networks are becoming more frequent; this issue affects installations of the Desktop image from the alternate image (or using d-i in any other way) when IPv6 autoconfiguration or DHCPv6 is used. These installations will fail to recognize that the interface should be managed by NetworkManager after the installation because only the "iface X inet dhcp" line would be commented out, leaving another valid "iface X" line for "inet6" causing NetworkManager to ignore the device. The solution was to comment out all lines in /etc/network/interfaces pertaining to interface X: "auto X", "iface X inet", and "iface X inet6".
[Test Case]
1a) With IPv6 autoconfiguration (for example, using radvd) or DHCPv6 available on the network:
1b) With no IPv6 available on the network:
2) Install Ubuntu from the alternate CD; or using d-i via a netboot image.
3) After the installation:
a) Verify that NetworkManager properly handles all interfaces.
b) Verify that the network interfaces configuration is commented out in /etc/network/interfaces.
[Regression Potential]
Untypical configurations may find devices that should be ignored by NetworkManager to be handled by it. Standard installations could fail to comment the necessary information from /etc/network/interfaces to allow for NetworkManager to do is job; or the file could be mangled to remove the "lo" interface, which would make unrelated services fail.
---
To reproduce:
- Download ubuntu-12.04-alternate-amd64.iso
- Burn it to a USB flash drive from a completely up-to-date Ubuntu 10.04 LTS with UNetbootin
- Install on a machine with both IPv4 and IPv6 connectivity
- Log in to the newly installed system
Current behaviour:
- There is no IPv4 connectivity
- NetworkManager doesn't show the wired interface in its dropdown
Expected behaviour:
- There is IPv4 connectivity
- NetworkManager does show the wired interface in its dropdown
Thoughts:
I suspect this is because during the install my /etc/network/interfaces was created like so:
---BEGINS---
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto
---ENDS---
Then network-manager-0.9.4.0/debian/ifblacklist_migrate.sh mutates the file to comment out a single line like so:
#NetworkManager#iface eth0 inet dhcp
i.e. the line
iface eth0 inet6 auto
remains intact
This means that the /etc/network/interfaces file gives me IPv6 connectivity but not IPv4 connectivity. Furthermore, because there is an uncommented iface eth0 inet6 line, NetworkManager doesn't show me the interface in its dropdown.
To fix:
- The regular expression needs to be changed so that the iface eth0 inet6 auto line is also commented out |
|
