pfSense

There isn't nearly enough information here and this site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .

See Reporting Issues with pfSense Software for more information.

1. NAT Reflection mode for port forwards
2. Enable NAT Reflection for 1:1 NAT
3. Enable automatic outbound NAT for Reflection
4. Port forward rule on WAN
5. 1:1 rule on WAN

This results in the following rules:
igb0 = WAN; igb1 = LAN1; igb2 = LAN2

binat on igb0 from 10.1.1.4 to any -> 192.0.2.2
[...]
# NAT Inbound Redirects
rdr on igb0 inet proto { tcp udp } from any to 177.231.47.7 port 8080 -> 10.1.1.3
# Reflection redirect
rdr on { igb1 igb2 } inet proto { tcp udp } from any to 192.0.2.3 port 80 -> 10.1.1.3
# Reflection redirects and NAT for 1:1 mappings
rdr on { igb1 igb2 } from any to 192.0.2.2 -> 10.1.1.4 bitmask
no nat on igb1 from (igb1) to 10.1.1.4
nat on igb1 from 10.1.1.0/24 to 10.1.1.4 -> 10.1.1.1 port 1024:65535

Here, the nat rule should instead be the following to address traffic from other subnets:

nat on igb1 from { 10.1.1.0/24 10.2.2.0/24 } to 10.1.1.4 -> 10.1.1.1 port 1024:65535

And an additional nat rule should be added for the port forward:

nat on igb1 from { 10.1.1.0/24 10.2.2.0/24 } to 10.1.1.3 -> 10.1.1.1 port 1024:65535

Without these additional rules, accessing the public IP results in asymmetric routing.

Closing as it's not an issue on 22.01.