[SOLVED] XS4ALL FTTH PPPoE LCP Down event after upgrade to v16.1.5

[Sinthoras]

Dear people,

For my internet connection, I use PPPoE to obtain an public IP from XS4ALL. This has always done the job. However after the upgrade to OPNsense v16.1.5 and the support of RFC 4638, my connection is broken. I can no longer obtain an public IP through PPPoE. I played around with several MTU settings, but I still get those "LCP Down" events and my OPNsense is continiously retrying to get an public IP, but he doesn't receives one.

I appreciate your help.

Kind regards,

Sinthoras

[franco]

RFC 4638 should not start to disrupt your connectivity, because it needs to be configured as such. The multipoint daemon setting is only flipped for MTUs larger than 1492, otherwise the same tag is used as before. There could be a bug in the reconfiguration code itself, but I'm unsure where to start in this case.

First of all, try to revert to opnsense 16.1.4 by issuing the following commands on the console:

# opnsense-update -sn "16.1.4\/OpenSSL"
# pkg install -fy opnsense

This should downgrade you to OPNsense 16.1.4. Try to connect up your PPPoE again to confirm that is indeed operational.

(If you use VLANs undereath your PPPoE, there is a 16.1.5_1 hotfix available that will most likely fix it already.)

[Sinthoras]

Dear franco,

Thanks for your reply.
The PPPoE traffic goes indeed over a VLAN. Yesterday evening I downgraded to an early OPNsense v16.1 release (I think v16.1.1) and my PPPoE connection comes up again. So it definitely is a problem with v16.1.5, because after a upgrade to the latest version my connection is broken. As I don't have an internet connection anymore on the OPNsense (I got internet with the ISP router), can you please tell me how to install these hotfix?

Thanks in advance.

Kind regards

Sinthoras.

[AdSchellevis]

Hi Sinthoras,

Franco created a hotfix for the issue yesterday evening, when the normal upgrade procedure shows 16.1.5_1 its going to install the right one.

I'm very sorry for the inconvenience,

Best regards,

Ad

[Sinthoras]

Thanks for all the replies.
The problem is solved with version 16.1.5_1. Wat I did is the following:

1) Reinstall (with format) OPNSense to an older version to get rid of all my tests.
2) Upgraded with the update tool to OPNsense 1.5.1_1 which solves the problem.

As my PPPoE traffic goes through an VLAN, the hotfix from franco did resolve the problem.

Kind regards,

Sinthoras

[franco]

Glad to hear, thank you