@doni49 Do you have any floating rules?
Your rule is any any, but your forcing out your wan gateway. If the gateway is down that rule could be created without the gateway setting depending on your setting.
Rules are evaluated top down, first rule to trigger wins, no other rules are evaluated - but with that policy route - there are couple of settings that come to mind that could maybe cause what your seeing
things.jpg
Floating tab is evaluated first - so if you have stuff in there it could supersede what rules you have on the interface. Also states that have been created would still work until the state is gone, or killed, etc.
Also you have some sort of VM setup - that could be have something to do with it, maybe you don't have your networks actually isolated at layer 2?
But normally those rules would no allow this iot network to talk to your other networks because your shoving it out your wan gateway. But since it is an any rule, and if your wan gateway could get to your lan?
It is always best to be explicit in your rules and block what you don't want to allow.. before you allow what you want, if you want to have a locked down vlan/network that can not talk to your other networks, or pfsense gui, etc.. Here is an example of such a locked down network.
locked.jpg
This "test" network of mine can ping pfsense test IP, can ask pfsense for dns, and ntp and can talk to my pihole on 192.168.3.10, but then it can not talk to any other firewall IP.. Nor can it get to any other rfc1918 network - my other networks.. But then it is allowed to talk to the internet.