MatthewL Posted December 18, 2019 Posted December 18, 2019 Got a slight VLAN issue with my pFsense setup, cannot get my DHCP scope working on my Guest VLAN SSID on Site B. Sites linked via an OpenVPN tunnel and can see and communicate with everything. Site A Firewall - 192.168.20.253 Unifi Controller - 192.168.20.251 Site B Firewall - 192.168.30.253 Switch - 192.168.30.252 linked via port 8 to firewall Unifi AP - 192.168.30.245 linked via port 1 to switch SSID 1 - works fine and issues DHCP 192.168.30.0/24 SSID 2 - is VLAN ID 3666 DHCP scope setup on pFense, should be dishing out 10.254.254.0/24 Ports 1 and 8 (WAP & Uplink) on switch tagged with VLAN 3666 VLAN setup on pFsense with DHCP options in, I use a Netgate SG-1100 at site B, it has a WAN, LAN & OPT port, switch plugged into LAN. This is the VLAN setup on the port, I know I need to add 3666 into this but on on the members which wants to be tagged (t) or untagged as I thin this is the issue? Any thoughts?
ibpalle Posted December 20, 2019 Posted December 20, 2019 I assume PFSense is the DHCP server on both sites or are you using relay to have one DHCP server for both sites?
mavhc Posted December 20, 2019 Posted December 20, 2019 Untagged ports expect traffic with no VLAN information, then the switch adds that information as the packet arrives. Tagged means it's expected packets with VLANs already in. So depends on if the devices connected to it already know what vlan they're using (tagged) or if they're unaware of vlans (untagged)
MatthewL Posted December 20, 2019 Author Posted December 20, 2019 Yes pfSense is DHCP server. I will have another look and see where I am going wrong. Think its to do with the port the switch is connected back into the pfSense box.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now