-
Notifications
You must be signed in to change notification settings - Fork 759
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
Multiple Gateway Bug on OPNsense 18.7.5_1-amd64 #2835
Comments
|
Here are candidates from the 18.7.5, assuming you were on 18.7.4 before: o backend: fix CPU hogging when reading on already disconnected streams You can switch back to older mpd5 via: You can undo patch 942ddc9 for the backend via: Both require internet connectivity. From my point of view it's unclear what caused this disruption so let's suspend judgement. :) |
|
PS: you can also revert to 18.7.4 core package directly |
|
Thanks for your fast answers, rollback will be useful ! |
|
there should be a file /usr/local/opnsense/version/opnsense.last but it has been deprecated with 18.7.5 now so it may not be accurate or available. |
|
why this issue is tagged as support and not a bug ? |
|
because you receive free support. if we know what to fix or add, we will change it to a bug or feature. :) |
|
sorry for me, the tagg of the ticket should be a bug once it is qualified, not a support it confusing somebody who would like to correct an issue. It's like you manage the ticketing as a private project :/ |
|
You receive the same gateway for both pppoe connections? |
|
yes this is the same provider with the same gateway but different public IP on each PPPOE. |
|
And this worked with pre 18.7.5 or did you receive different gateways before perhaps? |
|
The configurations didn't changed nope |
|
Yes, but the gateway you receive via LCP is a decision by the provider ... |
|
yes sure and ? |
|
I just try to understand the problem. |
|
I just tested: |
|
yes sure: |
|
@sachaz is this still the case on 18.7.7 ? |
|
the problem remain at version 18.7.7 . |
|
An idea of where the issue is coming from ? |
|
Firewall : Settings : Advanced : Disable force Gateway ... ticked or not? |
|
Disable force Gateway is unchecked. |
|
Can you enable it for testing? I usually always enable it on Multi WAN setups, otherwise you might have problems with port forwards on both WANs |
|
Timeout. |
|
Disable force Gateway is checked |
Dear all,
since last upgrade I have several issues on all my OPNsense firewalls with 2 PPPOE:
All this worked fine between the upgrade :/
netstat -rn show me only pppoe0
public ips are on lo0
My ADSL provider gives me public ip, but they got the same gateway.
I cannot route traffic to the non default gateway with packet filter
This is a major issue from my point of view
The text was updated successfully, but these errors were encountered: