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 reconnect automatically, if your ISP allows this to happen quickly then you might not notice it being down for any length of time. > At least another interface (em) with a DHCP configured IPv4 address will > have that address removed once it goes down (using ifconfig down). If my memory is correct, 'ifconfig down' forces dhclient to exit and remove the configured address, but if you just for example unplug the cable, that doesn't happen. > I think (with my limited knowledge of how it actually works :)) the > PPPoE issue won't be solved like that as unplugging the cable or loosing > the PPPoE connection won't make the interface go down. If you watch "route -n monitor" you should see it; looks like this here: RTM_IFINFO: iface status change: len 160, if# 19, name: pppoe0, link: active, flags:<PTP,RUNNING,SIMPLEX,MULTICAST> RTM_IFINFO: iface status change: len 160, if# 19, name: pppoe0, link: no carrier, flags:<PTP,SIMPLEX,MULTICAST> RTM_IFINFO: iface status change: len 160, if# 19, name: pppoe0, link: no carrier, flags:<UP,PTP,SIMPLEX,MULTICAST> RTM_IFINFO: iface status change: len 160, if# 19, name: pppoe0, link: no carrier, flags:<PTP,RUNNING,SIMPLEX,MULTICAST> RTM_IFINFO: iface status change: len 160, if# 19, name: pppoe0, link: no carrier, flags:<UP,PTP,RUNNING,SIMPLEX,MULTICAST> RTM_IFINFO: iface status change: len 160, if# 19, name: pppoe0, link: active, flags:<UP,PTP,RUNNING,SIMPLEX,MULTICAST> RTM_IFINFO: iface status change: len 160, if# 19, name: pppoe0, link: active, flags:<UP,PTP,RUNNING,SIMPLEX,MULTICAST> RTM_IFINFO: iface status change: len 160, if# 19, name: pppoe0, link: active, flags:<UP,PTP,RUNNING,SIMPLEX,MULTICAST>
