Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
19.1 Legacy Series
»
WAN admin - Firewall Allow but Blocked
« previous
next »
Print
Pages: [
1
]
Author
Topic: WAN admin - Firewall Allow but Blocked (Read 2963 times)
Deku2
Newbie
Posts: 30
Karma: 1
WAN admin - Firewall Allow but Blocked
«
on:
April 17, 2019, 05:25:34 am »
I have a situation where I need to enable web administration on the WAN. I've done this before without issues. Go to console, shut down packet filter, set WAN firewall to allow my source IP to destination WAN address port 443. Restart pf.
I just installed a new install of opnsense yesterday, but I can't get this to work. I'm able to stop pf from a remote console and then access the WAN web admin, but after adding the WAN firewall rule (even to the point of ANY ANY), when pf restarts, I'm blocked by the default fw block rule. Any thoughts why this would happen?
I know best practice is to vpn or something and access via the lan (and I'll get to that), but I need this to work on the wan first to set everything up properly. Also, web admin is enabled for all interfaces.
Logged
Deku2
Newbie
Posts: 30
Karma: 1
Re: WAN admin - Firewall Allow but Blocked
«
Reply #1 on:
April 18, 2019, 09:15:29 pm »
I'm not sure if this is normal, but I got it to work and I'll explain.
My WAN was set with an IP of 10.x.x.1 and my LAN 192.168.x.1. I disabled the option that would block private or bogon networks. I allowed any any to access 10.x.x.1 any. I was not able to connect to the web admin unless I went to the console and did a 'service pf onestop'.
I changed the WAN IP to a internet facing ip range and put it online. Now it works without issue and I've tightened up the source ip and destination port in the rules. Why would it not work with a 10.x.x.x assignment? I was accessing it from that network. Anyway.. figured I'd post in case others had a similar issue.
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
19.1 Legacy Series
»
WAN admin - Firewall Allow but Blocked