Trying to access modem GUI through WAN port

[hushcoden]

As per subject, I'd like to be able to log in to modem GUI via WAN port, but (and sorry if it's a dumb question) I don't understand how to configure OPNsense.

First thing, I don't have a 'local' address for my WAN port (I've attached screenshots of the configuration) and I was thinking that if I was able to assign the WAN port an IP in the same subnet as LAN, I should be able to do so: my OPNsense IP address is 192.168.0.1 and my LAN addresses range through DHCPv4 is 192.168.0.2 - 192.168.0.50

Appreciated some help.

Tia.

[chemlud]

Done that in the past:

https://forum.opnsense.org/index.php?topic=12094.msg55412#msg55412

[hushcoden]

Thanks, still not working - I'm not networking savvy :-)

What I did:

1) Interfaces --> WAN --> unchecked "Block private networks"

2) Firewall --> NAT --> Outbound --> see attachment  -- 192.168.2.1 is the modem IP address

What else I'm missing?

[hushcoden]

Solved following this https://docs.netgate.com/pfsense/en/latest/recipes/modem-access.html

[hushcoden]

Sorry to resurrect an old thread, but I have a fresh install - 21.7 - and nothing seems to work: hardware is still the same but I can't access the modem GUI, any suggestions?

Tia.

[chemlud]

As always: What EXACTLY have you configured how (screenshots) and what are the error messages you get when you do what?

[hushcoden]

As always: What EXACTLY have you configured how (screenshots)

I followed the same article I posted above which worked when I was using the 21.1 - see attachments

Modem IP address = 192.168.2.1

OPT2 = 192.168.2.10/32

and what are the error messages you get when you do what?

Simply the connection times out and no modem GUI

[chemlud]

I just tried it on 21.7.1:

Add for WAN a manual outbound NAT rule for the network your modem uses, press Apply, enter IP of modem in same browser: Reach GUI of modem. No problem here...

I guess your modem doesn't use a /32, more likely a /24 (192.168.2.0 /24). Check manual/settings of modem :-)

[hushcoden]

I've found the culprit  8)  I've changed the IP address of the OPT2 (WAN) interface from 192.168.2.10/32 to 192.168.2.10/24 and now it works !