wan gui access

Started by cerien, March 23, 2020, 09:19:06 PM

Previous topic - Next topic
Hello
I am discovering opnsense 20.1, and I have installed it on a vm in my lan, with 2 interfaces, LAN 192.168.1.1, and WAN 192.168.2.xxx - fresh install from the iso.
I am trying to access the management gui via the wan port - In system/settings/administration, I've defined listend to all ports for webgui, etc...
Interfaces WAN : I've unblocked private networks (and bogon networks, just in case !)
I've added a firewall rule, wan,  source any, destination wan address, port https
No luck - when I connect to the WAN IP, no gui comes up !
In the logs, I see my rule being triggered, in green, but not gui.

Out of despair, I've done the same config on a fresh pfsense, immediate success !
I've tried adding a nat rule, port forwarding to 192.168.1.1, no luck

Any ideas ? what could be wrong ??

J.

I have seen similar behaviour. Can you please try to remove the gateway and test again?
Twitter: banym
Mastodon: banym@bsd.network
Blog: https://www.banym.de


Mâââgic ! It does indeed work now. I'd love to understand why ! And, how can the lan network now access the WAN ?

Many thanks for your help !

Would love to see some answer from the developers on that matter, I do not think it is intended.

The lokal traffic should always be answered directly on any interface and not sent to the upstream gateway. But thats just my understanding of TCP/IP and I can be wrong and it has a reason why it is implemented that way.
Twitter: banym
Mastodon: banym@bsd.network
Blog: https://www.banym.de

as a reference, if someone else has this setup, a good workaround is to declare a 2nd ip adress on the interface of the computer trying to access the gui:
for instance:
ifconfig wlp2s0:0 192.168.1.10 netmask 255.255.255.0 up
and then, the machine can access the gui