Marking as Fix Released due to the reports above and because there's
been major work on IPv6 in Natty and even more on Oneiric (the current
development release as of this writing).
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notifica
I had this problem as well and just updated to Ubuntu 10.10 (Maverick),
as of today, I have it fully updated. As far as I can tell, the problem
with autoconfiguring IPv6 address is gone. Yahoo! However, when I
disconnect from my wired network (unplug the cable), the IPv6 address /
route still persi
I've been able to work around this in Lucid by setting IPv6 to "Link-
Local Only" for networks that don't have an IPv6 configuration Network
Manager likes.
--
IPv6=automatic breaks IPv4
https://bugs.launchpad.net/bugs/284874
You received this bug notification because you are a member of Ubuntu
Bu
The intended behavior is, AFAIK as written on the label; if the tooltip
is contradicting then it is indeed a bug; note that what you're
describing sounds like a bug as well (checking/unchecking with automatic
or without not yielding consitent results). Could you open separate bug
reports about thes
Thanks Vernon. That's good to know, I'll so some testing later.
Possibly a seperate bug, however. I couldn't help noticing on the
screen-shot that the tickbox labels contradict the popup-help label.
E.G:
for IP6:
Tickbox Label reads "Require IPv6 addressing for this connection to
complete" - E.G
I just booted the 23 Sep 2010 daily Maverick build and thoroughly tested
the network manager. By default, the settings don't match the dialog,
but after changing the settings, all works well. What I mean by this is
that by default, the IPv6 setting is to ignore. But it doesn't ignore
(I got an a
Could someone please test this in Maverick or confirm that the bug is
still present? There were some changes made to the way IPv6 is handled
upstream, but also requiring ISC-DHCPv4, which we don't have yet... but
would be a clear plan for Natty.
It's very likely that with the correct settings in M
people reading this bug should also see
https://bugzilla.redhat.com/show_bug.cgi?id=538499
** Bug watch added: Red Hat Bugzilla #538499
https://bugzilla.redhat.com/show_bug.cgi?id=538499
--
IPv6=automatic breaks IPv4
https://bugs.launchpad.net/bugs/284874
You received this bug notification be
An update. This should be used instead:
echo 1 > /proc/sys/net/ipv6/conf/DEV/disable_ipv6
echo 0 > /proc/sys/net/ipv6/conf/DEV/disable_ipv6
This seems to work if NM's ipv6 setting is "ignore", but if it is set to
"Link-local", then NM appears to somehow block the new address. I
glanced briefly at
I've just found that my suggestion in #20 this does not actually work in
general.
It should be easiest to set with some echoing into /proc/sys/net/ipv6/conf/DEV/*
However, I have two machines that I want to listen to radvd. They have
the same entries in that /proc/sys directory, but have differe
I think Abraham's work-around might be the best I have seen yet, but
still, 'Automatic' should really be 'use it if it is there, DON'T FAIL
if it is not there.' The hack that I have been using is to go into the
network manager's 'Edit Connections' dialog and under the 'Wired' tab,
click on 'Add' t
This might be a workaround:
Set NM IPv6 to "Ignore".
After IPv4 is up (so in an if-up.d script, if you like), issue
ip -6 link set DEV down
ip -6 link set DEV up
where DEV is eth0 or wlan0 or whatever.
This will not take down the IPv4 network, but will put the IPv6 stack for that
device back into
Also FWIW, I don't see any local v6 packets being generated when using
wireshark. I see the RA and EIGRP's from the IOS Switch, but that's it.
Mike
--
IPv6=automatic breaks IPv4
https://bugs.launchpad.net/bugs/284874
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I'm still a bit rough with IPv6, but configuring a manual v6 prefix
allows dual stack and link-local networks (I didn't config a v6
static/default). Seems to be an autoconfig issue and or stateless
config issue. Has anyone tried Stateful autoconfiguration (aka DHCP)???
I thought I tried it, but w
I jumped to conclusion too fast. The bug is still there, automatic
configuration just works sometimes.
--
IPv6=automatic breaks IPv4
https://bugs.launchpad.net/bugs/284874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
After recent updates the problems seem to have gone away. I don't know
which update did it but it wasn't networking-manager.
--
IPv6=automatic breaks IPv4
https://bugs.launchpad.net/bugs/284874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
"Automatic, addresses only" setting yields the same result, no
connection.
--
IPv6=automatic breaks IPv4
https://bugs.launchpad.net/bugs/284874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I have the same problem -- cannot connect to the network with radvd and
IPv6 configuration in network-manager set to automatic. It's not just
IPv6, network-manager fails to connect at all overy any protocol when
IPv6 configuration is set to automatic. For a while restarting network-
manager (servic
I noticed on a newly installed Lucid box that this was still the case.
Exacerbating the problem for me was that I enabled ufw, but forgot to
set 'IPV6=yes' in /etc/default/ufw. This blocked any ipv6 config
packets and thus caused the failure of any ipv6 configuration. The
default ipv6 firewall is
Confirmed on current lucid as well.
If the router advertisement fails for some reason, configuration of the
network just fails even if an ipv4 via dhcp is assigned:
Apr 19 14:59:37 faui44a NetworkManager: Activation (eth0) Stage 4 of 5
(IP4 Configure Get) complete.
Apr 19 14:59:37 faui44a dhc
Having the same issue on Lucid:
ar 30 11:27:34 tthomas NetworkManager: Activation (eth0) Stage 1 of 5
(Device Prepare) scheduled...
Mar 30 11:27:34 tthomas NetworkManager: Activation (eth0) Stage 1 of 5
(Device Prepare) started...
Mar 30 11:27:34 tthomas NetworkManager: nm_ip6_device_new()
On Fri, Mar 19, 2010 at 1:11 AM, Jasey wrote:
> I don't like the description / summary changes here, you've just taken a
> bug and CHANGED it into a bug which you have.
Okay, so change it back.
> The problem in this report is NOT that it brakes IP4, but the ract that
> IP6 doesn't work via RADVD
I don't like the description / summary changes here, you've just taken a
bug and CHANGED it into a bug which you have.
The problem in this report is NOT that it brakes IP4, but the ract that
IP6 doesn't work via RADVD with Network Manager. I do not have an IPv4
network , ONLY an IPv6 network. why
23 matches
Mail list logo
