Hello, On 30/09/15(Wed) 18:19, Daniel Gillen wrote: > [...] > inet 0.0.0.0 255.255.255.255 NONE \ > pppoedev vlan35 \ > authproto pap \ > authname "<user>@vo.lu" \ > authkey "<password>" > dest 0.0.0.1 > inet6 autoconf > !/sbin/route add 0.0.0.0/0 -ifp pppoe0 0.0.0.1 > !/sbin/route add ::/0 -ifp pppoe0 fe80:: > > As you can see, it get my IPv6 address trough autoconfiguration. > > After my pppoe reconnected again, I saw the following in ifconfig:
What do you mean by "reconnected again" ? > pppoe0: flags=208851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST,AUTOCONF6> > mtu 1492 > priority: 0 > dev: vlan35 state: session > sid: 0x44e PADI retries: 8 PADR retries: 0 time: 13:20:45 > sppp: phase network authproto pap authname "<user>@vo.lu" > groups: pppoe egress > status: active > inet6 fe80::XX:XX:XX:6c3a%pppoe0 -> prefixlen 64 scopeid 0x8 > inet6 2001:XX:XX:6f3:XX:XX:XX:6c3a -> prefixlen 64 autoconf > pltime 556434 vltime 2543634 > [...] > inet6 2001:XX:XX:6f3:XX:XX:XX:87b2 -> prefixlen 64 autoconf > autoconfprivacy pltime 1835 vltime 520374 > inet 85.XX.XX.XX --> 80.XX.XX.XX netmask 0xffffffff > inet6 2001:XX:XX:7c5:XX:XX:XX:6c3a -> prefixlen 64 autoconf > pltime 604755 vltime 2591955 > inet6 2001:XX:XX:7c5:XX:XX:XX:30c -> prefixlen 64 autoconf > autoconfprivacy pltime 37915 vltime 556755 > > I got the new 2001:XX:XX:7c5::/64 prefix after the reconnect and OpenBSD > added it to my interface. > > But it didn't remove the now invalid and no longer working > 2001:XX:XX:6f3::/64 prefix addresses which caused quite some issues as > my NAT was still using that address for part of the connections. > > Shouldn't those be removed as soon as their prefix is no longer valid? > Or at least all be deprecated? If this happens again could you include the output of "# ndp -p", "# route -n show -inet6" and "# ndp -r" in your report? Thanks, Martin