v25.7.6 Bug? Dual PPPoE Setup: WAN1 Can't Get IPv6, "Permission Denied" in Logs.

[metacyx]

Hey everyone, need some help troubleshooting a weird issue after the recent update.

I just upgraded my OPNsense firewall to v25.7.6, and immediately ran into a serious hiccup with my WAN setup.

The Problem:

WAN1 PPPoE is totally failing to get an IPv6 address. I checked the logs, and the system is spitting out "DHCPv6 permission denied" errors specifically for the IPv6 assignment process.

The Weird Part (It's a Dual WAN Setup):

I'm running a Dual-WAN setup with two separate PPPoE connections. The thing is, WAN2 is working flawlessly—it connects, authenticates, and gets its IPv6 address without any issues. Only WAN1 is affected.

My Setup & Temporary Fix:

    My OPNsense is installed as a VM on Proxmox (PVE). (Just giving full context, though I doubt it's the root cause.)

    I tried rolling back to the previous version, and everything went back to normal. WAN1 immediately got its IPv6 address again.

It really looks like a bug introduced in v25.7.6. Has anyone else with a dual PPPoE setup run into this? Any thoughts on where I should start digging besides the logs?

Thanks in advance for the help!

[Monviech (Cedrik)]

When reading the changelog there were no src updates (meaning ports or kernel related change) or any other commit that changes pppoe.

Do the update again and try it again. And maybe try a reboot.

[metacyx]

Quick update/mea culpa on this issue!

Turns out the v25.7.6 upgrade was a total red herring! My bad, everyone.

After some deep digging and going over my configs, I finally tracked down the real culprit: I messed with the NAT Outbound settings the day before yesterday, and that's what actually broke the IPv6 on WAN1.

It had absolutely nothing to do with the new version.

My sincere apologies for causing confusion and wasting anyone's time on this! Consider the "bug report" retracted. Thanks to those who looked into it!