Re: IPv6 default routes / NM vs. kernel autoconfig
- From: Stuart D Gathman <stuart gathman org>
- To: networkmanager-list gnome org
- Subject: Re: IPv6 default routes / NM vs. kernel autoconfig
- Date: Mon, 30 Jul 2012 16:59:08 -0400
On 07/23/2012 08:12 PM, Pavel Simerda expounded in part:
NM is working around lack of information from kernel and it works only
in basic situations. There are solutions to this.
While it doesn't actually break, I have a related issue with DHCP6. When
RA enables DHCP6 (and NM set to "Automatic"), I end up with *both* the
RA and DHCP addresses. And it keeps accumulating more IPs over time!
Here is what I have after 6 days uptime (prefix changed), the ::34 is
the DHCP6 assigned IP.
em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.9.34 netmask 255.255.255.0 broadcast 192.168.9.255
inet6 2001:db8:dead:beef:d070:56c1:718b:984a prefixlen 64
scopeid 0x0<global>
inet6 2001:db8:dead:beef:c14a:1e6f:cb6c:3789 prefixlen 64
scopeid 0x0<global>
inet6 2001:db8:dead:beef:781b:86da:f62a:3c46 prefixlen 64
scopeid 0x0<global>
inet6 2001:db8:dead:beef:20fd:9bd1:bec7:c06f prefixlen 64
scopeid 0x0<global>
inet6 2001:db8:dead:beef::34 prefixlen 64 scopeid 0x0<global>
inet6 2001:db8:dead:beef:20c:f1ff:fed9:97b4 prefixlen 64
scopeid 0x0<global>
inet6 fe80::20c:f1ff:fed9:97b4 prefixlen 64 scopeid 0x20<link>
inet6 2001:db8:dead:beef:5820:434c:936c:f4c1 prefixlen 64
scopeid 0x0<global>
inet6 2001:db8:dead:beef:cd72:db54:d19b:49d7 prefixlen 64
scopeid 0x0<global>
ether 00:0c:f1:d9:97:b4 txqueuelen 1000 (Ethernet)
RX packets 1412101 bytes 1128925860 (1.0 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 737197 bytes 72349628 (68.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
It looks like an attempt to use the privacy protocol to assign random
IPs that change periodically, but it forgets to remove old IPs.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]