16
18.7 Legacy Series / Re: WAN Interface not obtaining IPv6 prefix.
« on: January 16, 2019, 11:03:07 pm »
Yea I guess that makes sense. Just request the address anyway and use the prefix.
But now when I do that, it's using the prefix I previously had (starts with 2601) instead of the one comcast just gave me (2001). Tried rebooting, etc. Why wont the lan update to the new prefix?
Edit: After going back to my old config just to test a few things (DHCPv6 WAN with track interface LAN, no DHCPv6 on lan), comcast gave my router an IP starting with 2001, but all my clients are still getting IPs that start with 2601 (my old prefix). Why are they doing that?
And is it possible to have clients that are configured with SLAAC still be registered in the local DNS so that I can resolve them using 'asdf.lan6.example.com'?
Also an issue Im having is that using Track Interface for lan, it doesn't seem to be clearing the previous settings, thus why it's using the wrong prefix. How can I clear this?
But now when I do that, it's using the prefix I previously had (starts with 2601) instead of the one comcast just gave me (2001). Tried rebooting, etc. Why wont the lan update to the new prefix?
Edit: After going back to my old config just to test a few things (DHCPv6 WAN with track interface LAN, no DHCPv6 on lan), comcast gave my router an IP starting with 2001, but all my clients are still getting IPs that start with 2601 (my old prefix). Why are they doing that?
And is it possible to have clients that are configured with SLAAC still be registered in the local DNS so that I can resolve them using 'asdf.lan6.example.com'?
Also an issue Im having is that using Track Interface for lan, it doesn't seem to be clearing the previous settings, thus why it's using the wrong prefix. How can I clear this?