I am experiencing something similar but not exactly.
Lately I've read posts about IPv6 challenges so I am slowly familiarizing myself with it. I have also experienced my assigned prefix change after a disconnect (disable/re-enable IPv6 on my router) as well as forced client renew. Auto-renewals from my router's DHCPv6 client are fine.
For the past several days I received a /56 prefix and I could ping the DHCPv6 server and recursive DNS servers from my router. In today's experiment I forced a renew but didn't receive another prefix until almost 2 hours later. When I first tried to get a prefix it this weekend it took 30 minutes; yesterday when I disabled and re-enabled IPv6, it took around 20 minutes.
Today when I got the new prefix I could ping the DHCPv6 server but not Sonic's recursive DNS servers.
Lately I've read posts about IPv6 challenges so I am slowly familiarizing myself with it. I have also experienced my assigned prefix change after a disconnect (disable/re-enable IPv6 on my router) as well as forced client renew. Auto-renewals from my router's DHCPv6 client are fine.
For the past several days I received a /56 prefix and I could ping the DHCPv6 server and recursive DNS servers from my router. In today's experiment I forced a renew but didn't receive another prefix until almost 2 hours later. When I first tried to get a prefix it this weekend it took 30 minutes; yesterday when I disabled and re-enabled IPv6, it took around 20 minutes.
Today when I got the new prefix I could ping the DHCPv6 server but not Sonic's recursive DNS servers.
Statistics: Posted by klui — Wed Jan 08, 2025 5:39 pm