Creating a Guest Wired & Wireless Network for Guest & IoT Traffic
-
I was looking over my pfSense configuration and I think it is not totally correct.
Pfsense Configuration
1. On the Transit Network (VLAN 2000) uplink from the Juniper switch to Pfsense, add VLAN 30 to the Transit network. So, this will become a trunk port with VLAN 2000 and VLAN 30 as tagged traffic.
2. On the LAN interface in Pfsense, I need to create VLAN 30. This will become a subinterface off of the LAN interface.
3. I can now create an interface for VLAN 30 and create the routing, firewall, and NAT rules for the VLAN 30 interfaceIf I trunk the Transit network (VLAN 2000) and add VLAN 30 (Guest VLAN) to it, both VLANs will be tagged. So in addition to creating a subinterface on the LAN interface in pfSense for VLAN 30, I will now need to create VLAN 2000 in pfSense as well. VLAN 2000 will be the assigned to the original LAN interface. Does that sound correct? Please advise.
Got pfSense working.. I created VLAN 2000 in pfSense as well and assigned it to the original LAN interface. All the routing and firewall is now working for the LAN interface. Will be configuring the GUEST interface (VLAN 30) shortly.
I can't get the Guest network in pfSense working. I am testing using a wired connection. I configure a static IP address on my laptop (192.168.30.10) and connected directly into the switch port that is configured for VLAN 2000 (Transit network) and VLAN 30 (Guest network).
I have attached all the Guest network configuration in pfSense. It seems as though pfSense is not receiving VLAN 30 traffic.
-
So tag VLAN 30 through to the client. Client should be on an untagged port on VLAN 30.
This isn't rocket science.
If pfSense is not receiving traffic on that port on VLAN 30 then it's your switch/layer 2 that isn't passing it.
You obviously need DHCP on GUEST (unless provided from something else) and firewall rules passing the traffic into GUEST for anything to work.
-
So tag VLAN 30 through to the client. Client should be on an untagged port on VLAN 30.
This isn't rocket science.
If pfSense is not receiving traffic on that port on VLAN 30 then it's your switch/layer 2 that isn't passing it.
You obviously need DHCP on GUEST (unless provided from something else) and firewall rules passing the traffic into GUEST for anything to work.
For some reason, my DHCP setup on VLAN 30 on the Juniper switch is not working. Maybe because VLAN 30 is not setup for inter-vlan routing.
I created the Guest SSID on the UniFi AP and assigned it to VLAN 30. I went ahead and setup DHCP on the pfSense box and when I connect to the Guest SSID, I can now access the internet. Traffic to the other subnets is blocked as well. So, major progress. I will tinker with it more tomorrow. Thanks everyone…
-
I said earlier that you can probably not run a DHCP server on the switch without an RVI.
-
Is there any reason to assign an IP address to the Guest Vlan (VLAN 30) created on the Juniper switch? Right now I assigned it "192.168.30.1" but I am not sure if it is serving any purpose. On the pfSense box, the Guest interface (VLAN 30) has been assigned IP address "192.168.30.2".
-
No. I specifically said NOT to create one. You want the firewall to route traffic, not the switch.
-
No. I specifically said NOT to create one. You want the firewall to route traffic, not the switch.
Everything is working now. Thanks for the help.
-
Rules allowing access from the other subnets to the guest network will be on the transit interface (vlan 2000).
The attached is pretty basic but generally works for limiting guest access.
My local_nets_v4 includes some repetition. Blocking RFC1918 is probably sufficient unless you have inside networks on public IP space.
How did you create the local_nets_v4 table?
-
I created a Firewall Alias and it worked for me…
-
Got everything working.. I may tinker with the firewall rules on the Guest network some more…
Here is the final drawing. Thanks everyone.
-
Why are you calling it lan vip and dmz vip? Sounds like to me you are running 2 different layer 3 networks on the same layer 2??
-
Why are you calling it lan vip and dmz vip? Sounds like to me you are running 2 different layer 3 networks on the same layer 2??
Sorry about the confusion. The drawing is not correct. For the DMZ, I will have separate Layer 3 switch. It is currently not setup yet….
I will update the drawing the reflect the separate Layer 3 switch for the DMZ and it's uplink to pfSense.
-
Here is the correct drawing with the proposed DMZ setup. Once again, I have not installed the DMZ switch yet.
-
johnpoz … Do you see anything weird about my proposed DMZ setup?
-
Why are you doing layer 3 for 1 segment?
Still don't understand while on pfsense your calling lan and dmz VIPs?
Calling gateways out near your pfsense - looks like those are gateways setup on pfsense vs just the pfsense IP..
-
Why are you doing layer 3 for 1 segment?
Still don't understand while on pfsense your calling lan and dmz VIPs?
Calling gateways out near your pfsense - looks like those are gateways setup on pfsense vs just the pfsense IP..
Since I have an extra Juniper switch, my plan is to use it and perform routing on the switch. I guess I could purchase a cheap managed Layer 2 switch for the DMZ.
As for the VIP, I guess I should call it CARP or cluster IP and not virtual IP.
I will cleanup the gateway information on the drawing.
-
Routing to what? Just because a switch can do L3 doesn't mean you have to do it ;)
You have the DMZ segment on it, what exactly is it going to route to other than pfsense?
-
Routing to what? Just because a switch can do L3 doesn't mean you have to do it ;)
You have the DMZ segment on it, what exactly is it going to route to other than pfsense?
Updated drawing of the DMZ setup based on your recommendation. Opinion please.
-
idk why you are bothering with the separate DMZ switch. I'd probably just tag that on the existing trunk to the other switches.
-
idk why you are bothering with the separate DMZ switch. I'd probably just tag that on the existing trunk to the other switches.
Based on your recommendation I would:
1. Create a DMZ vlan (i.e. VLAN 70) on the existing Juniper switches. Do not create a RVI or assign the VLAN an IP address. Routing will be handled by pfSense.
2. Trunk the DMZ vlan (Vlan 70) on the existing uplink to pfSense.
3. Create a subinterface in pfSense over the LAN interface for the DMZ VLAN (Vlan 70). Just like I did for the Guest VLAN.
4. Create the firewall rules, NAT rules, etc. in pfSense for the DMZ interface.One more thought…
I do have an extra port on my pfSense boxes. So, I could create another uplink from my existing Juniper switches to the pfSense boxes. That why I am not trunking the DMZ Vlan on the LAN interface to pfSense.
