Maybe just a glitch or timing issue, but as I said, I had it on two machines with the same ISP. I know that this ISP sometimes takes a 2-3 minutes for DHCPv6, but the problem persisted for more than 5 minutes after the reboot.
> I found this thread and checking the "Use IPv4 connectivity" on the DHCPv6c fixed IP v6 instantly.Ok, it *might* serialise the IPv6 to be after IPv4 but that's pretty annoying if the ISP enforces this.Cheers,Franco
> Not surprising considering none of the work here is included in 24.7.2.
did you reboot?
i am confused.
Quote from: CruxtheNinth on August 22, 2024, 07:17:35 pmi am confused. Apparently. This thread is about PPPoE WAN. You don't have any PPPoE set up, please start a new thread with whatever issues you are having.
Quote from: meyergru on August 22, 2024, 11:38:39 amMaybe just a glitch or timing issue, but as I said, I had it on two machines with the same ISP. I know that this ISP sometimes takes a 2-3 minutes for DHCPv6, but the problem persisted for more than 5 minutes after the reboot.I had the exact same issue this morning also on a Deutsche Glasfaser circuit.Opnsense autoupdate ran at 3am this morning. The problem is No IPv6 on WAN.The Services dhcpd6, dpinger (v6) were stopped (crashed?) and can't be started anymore.I found this thread and checking the "Use IPv4 connectivity" on the DHCPv6c fixed IP v6 instantly.There is no PPPOE link.I can provide any logs if needed.
yes, and i was using this thread because at least 2 other user with the same ISP has exactly the same issue after this upgrade.