I can reproduce this on kinetic. I get sent a 2a02:908:2812:7d20::/64 prefix via RA with "valid lifetime" and ""preferred lifetime" set to 0, every 3s. Instead of the prefix being deleted from the interface, it's lifetime is set to 1s and then expires every second, causing regular "connection changed" type of errors in Chrome, it looks like this:
I think my router is broken though, as it does not advertise any valid prefix, so you end up with *only* the /64 prefix until the router receives a new prefix from the ISP or reconfirms it or whatever, but still this is broken regardless.
I can reproduce this on kinetic. I get sent a 2a02:908: 2812:7d20: :/64 prefix via RA with "valid lifetime" and ""preferred lifetime" set to 0, every 3s. Instead of the prefix being deleted from the interface, it's lifetime is set to 1s and then expires every second, causing regular "connection changed" type of errors in Chrome, it looks like this:
inet6 2a02:908: 2812:7d20: :e9eb/128 scope global dynamic noprefixroute 2812:7d20: 55e8:17dd: e766:a872/ 64 scope global deprecated dynamic noprefixroute
valid_lft 42961sec preferred_lft 42961sec
inet6 2a02:908:
valid_lft 6603sec preferred_lft 0sec
Reconnecting the WiFi gets rid of the /64 prefix.
I think my router is broken though, as it does not advertise any valid prefix, so you end up with *only* the /64 prefix until the router receives a new prefix from the ISP or reconfirms it or whatever, but still this is broken regardless.