I am running PFSense in VMBox in windows on a mini PC with 2 nic. The VMBox is running both nic in bridge mode. It feeds into a TL-SG108E 6.0 and then two ports are lag to a netgear AP. I have watched the video about how to set up the switch and VLANs 20 times and still having issues with VLAN tagging working.
I think it is the switch because when I turn one of the ports PVID to the tag like in the video it cannot pull an IP. I change an SSID on the AP to add a VLAN tag and nothing. I’ve reset everything twice. New to this so any ideas would help.
No idea what is happening on your box, however, I would install pfSense on bare metal then connect your switch with the vlans, then test each vlan on your switch with your laptop. If that all works, then set up your AP. If that works then backup your config and virtualise pfSense next.
I agree with @neogrid that trying this on hardware directly would remove a layer of complexity in figuring out where the issue is. My suspicion is that the trouble lies in the VLAN setup on the switch (like you guessed). Could you add some info about how you’ve set that up?
Specifically, do you have a trunk set up between pfSense and the switch (on both sides) and how are you tagging VLANs on the interface to the AP?
Don’t have a spare bare medal laying around to do this on. I set up the switch like the video by adding a VLAN 30 tag. I set up the VLAN on pfsense on the interface and turned on DHCP services. And then tagged it on the TP Link Switch. Even if I PVID a port a plug a laptop in, it doesn’t pull anything.
I did that and rebooted pfsense and the switch. I get nothing and also the switch appears in the DHCP as not online even though I can pull it up and manage it.
I don’t know this switch, so sorry if I’m reading it wrong, but it looks to me like port 4 on your switch is listed as untagged both for VLAN 1 and 30, which shouldn’t work. On any switches I’ve used, you can only have one VLAN untagged per port.
If that doesn’t solve anything, I’d start looking at the VM’s networking features. It could easily be some craziness in there that’s not passing tagged traffic from pfSense through to the switch.
