FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 07-29-2011, 02:00 PM
Paul Wouters
 
Default DHCPv6 support in Network Manager isn't RFC compliant

On Fri, 29 Jul 2011, Tore Anderson wrote:

> There's two potential explanations for that that I'm aware of:
>
> 1) The «Require IPv4 for this connection to complete» NM setting is
> unfortunately checked by default, see
> <https://bugzilla.redhat.com/show_bug.cgi?id=538499> and
> <https://bugs.launchpad.net/bugs/761558>.

That is still the case for Fedora 14 with all updates

I had to disable it. That in itself is hard because the connection
(since it has only failed) shows up at the BOTTOM of the network manager
wireless networks, since it is sorted on "last connection" which does
not take failed connections into account ("never" is sorted to the bottom)

I think it would be much better to keep failed but just attempted connections
at the top of the list in network manager, if the sort order is connection time
and not alphabetical.

> 2) Fedora, for some reason I cannot fully comprehend, drops DHCPv6
> replies in its default ip6tables ruleset, see
> <https://bugzilla.redhat.com/show_bug.cgi?id=591630> (apparently a WONTFIX).

I can confirm this is still an issue and I've updated the bug to reflect that.
Stopping the firewall did not help me on ietf-v6ONLY though. I still got not
DNS entry in /etc/resolv.conf and on top of that my routing seemed to not have
a working default route.

[paul@thinkpad ~]$ traceroute6 -n 2001:888:2003:1004:c2ff:eeff:fe00:136
traceroute to 2001:888:2003:1004:c2ff:eeff:fe00:136 (2001:888:2003:1004:c2ff:eeff:fe00:136), 30 hops max, 80 byte packets
1 2001:df8:0:112:221:5cff:fe54:4fe5 3005.373 ms !H 3007.441 ms !H *
[paul@thinkpad ~]$

[paul@thinkpad ~]$ ip -6 ro li default
default dev wlan0 proto static metric 1024 expires 2147157sec mtu 1500 advmss 1440 hoplimit 0
default via fe80::212:1e00:70e7:bc00 dev wlan0 proto kernel metric 1024 mtu 1500 advmss 1440 hoplimit 64
default via fe80::205:8500:708e:3c00 dev wlan0 proto kernel metric 1024 expires 1716sec mtu 1500 advmss 1440 hoplimit 64


So, IPv6only is better then it was one or two fedora releases ago, but it seems to not
be fully working on Fedora-14, and from listening to other people, has not fully been
resolved on Fedora-15 either....

Paul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 07-29-2011, 03:50 PM
Dan Williams
 
Default DHCPv6 support in Network Manager isn't RFC compliant

On Fri, 2011-07-29 at 16:12 +0200, Tore Anderson wrote:
> * Paul Wouters
>
> > Stopping the firewall did not help me on ietf-v6ONLY though. I still got
> > not DNS entry in /etc/resolv.conf and on top of that my routing seemed to
> > not have a working default route.
> >
> > [...]
> >
> > [paul@thinkpad ~]$ ip -6 ro li default
> > default dev wlan0 proto static metric 1024 expires 2147157sec mtu
> > 1500 advmss 1440 hoplimit 0
>
> This route is bogus, it basically says the entire IPv6 internet is
> directly attached to the layer 2 LAN segment you're on. I've seen NM
> create such a route before, but under different circumstances, and
> besides that bug should be long fixed - see
> <https://bugzilla.redhat.com/show_bug.cgi?id=588560>.
>
> > default via fe80::212:1e00:70e7:bc00 dev wlan0 proto kernel metric
> > 1024 mtu 1500 advmss 1440 hoplimit 64
> > default via fe80::205:8500:708e:3c00 dev wlan0 proto kernel metric
> > 1024 expires 1716sec mtu 1500 advmss 1440 hoplimit 64
>
> Here you have another two default routes via two different next-hops.
> Likely one of them is bogus, perhaps caused by a rogue RA. I find it
> curious that only one of them is displaying a lifetime counter, too.
>
> Are you certain that NM adds all of these? One way to try is to set the
> IPv4 mode to link-local only, IPv6 mode to disabled/ignored, and then
> connect to the network. The connection should then «succeed», and you'll
> be able to see if anything IPv6-related is going on outside of NM's control.

Running NM with --no-daemon --log-level=debug is a great way to figure
out *exactly* what NM is doing with addressing and the routing table,
which people can use as a basis for diagnosing these issues...

Dan


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 

Thread Tools




All times are GMT. The time now is 05:16 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org