Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with multi-wan PPPoE interfaces since 24.7.11 #8181

Open
andrewhotlab opened this issue Jan 5, 2025 · 5 comments
Open

Problem with multi-wan PPPoE interfaces since 24.7.11 #8181

andrewhotlab opened this issue Jan 5, 2025 · 5 comments
Labels
support Community support

Comments

@andrewhotlab
Copy link

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug

We have two WAN interfaces, both configured as PPPoE clients. Both providers assign the same IPv4 address as default gateway. Since we upgraded to OPNsense 24.7.11, only one link can be used at the same time. We downgraded to 24.7.10 and the problem disappeared.
No problem in another setup, were both PPPoE interfaces receive different gateway IP addresses.

We guess that the cause is in one of these changes, but we have no clue about what of them.

To Reproduce

Upgrade OPNsense from 24.7.10 to 24.7.11

Expected behavior

Traffic flow on both WAN interfaces.

Screenshots

2025-01-05_12-53

@AdSchellevis
Copy link
Member

We have two WAN interfaces, both configured as PPPoE clients. Both providers assign the same IPv4 address as default gateway. Since we upgraded to OPNsense 24.7.11, only one link can be used at the same time.

This isn't new, you just can't have two identical upstream gateways.

@AdSchellevis AdSchellevis added the support Community support label Jan 5, 2025
@andrewhotlab
Copy link
Author

It absolutely makes sense, but that setup has been working fine until version 24.7.11… what might be the commit which changed this behavior?

@Monviech
Copy link
Member

Monviech commented Jan 5, 2025

#5238

@andrewhotlab
Copy link
Author

Thank you very much @Monviech, but it does not help me understand why that setup has been working until the latest update.
In the mean time, I found that the "disruptive" change is not inside the opnsense-24.7.11 package, but in kernel-24.7.10-amd64.pkg. If I remember correctly, it has been a problematic version, fixed on 4th December 2024: https://forum.opnsense.org/index.php?topic=44413.msg221775#msg221775

Sorry for my ignorance: where are sources which the kernel package is built from?

@AdSchellevis
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

3 participants