Blocking inter vlan traffic blocks access to website
-
This post is deleted! -
You have to pass traffic to the private addresses and ports you want passed before blocking access to the server VLAN on the firewall rules on the GUEST interface.
NAT happens before firewall rules are checked.
So if your web server is 192.168.1.100 ports 80 and 443 you would do something like this on the GUEST interface:
pass tcp source GUEST net dest 192.168.1.100 port 80
pass tcp source GUEST net dest 192.168.1.100 port 443
reject any source GUEST net dest SERVER netAs a trailer I would also say it would be better to pass traffic to "this firewall" that they need access to (like DNS) then block everything else to "this firewall" instead of just blocking the management ports.
That way things can change (like changing the webgui port) and you are still secure without having to remember to change that alias.
-
This post is deleted! -
This post is deleted! -
If it works with SERVER Net and not specific addresses I would posit you are using the wrong addresses.
You might want to post the actual port forwards and firewall rules. Should only be necessary to post the GUEST rules.
Configure it to something you think should work but doesn't and post that.
-
This post is deleted! -
Does Diagnostics > Tables look sane when you examine the exchange table?
Is the DNS answer the public WAN address or the inside address?
What does the port forward on WAN look like?
-
This post is deleted! -
Well, yeah. There's your problem.
What DNS servers do you want pfSense itself to use to resolve names?
Do any clients rely on pfSense for DNS server functionality?
-
This post is deleted! -
If you do not need any DNS services on pfSense:
Set the DNS servers you want pfSense itself to use in System > General
Make sure DNS server override is unchecked
Check Disable DNS Forwarder (removes 127.0.0.1 from the list of nameservers)
Disable both DNS Forwarder and DNS Resolver in Services.
-
This post is deleted!