Anti-Lockout Rule (Destination NAT) -> open ports external?

[RamSense]

I just noticed on https://pentest-tools.com/network-vulnerability-scanning/port-scanner-online-nmap
that the auto generated Anti-Lockout Rules (Destination NAT) for port 22 and port 444 (my opnsense gui) are both opened on WAN and can be reached.

Is this my fault and should those 2 Anti-Lockout rules be deleted after installing 26.1 or is this something to look at? I cant see a delete option in the Destination NAT list.

[meyergru]

How would that work? The anti-lockout rules are for the LAN interface as source only. Did you actually see those two ports open from the WAN side?

[RamSense]

I've tried the OPNsense web Gui and it is reachable. It was always disabled for WAN. In OPNSense I had, and still have, System -> Settings :  Listen Interfaces ALL (recommended).
Looks like I have to change this to LAN and Wireguard only(?) although it is not recommended?
Can you reproduce?

I have not made any rules for the OPNsense gui to be reachable on wan

Im on OPNsense 26.1_4-amd64
and migrated to the rules (new) and deleted the old rules.

[RamSense]

Looks like a bug, when I place a block rule on wan port 444 I can still externally reach the OPNsense gui:

[Patrick M. Hausen]

Possibly a bad interaction of anti-lockout and NAT reflection? I use neither, sorry.

[meyergru]

I have the Anti-Lockout rules enabled and administration on all interfaces, too. During 26.1 upgrade, two separate non-editable rules have shown up on top of the destination NAT rules, for IPv4 and IPv6. The source interface for both is LAN.

I have done no rules migration to new rules and also created no new rules. Reflection settings are all on in "Firewall: Settings: Advanced".

SSH and Web GUI are not open on WAN.

[RamSense]

Reflection settings were are all on in "Firewall: Settings: Advanced". I turned them off, no difference.
Made a block rule below (can't get it above the lock out rule), no difference, see picture.

[Patrick M. Hausen]

Er ... are you really testing from the public Internet or possibly from an internal (LAN) system and trying to connect to your WAN address? The latter will always work if access from LAN is permitted. Using the WAN destination address does not magically route the connection out and back in again.