What's new

PPPOE WAN not working on OPNsense but works on router

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

CntrlAltDel

Occasional Visitor
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.
 
Looking around on the Internet, I see others that had expirienced that bug. There is even a bug report raised at its github. So if you have that older version of OPNsense, you need to use that instead of the two newer versions that have the VM bugs with the kernel. But to be fair, this software wasn't really designed to run inside a VM environment and there will be a small deterioration of performance with PPPoe connections.
 
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.

Authentication?

I would start looking at the OpnSense system logs and see what's happening there...
 
Its the setting choices in the OS and kernel code, what I see on my scratchpad computer I installed it on to look at the code.

the module MSIX has bad IRQ timing statements. Which is just one of several of the issues I see, however, I don't have time today to further go into detail of the other things I see. Use Legacy settings (MSI)

Bios:
Disable all c-states.
Disable all onboard Audio
Disable CPU scaling

inside OPNsense
No MAC spoofing,No promiscuous,
set
Code:
hw.pci.enable_msix: 0
hw.pci.enable_msi: 1
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Top