In D30246#679309, @eri wrote:

This kind of breaks the assumption of floating states, 'it will apply in any interface any direction'.

The usual state matching still applies, so the state will still be match traffic irrespective of interface.

These states can be killed through src/dst options, or potentially you can do this in a daemon managing states in userland and killing states by id.

Yes, but without it there's no way to say 'kill states originating on interface X' (assuming floating states, of course). It intuitively makes no sense to be unable to kill states (in this way) simply because we're less strict about matching them.

I know there is a use-case in pfSense for this but in itself pfSense overloaded the meaning of floating state and has patches internal patches to deal with it. IIRC this is a by product of that.

pfSense currently has a fairly hacky solution to this where it basically hardcodes all states to be if-bound, but then undoes that in the state matching code. That obtains the same result (i.e. we can kill floating states by their interface), but has a lot more fallout that this.