Re: inet6 autoconf will not remove invalid addresses on -current

2015-10-02 Thread Martin Pieuchot
On 02/10/15(Fri) 12:53, Stuart Henderson wrote: > [...] > I think it would probably make sense to remove an autoconfigured > prefix/address if an interface goes down (and one could argue for this > being the right thing to do for IPv4/DHCP as well - I lost count of > the number of times I have to

Re: inet6 autoconf will not remove invalid addresses on -current

2015-10-02 Thread Stuart Henderson
On 2015-10-02, Martin Pieuchot wrote: > On 01/10/15(Thu) 19:00, Daniel Gillen wrote: >> # ndp -p >> 2001:XX:XX:7c5::/64 if=pppoe0 >> flags=LAD vltime=2592000, pltime=604800, expire=29d23h59m47s, ref=2 >> advertised by >> fe80::46d3:caff:fe9c:ef00%pppoe0 (no neighbor state) >>

Re: inet6 autoconf will not remove invalid addresses on -current

2015-10-02 Thread Martin Pieuchot
On 01/10/15(Thu) 19:00, Daniel Gillen wrote: > [...] > I managed to reproduce the issue and executed the commands you told me. > > # ifconfig pppoe0 > IPv4 address is 80.XX.XX.227 > Autoconfigured IPv6 address is 2001:XX:XX:707:XX:XX:XX:6c3a > > # ping6 -c 1 -S 2001:XX:XX:707:XX:XX:XX:6c3a

Re: inet6 autoconf will not remove invalid addresses on -current

2015-10-02 Thread Stuart Henderson
On 2015/10/02 21:24, Daniel Gillen wrote: > But does an ifconfig down really does not remove autoconfigured IPv6 > addresses? Nope, they stay there. > I can't test it as ifconfig pppoe0 down does not seem to work > as expected at all (but that's another issue). pppoe(4)'s normal mode is to

Re: inet6 autoconf will not remove invalid addresses on -current

2015-10-02 Thread Daniel Gillen
On 02.10.2015 21:55, Stuart Henderson wrote: > On 2015/10/02 21:24, Daniel Gillen wrote: >> But does an ifconfig down really does not remove autoconfigured IPv6 >> addresses? > > Nope, they stay there. > >> I can't test it as ifconfig pppoe0 down does not seem to work >> as expected at all (but

Re: inet6 autoconf will not remove invalid addresses on -current

2015-10-02 Thread Daniel Gillen
On 02.10.2015 15:21, Martin Pieuchot wrote: > On 02/10/15(Fri) 12:53, Stuart Henderson wrote: >> [...] >> I think it would probably make sense to remove an autoconfigured >> prefix/address if an interface goes down (and one could argue for this >> being the right thing to do for IPv4/DHCP as well

Re: inet6 autoconf will not remove invalid addresses on -current

2015-10-01 Thread Daniel Gillen
On 01.10.2015 10:48, Martin Pieuchot wrote: > 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 "@vo.lu" \ >> authkey "" >> dest 0.0.0.1 >> inet6 autoconf >>

Re: inet6 autoconf will not remove invalid addresses on -current

2015-10-01 Thread Daniel Gillen
On 01/10/2015 10:48, Martin Pieuchot wrote: > 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 "@vo.lu" \ >> authkey "" >> dest 0.0.0.1 >> inet6 autoconf >>

Re: inet6 autoconf will not remove invalid addresses on -current

2015-10-01 Thread Martin Pieuchot
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 "@vo.lu" \ > authkey "" > dest 0.0.0.1 > inet6 autoconf > !/sbin/route add 0.0.0.0/0 -ifp pppoe0 0.0.0.1 >

inet6 autoconf will not remove invalid addresses on -current

2015-09-30 Thread Daniel Gillen
Hi again I spotted the following while my ISP disconnected my pppoe link last night. I have the following /etc/hostname.pppoe0 file: inet 0.0.0.0 255.255.255.255 NONE \ pppoedev vlan35 \ authproto pap \ authname "@vo.lu" \ authkey "" dest 0.0.0.1 inet6 autoconf