Why do interfaces behave differently based on their TAG ?

[Madifor]

By default , when you install OPnSense Firewall an dgo thrue the initial setup you define your WAN & LAN interface configuration.
All additional interfaces you define / configure start with opt and then a nr for example opt1.

I hope some one can explain why when you try to test a port-redirect rule configured on a opt<x>, interface as shown the firewall log(if you enable logging on the specific port) ,but when you do the same on the WAN port , nothing is shown and also not working ?

Should it work and is my opnsense firewall configuration a little bit corrupt / misconfigured due to all the testing and playing around with the settings or is there a good reason for why this is happening.

Sometimes you want to test this prior making this port open to the public (by creating a forwarding rule from the internet to your opnsense firewal wan interface.

[viragomann]

but when you do the same on the WAN port , nothing is shown and also not working ?

Did you access the WAN from a private IP by any chance? Private IPs are blocked on WAN by default. ("block private" in the interface settings).

[Patrick M. Hausen]

Also if you have an Ethernet (broadcast) network between your WAN and the default gateway and try to access services from a PC in that same broadcast domain, you need to disable reply-to.