ER605 V2 announces old prefix after it is no longer valid
I have an ER605 V2, the WAN interface is configured like this:
The LAN interface is configured like this:
(By the way, the prefix that you can see in this screenshot is also the old one, but I guess that's from the controller and might be outdated, no big deal.)
The prefix has just changed (I think about an hour ago) and the DHCPv6 prefix delegation has long expired. According to the upstream DHCP server the router has gotten the new prefix. (Lease time is 1 minute and the router correctly comes to check about every minute.)
The problem is that the router still sends out RAs with the old prefix!
It should at least send RAs with the new prefix. Even better, it should send the old prefix as deprecated (valid/preferred lifetime = 0) in addition to the new prefix.
But it just sends RAs with the old prefix.
@Clive_A I had already captured one on the LAN side but the site wouldn't allow me to upload it. I now had the idea to take a screenshot of the screenshot and now I could upload it.
I'll have to see how I can get one on the WAN side when the prefix changes next time.
In case you're interested (this is completely off topic of course), this is what I get when I try to upload the original screenshot:
It happened again.
The DHCPv6 Renew requests from ER605 WAN to upstream router:
The replies from upstream router to ER605 WAN:
And the RAs that the ER605 sends out on the LAN:
As you can see the prefix that the ER605 is getting is 2001:9e8:5431:b720::/60 but the prefix it is advertising on the LAN is 2001:9e8:5424:c321::/64.
The prefix that it's currently advertising was the correct prefix a couple of hours ago but no longer is.
The controller interface also currently shows the wrong, old prefix:
I will now reboot the ER605 which I think will "fix" it for a couple of days or so.
Interestingly the "Renew" requests from the router contain the correct prefix, only the RAs don't. So I'm assuming the DHCP client part of the ER605 does not correctly talk to the RA part?