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

Multiple Gateway Bug on OPNsense 18.7.5_1-amd64 #2835

Closed
sachaz opened this issue Oct 23, 2018 · 25 comments
Closed

Multiple Gateway Bug on OPNsense 18.7.5_1-amd64 #2835

sachaz opened this issue Oct 23, 2018 · 25 comments
Labels
support Community support

Comments

@sachaz
Copy link

sachaz commented Oct 23, 2018

Dear all,

since last upgrade I have several issues on all my OPNsense firewalls with 2 PPPOE:

  • OPNSense 18.7.5_1-amd64:
  • 2 PPPOE links
  • routing depending on firewall rule selecting a gateway (pppoe0 or pppoe1)
    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

@fichtner
Copy link
Member

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
o ports: mpd5 upstream MTU fix

You can switch back to older mpd5 via:

# opnsense-revert -r 18.7.4 mpd5

You can undo patch 942ddc9 for the backend via:

# opnsense-patch 942ddc996

Both require internet connectivity.

From my point of view it's unclear what caused this disruption so let's suspend judgement. :)

@fichtner fichtner added the support Community support label Oct 23, 2018
@fichtner
Copy link
Member

PS: you can also revert to 18.7.4 core package directly

# opnsense-revert -r 18.7.4 opnsense

@sachaz
Copy link
Author

sachaz commented Oct 23, 2018

Thanks for your fast answers, rollback will be useful !
I'm not sure I was on 18.7.4 is there somewhere any history of the updates ?

@fichtner
Copy link
Member

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.

@sachaz
Copy link
Author

sachaz commented Oct 24, 2018

why this issue is tagged as support and not a bug ?

@fichtner
Copy link
Member

because you receive free support. if we know what to fix or add, we will change it to a bug or feature. :)

@sachaz
Copy link
Author

sachaz commented Oct 24, 2018

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 :/

@mimugmail
Copy link
Member

You receive the same gateway for both pppoe connections?

@sachaz
Copy link
Author

sachaz commented Oct 24, 2018

yes this is the same provider with the same gateway but different public IP on each PPPOE.

@mimugmail
Copy link
Member

And this worked with pre 18.7.5 or did you receive different gateways before perhaps?

@sachaz
Copy link
Author

sachaz commented Oct 24, 2018

The configurations didn't changed nope

@mimugmail
Copy link
Member

Yes, but the gateway you receive via LCP is a decision by the provider ...

@sachaz
Copy link
Author

sachaz commented Oct 24, 2018

yes sure and ?

@mimugmail
Copy link
Member

I just try to understand the problem.
So, when you revert back to 18.7.4 all works fine again?

@sachaz
Copy link
Author

sachaz commented Oct 24, 2018

I just tested:
# opnsense-revert -r 18.7.4 opnsense
the route-to rules to pppoe[0-1] are working again

@fichtner
Copy link
Member

fichtner commented Oct 24, 2018

There are two firewall changes in 18.7.4 -> 18.7.5:

5f5f8bf8
027d8fc8

Second one being the more likely candidate.

Can you grep and provide the route-to rules in the working state?

# grep route-to /tmp/rules.debug

@sachaz
Copy link
Author

sachaz commented Oct 24, 2018

yes sure:

pass out log route-to ( pppoe0 $IP_GW ) from {pppoe0} to {!(pppoe0:network)} keep state allow-opts label "let out anything from firewall host itself"
pass out log route-to ( pppoe1 $IP_GW ) from {pppoe1} to {!(pppoe1:network)} keep state allow-opts label "let out anything from firewall host itself"
# pass in quick on igb0_vlan100 route-to ( pppoe1 $IP_GW ) inet from {(igb0_vlan100:network)} to $Video_Wildix keep state set prio (4, 4) label "USER_RULE" # e7509540f71ef91623f1a3c10cf06b72
pass in quick on igb0_vlan100 route-to ( pppoe0 $IP_GW ) inet from {(igb0_vlan100:network)} to {any} keep state label "USER_RULE: Default allow LAN to any rule" # 1a8e19dfe7c0b041baf28059c0db7cc2
# pass in quick on igb0_vlan30 route-to ( pppoe1 $IP_GW ) inet proto tcp from {(igb0_vlan30:network)} to {!(igb0_vlan30:network)} keep state label "USER_RULE" # af7c0fe3720b8275c375d4a5f3c75acb

@fichtner
Copy link
Member

@sachaz is this still the case on 18.7.7 ?

@stevenfoong
Copy link

the problem remain at version 18.7.7 .

@sachaz
Copy link
Author

sachaz commented Nov 27, 2018

An idea of where the issue is coming from ?

@mimugmail
Copy link
Member

Firewall : Settings : Advanced : Disable force Gateway ... ticked or not?

@stevenfoong
Copy link

Disable force Gateway is unchecked.

@mimugmail
Copy link
Member

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

@fichtner
Copy link
Member

Timeout.

@sachaz
Copy link
Author

sachaz commented Mar 4, 2019

Disable force Gateway is checked
still not working
a rule with a specific gateway => flow outgoing but not incoming

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

4 participants