Thanks for taking the time to respond to my email. I would have solved this
issue had I had direct internet connection. Unfortunately for me the only
connections I have had access to lately is wifi via coffee houses! I plan
to get with a direct connection so that I could access to updates! If I
** Description changed:
[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
Read your post but I can't find Download ubuntu-12.04-alternate-amd64.iso,
sha256sum: f8d54df0afbab6a6248f6e2bcab3e68f01c04d52b0bb1f889d880ad3bc881ccb
there are other .iso's websites i.e
http://nl.releases.ubuntu.com/precise/
The issue seems to be md5sum failure or sha256sum failure to match.
Thanks all for completing the testing on this bug so that this and other
fixes could be released. I appreciate it as this was the last bug that
required testing before the most recent proposed change could be
released.
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package network-manager - 0.9.4.0-0ubuntu4.2
---
network-manager (0.9.4.0-0ubuntu4.2) precise-proposed; urgency=low
* debian/patches/git_use_wpa_wext_methods_50435e1.patch: use the same kind
of logic as wpasupplicant instead of just looking at whether
I've verified the fix in proposed using the precise mini.iso. With IPv6
enabled on the router, I was able to duplicate the issue. Reinstalling
with proposed enabled in the kernel command-line worked as expected
(with IPv4 connectivity).
** Tags removed: verification-needed
** Tags added:
You don't need to apply anything; you can test this by simply running an
install (provided you have IPv6 connectivity when you do so; reproducing
the actual bug), and enabling proposed for the install: see
https://wiki.ubuntu.com/Testing/EnableProposed (the section
Installation testing with
For the curious; that's just by adding the apt-setup/proposed=true
boot parameter as you boot from an alternate CD -- you don't need to
download any special installer image (you don't need the first link in
the wiki page mentioned above).
--
You received this bug notification because you are a
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
Is there anyone who can test this so that the fix can be released for
this and the other three bugs? I would test this if I could. Any help
from anyone would be greatly appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have a Precise installation in a IPv6 network, but it works properly.
How can I test the fix? By adding the line iface eth0 inet6 auto?
--
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:
Nope, I'm unable to reproduce the problem by adding iface eth0 inet6
auto and iface eth0 inet dhcp and running restart networking. I have
not enabled proposed updates. Are there any other steps in the
reproduction? I'm not sure that this machine has used the alternate
installation, and it has been
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
Mathieu, How can this be tested so that the other chages tied to the
same fix can be released? I've been waiting on the fix to bug #1035590,
which 0.9.4.0-0ubuntu4.2 has been confirmed to resolve. But the package
is being held up it seems because no testing has been completed for this
bug. I don't
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 Ubuntu
Carl, David,
Are you able to test this? Enabling proposed for the install might be a
little tricky, but you can look at
https://wiki.ubuntu.com/Testing/EnableProposed (the section
Installation testing with -proposed) to know how to run the tests and
get the updated network-manager package.
--
Hello David, or anyone else affected,
Accepted network-manager into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/network-
manager/0.9.4.0-0ubuntu4.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Description changed:
+ [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
Not needed, there's a new ifblacklist_migrate.sh available in the
quantal package already; I'll just need to fix it up for a Precise SRU.
** Also affects: network-manager (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu Precise)
Status:
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
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
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
Nice catch, that's indeed a wrong assumption on the part of the
ifblacklist_migrate.sh script -- I'll look at fixing this ASAP; but
anyone wanting to take a stab and that funky sed line in
ifblacklist_migrate.sh is welcome to do so ;)
** Changed in: network-manager (Ubuntu)
Importance:
I think this is not a bug of network-manager but of the installer who
creates /etc/network/interfaces ...
This line should not be created in the first place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995165
I had the same problem and simply commenting the line
iface eth0 inet6 auto
resolved the problem.
--
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
27 matches
Mail list logo
