Bug#756534: network-manager: IPv6 hop limit set to 0

2014-10-29 Thread Yin

Seems this has been noticed and fixed upstream:

https://bugzilla.gnome.org/show_bug.cgi?id=737252

Over to you maintainer :)

- Yinette


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#756534: network-manager: IPv6 hop limit set to 0

2014-08-12 Thread Yin
I can confirm I'm getting the same issue. (Running Jessie/Sid, with 
network-manager Version: 0.9.4.0-10)


It appears that network manager will directly change the sysctl values 
like thus:


# sysctl -A |grep -i hop_limit
net.ipv6.conf.all.hop_limit = 64
net.ipv6.conf.default.hop_limit = 64
net.ipv6.conf.eth0.hop_limit = 0
net.ipv6.conf.lo.hop_limit = 64
net.ipv6.conf.wlan0.hop_limit = 0

Once reset using a script or sysctl -w directly, once the interface is 
brought back up (unplugged-replugged or wifi reconnect) it will reset 
the value from 64 (or whatever) back to 0


I've had a look through the RedHat/Gnome NetworkManager git tree, but 
cannot see any fix for this as yet. I have been unable to confirm if its 
an issue with their source or if its a debian patch that has introduced 
this.


Regards, Yinette.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#756534: network-manager: IPv6 hop limit set to 0

2014-07-30 Thread Ralf Jung
Package: network-manager
Version: 0.9.10.0-1
Severity: normal

Dear Maintainer,

I am having trouble connecting to an IPv6 network. Other hosts in this network
(e.g. with Windows) connect fine. Unfortunately, I don't have access to any
other IPv6 network to test.

Running ping6 ralfj.de shows Hop Limit exceeded, and indeed checking the
packets with Wireshark shows that the hop limit of all packets is 0.
When I try to connect to an IPv6 site with Firefox, the packets also have
hop limit 0.

IPv6 used to work fine around 1.5 months ago, I did not have the time to
try in between. There were several NM updates since then.

I tried to debug the issue, but did not get very far: I could not find out
where this hop limit comes from. I also failed to change the hop limit
with route -6 or ip -6 route due to both commands disliking how I told
them abour routes (I couldn't figure out how to specify existing routes,
just got useless errors all the time).

I found some weird entries in route -6:
Kernel IPv6 routing table
DestinationNext Hop   Flag Met Ref Use If
::1/128:: U256 0 0 lo
2a02:810c:86c0:ca::/64 :: Ue   256 0 0 wlan0
fe80::/64  :: U256 0 0 wlan0
::/0   fe80::20c:42ff:fe34:855b   UG   1024 0 0 
wlan0
::/0   :: !n   -1  1   309 lo
::1/128:: Un   0   1 7 lo
2a02:810c:86c0:ca:511:cc78:59bd:57e4/128 :: Un   0   1  
  43 lo
2a02:810c:86c0:ca:fef8:aeff:fe51:889e/128 :: Un   0   1 
0 lo
fe80::fef8:aeff:fe51:889e/128  :: Un   0   127 lo
ff00::/8   :: U256 0 0 wlan0
::/0   :: !n   -1  1   309 lo

Note the two reject routes for ::/0 which the counter says are used all
the time - except that I actually do see packets on the wire with wireshark.
Also note I have no idea whether this is weird or a problem at all ;-)

ip -6 route show shows way less:
2a02:810c:86c0:ca::/64 dev wlan0  proto kernel  metric 256  expires 601727sec
fe80::/64 dev wlan0  proto kernel  metric 256 
default via fe80::20c:42ff:fe34:855b dev wlan0  proto static  metric 1024

Kind regards
Ralf

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.15.3 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.8.6-1
ii  init-system-helpers1.19
ii  isc-dhcp-client4.3.0+dfsg-2
ii  libc6  2.19-7
ii  libdbus-1-31.8.6-1
ii  libdbus-glib-1-2   0.102-1
ii  libgcrypt111.5.3-4
ii  libglib2.0-0   2.40.0-3
ii  libgnutls-deb0-28  3.2.16-1
ii  libgudev-1.0-0 208-6
ii  libmm-glib01.2.0-1
ii  libndp01.3-1
ii  libnewt0.520.52.17-1
ii  libnl-3-2003.2.24-2
ii  libnl-genl-3-200   3.2.24-2
ii  libnl-route-3-200  3.2.24-2
ii  libnm-glib40.9.10.0-1
ii  libnm-util20.9.10.0-1
ii  libpam-systemd 208-6
ii  libpolkit-gobject-1-0  0.105-6.1
ii  libreadline6   6.3-6
ii  libsoup2.4-1   2.46.0-2
ii  libsystemd-daemon0 208-6
ii  libsystemd-login0  208-6
ii  libuuid1   2.20.1-5.8
ii  lsb-base   4.1+Debian13
ii  policykit-10.105-6.1
ii  udev   208-6
ii  wpasupplicant  1.1-1

Versions of packages network-manager recommends:
ii  crda  1.1.2-1
ii  dnsmasq-base  2.71-1
ii  iptables  1.4.21-2
ii  modemmanager  1.2.0-1
ii  ppp   2.4.6-2

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.31-4

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
no-auto-default=10:BF:48:05:C7:F7,
[ifupdown]
managed=false


-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org