Port Forward NAT Weird Behavior when using WAN Address

[FLguy]

Hello all,

I'm not sure if this is a bug, or why opnSense is behaving this way.  But if I have this Port Forward NAT rule that uses the "WAN Address" object and Port Forwards SSH higher in the list.  All other Vitral IP SSH NATs will go to the "Dell_Host".  Regardless of the Virtual IP I'm trying to use, like popos_NAT (192.168.169.7) or pmox_nat (192.168.169.210).  I will also get a new SSH fingerprint message.  The WAN address is 192.168.169.20.




If I move this WAN Address rule to the bottom of the list, it works.  I can also change the forwarding port to something like TCP 2222 and 2223 for both of these rules, which will work. 




Why am I having this issue with the WAN Address object? 

Thank you

[FLguy]

We can ignore this post.  :)  I just informed via Discord that the WAN address alias/object refers to all addresses associated with the WAN interface including Virtual IPs (VIPs).

That answers the question!  +1 for discord.