After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 737252 - IPv6 next hop count being set incorrectly, breaks connectivity
IPv6 next hop count being set incorrectly, breaks connectivity
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: IP and DNS config
0.9.x
Other Linux
: Normal critical
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
: 742974 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-09-24 11:04 UTC by Andrew Cowie
Modified: 2015-01-15 16:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Andrew Cowie 2014-09-24 11:04:38 UTC 
IPv6 does not work when I'm at the office:

PING www.operationaldynamics.com(2600:3c02::f03c:91ff:fedf:52e8) 56 data bytes
From procyon.atl.operationaldynamics.com icmp_seq=1 Time exceeded: Hop limit
From procyon.atl.operationaldynamics.com icmp_seq=2 Time exceeded: Hop limit
^C

I keep having to do this:

# sysctl -w net.ipv6.conf.enp0s25.hop_limit=64

because NetworkManager is setting it to 0. This is unfortunately because apparently NM honours whatever the router advertises, but some routers seem to think that 0 is an appropriate value for "infinite, yes, use me please". Like the one at work. 

Unfortunately putting this in /etc/sysctl.conf doesn't help because NetworkManager resets it on each new connection.

You can see people working through the issue here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756534

The suggestion is made that if a 0 turns up, maybe NM should override that with a default of 64. I think it a good idea.

I know we're about to release, but urgent; IPv6 is broken!

Fedora 20, GNOME 3.12 from Richard Hughes. Can and will build to test if you need me to.

AfC
Comment 1 Lubomir Rintel 2014-10-29 11:17:05 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.

master: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=c6682972
0.9.10: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6a79acb0
Comment 2 Patrick Rauscher 2015-01-15 16:03:14 UTC 
*** Bug 742974 has been marked as a duplicate of this bug. ***