-
Notifications
You must be signed in to change notification settings - Fork 759
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
firewall: only add gateway rules when the protocol is assigned to the…
… interface PR: #1681 (cherry picked from commit 5739487) (cherry picked from commit 3676fb4) (cherry picked from commit afcca42) (cherry picked from commit 9dc19a1)
- Loading branch information
1 parent
dfb9ed1
commit 0b38eff
Showing
2 changed files
with
45 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0b38effThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, I stumbled upon this one regarding my problem with Multi WAN and this post:
https://forum.opnsense.org/index.php?topic=5743.msg23575#msg23575
@fichtner Is this already in 17.7.1. Does this really work for local generated traffic to enter gateway (group)? It's not working for me but probably a Layer 8 problem.
0b38effThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the fix in 17.7.1 works exactly the other way, it puts back interface pinning, so it sucks ;)
0b38effThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem is that linux users are spoiled with multiple routing tables.
Everybody wants this simple feature:
2 WANs, Connect from INET to WAN1, reply packet goes out WAN1 with source WAN1 address. Connect from INET to WAN2, reply packet goes out WAN2 with source WAN2 address.
This should be an implicitness ...
0b38effThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea why, but now it works as expected. I disabled gate groups and all pf rules with route target.
Only gateway switching enabled. Now I can reach OPN via WAN1 and WAN2 IP.
oO
0b38effThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mimugmail 65a55bb makes the route-to auto generated rules optional. Different expectations from different users, this is likely the best we can do now.