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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995165 Title: IPv4 connectivity broken after installing from ubuntu-12.04-alternate- amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/995165/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
