Your message dated Wed, 6 Jul 2016 04:22:11 +0800
with message-id 
<CAMr=8w7GqT1CHpE6aCdvNJ=RG2F2yhjGfxjqJAvg=p76rwm...@mail.gmail.com>
and subject line Re: network-manager: very many IPV6 addresses on eth0
has caused the Debian Bug report #747931,
regarding network-manager: very many IPV6 addresses on eth0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
747931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747931
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.9.4.0-10
Severity: normal
Tags: ipv6

Dear Maintainer,

These lines appear in /var/log/syslog every 5 min
May 12 07:52:11 sleipnir NetworkManager[6719]: <info> Policy set
'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
May 12 07:52:11 sleipnir NetworkManager[6719]: <info> Policy set
'Wired connection 1' (eth0) as default for IPv6 routing and DNS.

When it happens, eth0 gets another IPV6 address, for example:
eth0      Link encap:Ethernet  HWaddr 00:0a:95:66:9c:38
          inet addr:192.168.8.14  Bcast:192.168.8.255  Mask:255.255.255.0
          inet6 addr: 2002:XXXX:61ef:1:c20:268e:2d67:67a8/64 Scope:Global
          inet6 addr: 2002:XXXX:61ef:1:188b:efac:7164:7dd8/64 Scope:Global
          inet6 addr: 2002:XXXX:61ef:1:569:ac30:a77e:7b90/64 Scope:Global
          inet6 addr: 2002:XXXX:61ef:1:503b:ffd9:1adc:c27c/64 Scope:Global
          inet6 addr: 2002:XXXX:61ef:1:20a:95ff:fe66:9c38/64 Scope:Global
          inet6 addr: fe80::20a:95ff:fe66:9c38/64 Scope:Link
          inet6 addr: 2002:XXXX:61ef:1:5441:2c23:a00b:cdd8/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24328 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20851 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3793711 (3.6 MiB)  TX bytes:5166528 (4.9 MiB)
          Interrupt:41 Base address:0x4800

This system was installed a few weeks ago. I believe I have made no
network configuration whatsoever -
just relying on standrad DHCP for IPv4 and Autoconfigure for IPv6.
I have one other Debain 7.5 system (an armv5tel system, not a PowerPC)
on the network, without this problem.
I have a very simple 6to4-configured OpenWRT router that advertises
the IPV6 network. The clients autoconfigure.
I also have several other computers with different operating systems
(Xubuntu, Mac OS X, Windows 7) on the
network - none of them have problems with several IPV6 addresses.

I noticed this problem because the avahi-deamon consumed 99% cpu when
I had almost 200 IPv6 addresses:
/var/log/syslog:
  (almost 200 lines like the next line)
May 11 07:44:28 sleipnir avahi-daemon[2350]: Withdrawing address
record for 2002:XXXX:61ef:1:90d1:46d6:3b17:5f0a on eth0.
  (then)
May 11 07:44:28 sleipnir rsyslogd-2177: imuxsock begins to drop
messages from pid 2350 due to rate-limiting
May 11 07:44:45 sleipnir NetworkManager[2174]: <warn> error monitoring
device for netlink events: No buffer space available
May 11 07:44:45 sleipnir minissdpd[3915]: recvmsg(s, &hdr, 0): No
buffer space available

I understand I may be better off without the avahi-daemon, but
switching it off does not fix the problem.
Restarting Network Manager brings me down to TWO IPV6-addresses (which
is one too much, as I understand it):
root@sleipnir:~# service network-manager restart ; /sbin/ifconfig
[ ok ] Stopping network connection manager: NetworkManager.
[ ok ] Starting network connection manager: NetworkManager.
eth0      Link encap:Ethernet  HWaddr 00:0a:95:66:9c:38
          inet addr:192.168.8.14  Bcast:192.168.8.255  Mask:255.255.255.0
          inet6 addr: 2002:XXXX:61ef:1:20a:95ff:fe66:9c38/64 Scope:Global
          inet6 addr: fe80::20a:95ff:fe66:9c38/64 Scope:Link
          inet6 addr: 2002:XXXX:61ef:1:8431:f293:326a:4e5/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:35676 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28823 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5006172 (4.7 MiB)  TX bytes:6793477 (6.4 MiB)
          Interrupt:41 Base address:0x4800

According to syslog the problem appeared for the first time on 2014-05-09.
According to /etc/apt/history.log the system had not been updated
since 2014-05-01.
I updated it as soon as I found the problem, but with no success.
I belive the problem with TWO addresses has been present since I
installed the system. At that time
I just found it peculiar. But getting more and more addresses with
time is new since May 9.

This is an Apple PowerBook. The wireless network (eth1) is disabled.
The computer is on 24/7, acting as a test webserver.

Workaround: add to /etc/crontab
59 *    * * *   root    service network-manager restart

Restarting the computer also takes me down to two addresses, but does
not solve the problem.

Below is standard reportbug output, run as root, otherwise I got
permission error with:
/etc/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla

I find this all strange enough to file a bug report.

Thank you all for making a fantastic job with Debian!

  Regards
  Gunnar

-- System Information:
Debian Release: 7.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: powerpc (ppc)

Kernel: Linux 3.2.0-4-powerpc
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  adduser                3.113+nmu3
ii  dbus                   1.6.8-1+deb7u1
ii  dpkg                   1.16.14
ii  isc-dhcp-client        4.2.2.dfsg.1-5+deb70u6
ii  libc6                  2.13-38+deb7u1
ii  libdbus-1-3            1.6.8-1+deb7u1
ii  libdbus-glib-1-2       0.100.2-1
ii  libgcrypt11            1.5.0-5+deb7u1
ii  libglib2.0-0           2.33.12+really2.32.4-5
ii  libgnutls26            2.12.20-8+deb7u1
ii  libgudev-1.0-0         175-7.2
ii  libnl-3-200            3.2.7-4
ii  libnl-genl-3-200       3.2.7-4
ii  libnl-route-3-200      3.2.7-4
ii  libnm-glib4            0.9.4.0-10
ii  libnm-util2            0.9.4.0-10
ii  libpolkit-gobject-1-0  0.105-3
ii  libuuid1               2.20.1-5.3
ii  lsb-base               4.1+Debian8+deb7u1
ii  udev                   175-7.2
ii  wpasupplicant          1.0-3+b2

Versions of packages network-manager recommends:
ii  crda          1.1.2-1
ii  dnsmasq-base  2.62-3+deb7u1
ii  iptables      1.4.14-3.1
ii  modemmanager  0.5.2.0-2
ii  policykit-1   0.105-3
ii  ppp           2.4.5-5.1+b1

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

-- no debconf information

--- End Message ---
--- Begin Message ---
This is not a bug, but a behavior defined by "Privacy Extensions for
Stateless Address Autoconfiguration in IPv6", which is RFC 4941.

This feature is intended to protect user's privacy by assigning short
lifetime (hours to days) IPv6 addresses that are not directly
generated from your MAC address because the latter one could be used
as an interface identifier to track the user's activity.

Best,
Aron

--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

Reply via email to