[Desktop-packages] [Bug 995165] Re: IPv4 connectivity broken after installing from ubuntu-12.04-alternate-amd64.iso
Hi Mathieu, I have been moved into a different development group, so I don't have the facility to try this any more. I have asked my guys in Hyderabad if they can try this as they now own the lab environment. Regards, Carl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/995165 Title: IPv4 connectivity broken after installing from ubuntu-12.04-alternate- amd64.iso Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Precise: Fix Committed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/995165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995165] Re: IPv4 connectivity broken after installing from ubuntu-12.04-alternate-amd64.iso
Hi. Sorry I haven't been able to get anyone to retry at my site, but they are in final sprints of product release. In my scenario, where I saw the failures, there would have been existing Windows-based machines with auto-assigned (link-local) IPv6 addresses but no 'real' IPv6 infrastructure. If someone can given the manual steps to try verifiying the fix, they have given me access to their test environment. As I'm not really an Ubuntu expert (sorry), I would appreciate the steps required to test the fix including how I would patch, etc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/995165 Title: IPv4 connectivity broken after installing from ubuntu-12.04-alternate- amd64.iso Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Precise: Fix Committed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/995165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995165] Re: IPv4 connectivity broken after installing from ubuntu-12.04-alternate-amd64.iso
I previously said: "If someone can given the manual steps to try verifiying the fix, they have given me access to their test environment. As I'm not really an Ubuntu expert (sorry), I would appreciate the steps required to test the fix including how I would patch, etc." If someone can tell me where to get the binaries and how to apply them to asn appropriate ISO or mirror, I can get access to the emvironment to test this behaviour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/995165 Title: IPv4 connectivity broken after installing from ubuntu-12.04-alternate- amd64.iso Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Precise: Fix Committed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/995165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995165] Re: IPv4 connectivity broken after installing from ubuntu-12.04-alternate-amd64.iso
I have also seen this in 12.04 LTS AMD 64. In my failing environment, interface->dhcp is 1; interface->slaac is 1, and interface->dhcp6 is 0. The install syslog shows: Network config complete Writing informative header Success! Writing loopback interface Success! Writing DHCP stanza for eth0 Writing SLAAC stanza for eth0 Success! /etc/network/interfaces shows as follows (sans some comments at top) = START = # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 #NetworkManager#iface eth0 inet dhcp # This is an autoconfigured IPv6 interface iface eth0 inet6 auto = END = If I comment out the #NetworkManager# comment, then my network is fine - ifconfig shows IPv4 and IPv6 addresses, but the Network manager reports unmanaged. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/995165 Title: IPv4 connectivity broken after installing from ubuntu-12.04-alternate- amd64.iso Status in “network-manager” package in Ubuntu: Confirmed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/995165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995165] Re: IPv4 connectivity broken after installing from ubuntu-12.04-alternate-amd64.iso
This bug seems releated to 948217 and several others. In my case, during a netboot install I have an IPv4 DHCP assigned address and IPv6 global addresses assigned by SLAAC. This then ends up with two iface entries in /e/n/interfaces: iface eth0 inet dhcp iface eth0 inet6 auto The ifblacklist_migrate.sh script locates and disables the first entry, but not the second (and I don't think it has a way of knowing this is SLAAC so can't disable it?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/995165 Title: IPv4 connectivity broken after installing from ubuntu-12.04-alternate- amd64.iso Status in “network-manager” package in Ubuntu: Confirmed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/995165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995165] Re: IPv4 connectivity broken after installing from ubuntu-12.04-alternate-amd64.iso
Precise Alternate CD comes with netcfg 1.68 (netcfg_1.68ubuntu14_amd64.udeb) and this version of netcfg writes out two iface entries for eth0 when it has dhcp/dhcp6 assigned or SLAAC assigned global IPv6 addresses (write_interface.c). The ifblacklist_migrate.sh only disables the first entry because of the dhcp tag, and doesn't disable the second, so we end up with an unmanaged NIC according to NetworkManager and no IPv4 address. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/995165 Title: IPv4 connectivity broken after installing from ubuntu-12.04-alternate- amd64.iso Status in “network-manager” package in Ubuntu: Confirmed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/995165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995165] Re: IPv4 connectivity broken after installing from ubuntu-12.04-alternate-amd64.iso
I checked out the sed line and I think I've just about got over the trauma now... >From my 'newb' PoV, I would also be looking at netcfg and why there is no distinction between link-local auto-assigned IPv6 addresses and SLAAC auto-assigned global IPv6 addresses and how NetworkManager handles IPv6. Where I have an installation that is NetworkManager managed - it has a commented out "iface eth0 inet dhcp" entry but no IPv6 entry at all, ifconfig still shows that I have an IPv6 link-local (fe80::/64) address. I guess this is because the IPv6 support is built into the kernel itself? Can something (a keyword?) be introduced into the inet ipv6 stanza to distinguish the address classes to assist ifblacklist_migrate.sh? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/995165 Title: IPv4 connectivity broken after installing from ubuntu-12.04-alternate- amd64.iso Status in “network-manager” package in Ubuntu: Confirmed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/995165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
