PPPOE WAN not working on OPNsense but works on router

Started by CntrlAltDel, December 13, 2024, 09:29:03 AM

Previous topic - Next topic
Hi there,

I have a ESXi host with OPNsense installed serving as my router connected to an Asus RT-AC88U in AP mode.
The issue I'm having is I can connect to my GPON/ONT with WAN set in DHCP mode fine but it provisions a CG-NAT'd IP.
When I switch to PPPOE and use my PPPOE credentials that work on my Asus router (not ISP provided router) it connects fine.
But when I do the same on OPNsense I just get "connecting..." from the logs.
Strange thing is, I had OPNsense running in this exact scenario for 2 years prior, just about 4 months ago I decided to switch back to my regular router and decomission my ESXi host, I've now redeployed everything but seem to be stuck here.
Has anyone else dealt with this issue?
ISP is saying PPPOE connectivity is being rejected from their end but like I said I've gotten this to work before and it does work on my regular Asus router.

Quote from: CntrlAltDel on December 13, 2024, 09:29:03 AMISP is saying PPPOE connectivity is being rejected from their end but like I said I've gotten this to work before and it does work on my regular Asus router.

Did they say WHY it's being rejected?

Quote from: CntrlAltDel on December 13, 2024, 09:29:03 AMISP is saying PPPOE connectivity is being rejected from their end but like I said I've gotten this to work before and it does work on my regular Asus router.

I have PPPoE running successfully in OPNsense running in ESXi VM, without any issues....works great, even supports adaptive LCP echo request, which is a big plus...

You just need to take a look at the PPPoE logs to figure out what's not working in your deployment.

Just navigate to Interfaces -> Point-to-Point -> LogFile

Select Log level = informational


PPPoE is quite a simple protocol to tshoot, and the logging is excellent.

It might be an issues with MAC address of your WAN interface. Some (not all) ISP do look at your MAC address and if it changes they will reject even valid PPPOE creds. Second thing is cred. I've had this in the past, when I was migrating between routers, I've failed to store updated pppoe creds and was scratching my head why it works on old router, but not the new one ... all while I was using old pppoe password.