Hi all, I tried to configure PPPoE on opnsense with dedicated WAN ethernet port.
Opnsense is at release 24.1.3_1-amd64
I already addressed VLAN tag topic on interface.
Now when PPPoE daemon initialize connection it fail with this message
...
PPPoE connection timeout after 9 seconds
...
I read that is something related low timeout in opnsese and I alreeady asked to the provider if is possible to make faster the process fron their side but no way....
Is possiblle with any settings/flas/config file to increase this timeiyt from actual 9 seconds?
No one has this problem?
That error indicates that there are no answers to your PADI requests. This is probably:
1. Your ISP does give PADO answers very slowly - which is uncommon.
2. The lower OSI layer connection is not active.
The latter can be because of several problems that lie outside of the reach of OpnSense as a router, namely: Your ONT does not get a connection because of faulty cabling or nonfunctional authorisation (like PLOAM password on GPON).
But I tend to guess that you try to transition from an ISP router to an OpnSense and think you can connect the WAN port of your OpnSense to that without setting it to bridge mode first - if that is at all possible. That, of course, will not work (tm).
Quote from: nicwanz on August 03, 2024, 02:53:51 PM
No one has this problem?
Here (https://forum.opnsense.org/index.php?topic=41574.0) my friend. No one helped me yet. For me it is happening after leaving OPNsense off for a couple of minutes (not happening when just rebooting opnsense or leaving off for a few seconds).
After many tries PPPoE got connected. It is 100% opnsense related issue as using a PC as a PPPoE client it works like a charm -.-"
Judging by Google this keeps happening for some people. Just looking at a few reports here and elsewhere it looks like it's not the ISP is purely at fault, but mileage highly varies between project use and OS versions.
I think the timeout can be increased, but if it's not "just a slow ISP" making the timeout longer will not change it because it's something persistent. Modem driver? Bad link? Don't know.
Cheers,
Franco