Not sure if this is a bug or I'm just misunderstanding the intent. But in Firewall > Rules [new], the interface filter in the top-left dropdown appears to incorrectly hide some floating rules that apply to the selected interface. When viewing All rules, four floating rules are visible. One floating rule is assigned using an inverted interface selector, ! WAN. Three other floating rules are explicitly assigned to both LAN and v30_TrustedEth. When the top-left filter is changed to v30_TrustedEth, only the ! WAN floating rule remains visible. The three floating rules explicitly assigned to v30_TrustedEth disappear from the filtered view even though they apply to that interface. At the very least, it's rather inconsistent. Why does the '! Wan' rule show up but the explicitly defined floating rule doesn't on the interface?
OPNsense 26.1.10-amd64
Screenshot_20260624_180007.png
The expected behavior is not to show floating rules in "Interface rules" sections.
In fact, you should not see that rule when selecting "v30_TrustedEth". It may be a bug relative to the use of the negation (!WAN) you are using in your floating rule.
There is an issue about this on GitHub: https://github.com/opnsense/core/issues/10313 (https://github.com/opnsense/core/issues/10313)
Better leave your comments there, as the "Rules (new)" interface is a work in progress.
I did see that issue, but I didn't feel like it totally applied as it seems like since 26.1.8 there has been a slight shift in intended direction. Previously you had to click the 'inspect' eye button to show all the rules... now in 26.1.10 it looks like they are wanting to show all the rules relevant to the interface filter but in collapsible sections. This actually makes a lot of sense to me and I prefer it. You can collapse sections for a condensed view, expand them for an exhaustive look and the sections give a clear visual indicator for the order in which rules will be processed.
It's just inconsistent at the moment with some floating rules appearing and some not. I'll see about putting in a new bug issue as the previously one is closed and see where it goes.