Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
22.1 Legacy Series
»
Floating rule issues
« previous
next »
Print
Pages: [
1
]
Author
Topic: Floating rule issues (Read 1062 times)
jclendineng
Full Member
Posts: 153
Karma: 7
Floating rule issues
«
on:
May 20, 2022, 04:21:15 am »
I posted on a couple other threads regarding Default deny/state violations in the logs. On a related note, I have floating rules for certain items but it was my understanding that interface rules applied after floating. Im blocking a lot of IGMP traffic and had to make a new floating rule to allow IGMP on all interfaces. This shouldn't be required...floating rules are applied prior to interface rules so if there are default deny rules in the floating rules they will take precedent over the allow alls I have on each interface...Im also seeing blocked traffic to certain servers from a reverse proxy. all other traffic from that proxy is allowed so I'm not sure why/where the default deny is happening.
Logged
zerwes
Full Member
Posts: 125
Karma: 8
Re: Floating rule issues
«
Reply #1 on:
May 20, 2022, 07:26:15 am »
https://docs.opnsense.org/manual/firewall.html#processing-order
And the "quick" setting might be important here ...
Logged
jclendineng
Full Member
Posts: 153
Karma: 7
Re: Floating rule issues
«
Reply #2 on:
May 20, 2022, 04:44:10 pm »
I get that part, I guess my question is more along the lines of why then does the Floating rules have a default deny all at the top? Wouldn't that logically mean that all the Default deny / state violation rules I'm seeing are from the "System Defined" rule in floating? Some are tagged DF, that's fine, I get that is blocked unless I manually change in FW settings but what about all the traffic blocked that do not have any tags? There isn't really any visibility into why its being dropped except its a state violation of some sort, making it hard to diagnose new drops.
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
22.1 Legacy Series
»
Floating rule issues