Create a guest network with VLAN tag 1003
-
No way to know without knowing what that LOCAL_NETWORKS Alias and those port aliases are. Those rules don't make much sense.
What are you trying to do here?
I personally despise "blocking" traffic with pass ! rules. Hate it. Loathe it. Wish it would die in a fire.
If you want to block it, just block it. Then pass any.
![Screen Shot 2018-01-01 at 3.50.23 PM.png](/public/imported_attachments/1/Screen Shot 2018-01-01 at 3.50.23 PM.png)
![Screen Shot 2018-01-01 at 3.50.23 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2018-01-01 at 3.50.23 PM.png_thumb) -
No way to know without knowing what that LOCAL_NETWORKS Alias and those port aliases are. Those rules don't make much sense.
What are you trying to do here?
I personally despise "blocking" traffic with pass ! rules. Hate it. Loathe it. Wish it would die in a fire.
If you want to block it, just block it. Then pass any.
local_subnets
These rules aren't mine really. Straight from a guide. Would be glad for any suggestions to simplify them.
As far as what I want to accomplish. I have 2 airports that are configured with a WPA2 “Home Network” which works and a “Guest Network” which shows “no internet”. I’m trying to setup a vlan that will allow guest connections to DHCP server and WAN only, without interfering with the “Home Network” which needs full access to local networks.
-
Just because it's in a "guide" doesn't mean it's correct.
You only gave half the picture. What destination ports are you passing?
-
Just because it's in a "guide" doesn't mean it's correct.
You only gave half the picture. What destination ports are you passing?
Not sure what you mean by destination ports?
-
-
I would disable those rules and add a pass any any rule. Does it work? Then you are not passing traffic you need to pass.
You do realize that you will be unable to ping with that configuration because it is not passed, right?
I can be confident that pfSense is behaving exactly as it is being instructed to behave.
Check the firewall logs for what is being blocked and evaluate whether it should be passed and pass it or don't.
-
I would disable those rules and add a pass any any rule. Does it work? Then you are not passing traffic you need to pass.
Thanks. Makes a lot of sense. Maybe one of these days I’ll learn to quit following these online step-by-step guides.
-
Think I've got everything working now. Thanks @Derelict. Guest network has access to DHCP Server and WAN but no access to firewall or LAN (only other local network currently).
The firewall rules may need some tweaking. Any advice? I checked pinging, that works.
Edit: Caught my mistake with the "Block LAN Access" rule order. It's now one above "Allow Any".
-
Your Allow any rule will pass all traffic and nothing below it will have any effect.
-
Your Allow any rule will pass all traffic and nothing below it will have any effect.
Are you saying I should modify “allow any” or delete the rules below it? Or both?
-
What he is saying is rules are evaluated top down, first rule to trigger wins - no other rules are evaluated.
Anything below an any any allow is pointless since no traffic will ever make it to that rule since the any any allow will pass the traffic. You need to place your rules in the correct order top down so they evaluate how you want them to evaluate.
-
Thanks. Actually, I understood that. Should have been more specific.
I can see that the default block rules aren’t going to do anything. If I move the any-any rule below them then it won’t do anything. Since I’m a noob at this, I’m not sure if I should modify the any-any rule or just delete the default block rules? My intent with this rule is to allow unlimited acces to the internet.
-
there is a default deny rule anyway.. There is no reason to create your own rule unless have turned off logging of the default rule and would still like to log stuff that makes it through your rules that you block that meet some specific criteria you setup in the block rule that would be different than default deny, etc. Or if you only want to log stuff on specific lan side interfaces and have turned off the logging of the default deny rule that is on all interfaces.