Create a guest network with VLAN tag 1003

wgstarks · Dec 31, 2017, 4:27 AM

Why are you creating a VLAN for desktops etc.? Normally, those don't need a VLAN, so you'd have to set up access ports on VLAN 10. Also, each VLAN in pfSense appears as a separate logical interface, which you'd use as any other interface. The rules etc., will depend on what you want to do.

When I set those vlans up I was using a guide that I modified slightly to meet my needs. That’s all up and running except for the guest WiFi. I’m just not sure what I need to do to get pfSense to read the tags. Is this done in the background or do I need to configure a rule to match the packets with the 1003 tag to my guest network?

Derelict · Dec 31, 2017, 7:19 AM

Create a VLAN 1003 on the physical interface to your switch (using eth0 below as an example).

Assign an interface to that VLAN 1003 on eth0 interface.

Create appropriate firewall rules, DHCP services, etc on that interface.

Everything transmitted by that interface will be tagged with 1003. Everything arriving tagged 1003 will be processed by that interface.

Michel-angelo · Dec 31, 2017, 10:23 AM

@wgstarks:

I’m attempting to get my guest network setup on my Airport Extremes and this thread has been very helpful but a couple of things I’m not sure about.

I’m using a Netgear GS724Tv2 switch to create the vlans MAIN_VLAN10 (pvid10) for all my desktops, printers and servers and WIFI_VLAN20 (pvid20) for the Airports. If I’m understanding correctly the Airports will tag guest traffic with 1003?

I will just clarify the airport Extreme (or Express, or time Capsule) side.
When used as a router, an Airport Extreme (and the other new Airport base stations) will be able to *create a guest network by VLAN tagging, assigning the Vlan tag 1003 to packets going to the guest network (ethernet or wireless).
When used as a wifi simple access point, an airport Extreme base station will recognise packets Vlan tagged 1003 and be able to send them to the wireless guest network.
Given that your airport base stations are wifi access points and not routers, none of them will do the Vlan tagging. But they will need it. You need to do it on your guest interface in the pfSense router. pfSense > Interfaces > VlanAssignment > Vlans. I attach a copy of my setup. HTH

wgstarks · Dec 31, 2017, 1:05 PM

@Derelict:

Create a VLAN 1003 on the physical interface to your switch (using eth0 below as an example).

Assign an interface to that VLAN 1003 on eth0 interface.

Create appropriate firewall rules, DHCP services, etc on that interface.

Everything transmitted by that interface will be tagged with 1003. Everything arriving tagged 1003 will be processed by that interface.

Outstanding. That's what I thought. Just wanted to be sure.

wgstarks · Dec 31, 2017, 1:19 PM

@Michel-angelo:

Given that your airport base stations are wifi access points and not routers, none of them will do the Vlan tagging. But they will need it. You need to do it on your guest interface in the pfSense router.

This is all fairly new to me, but I don"t see how this could be? You are able to login to the wifi guest network and also into the regular network that you have setup right? The Airport must have some way to distinguish between the 2 different wifi networks. I would think that the Airport must be applying tags to all traffic entering the guest network via wifi. Of course there's always the chance that I'm completely wrong. :D

johnpoz · Dec 31, 2017, 3:11 PM

My understanding is the guest network on a airport will be tagged 1003.. You need to setup your switching and pfsense correctly to understand that tag..

https://www.thegeekpub.com/5191/use-airport-extreme-guest-network-bridge-mode/
The Airport Extreme Guest Wireless network can be used with almost any other brand of router as your main router, as long is it supports VLANs

wgstarks · Dec 31, 2017, 4:27 PM

@johnpoz:

My understanding is the guest network on a airport will be tagged 1003.. You need to setup your switching and pfsense correctly to understand that tag..

https://www.thegeekpub.com/5191/use-airport-extreme-guest-network-bridge-mode/
The Airport Extreme Guest Wireless network can be used with almost any other brand of router as your main router, as long is it supports VLANs

Thanks. I think I’ve kinda got my head wrapped around the basics of the tag routing now. Having a family day today, but I’ll give it a shot tomorrow and see if I can get it to work.

Thanks to everyone for your help so far.

wgstarks · Jan 1, 2018, 11:12 PM

@wgstarks:

@johnpoz:

My understanding is the guest network on a airport will be tagged 1003.. You need to setup your switching and pfsense correctly to understand that tag..

https://www.thegeekpub.com/5191/use-airport-extreme-guest-network-bridge-mode/
The Airport Extreme Guest Wireless network can be used with almost any other brand of router as your main router, as long is it supports VLANs

Thanks. I think I’ve kinda got my head wrapped around the basics of the tag routing now. Having a family day today, but I’ll give it a shot tomorrow and see if I can get it to work.

Thanks to everyone for your help so far.

Well that didn't turn out too good. I created a VLAN10 (pvid 10) on my switch with associated ports tagged. Created VLAN10_MAIN on my firewall for approved laptops and other wireless devices and created VLAN1003_Guest for guest use.

VLAN1003 should have no access to local network. Only internet. I believe that's working.

VLAN10 needs to have full access to the local network as well as the internet. I can get access to the internet but not the local network.

I'm hoping I've just missed a rule or misconfigured one?

Derelict · Jan 1, 2018, 11:52 PM

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)

wgstarks · Jan 2, 2018, 1:45 AM

@Derelict:

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.

Derelict · Jan 2, 2018, 1:49 AM

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?

wgstarks · Jan 2, 2018, 1:56 AM

@Derelict:

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?

wgstarks · Jan 2, 2018, 2:22 AM

@wgstarks:

@Derelict:

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?

Guess I'm a little slow tonight.:)

Derelict · Jan 2, 2018, 5:12 PM

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.

wgstarks · Jan 2, 2018, 6:02 PM

@Derelict:

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.

wgstarks · Jan 3, 2018, 1:16 AM

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".

Derelict · Jan 3, 2018, 4:46 AM

Your Allow any rule will pass all traffic and nothing below it will have any effect.

wgstarks · Jan 3, 2018, 12:59 PM

@Derelict:

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?

johnpoz · Jan 3, 2018, 1:05 PM

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.

wgstarks · Jan 3, 2018, 1:23 PM

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.