Trouble Setting up 2 Vlans on one AP
-
@johnpoz
Don't forget all untagged packets end up on the default VLAN. If your default VLAN is 10 then all untagged traffic will end up on VLAN 10.And to the original poster use 1 VLAN per SSID.
-
@coxhaus said in Trouble Setting up 2 Vlans on one AP:
Don't forget all untagged packets end up on the default VLAN. If your default VLAN is 10 then all untagged traffic will end up on VLAN 10.
huh?? Not sure what your talking about. The traffic will end up on the vlan you set the pvid to..
-
@shclark3 The 2100 and other models with the built in switch are new to me and seem a bit more complicated than "vanilla pfsense". But I wonder, do you really need to use 802.1q mode? As far as I understand it, you already have full VLAN capability in Port VLAN mode (default). All you need is the first section under Interfaces > VLAN and then assign them to your LAN port the way you have done it already.
What you may want to check is that you have configured each interface correctly with their individual subnets and that each DHCP server is correctly configured for the different VLANs...Also, it may be good to know that your EAP650 is Omada compatible so you can manage that and any other Omada devices from one central UI (Omada SW Controller) which you can install on a Raspberry Pi, a PC or a VM if you want.
Going forward, if you want evolve your network and use VLAN's, I'd consider replacing the Netgear switch with an Omada switch which will simplify things greatly. -
@Gblenn I think I'm going to return the net gear. and do just that today.
I had to remove it from the equation and the AP is now just on a POE injector connected to the PF SENSE. The thing is It's still not working the way I would like it to. I have both vlans operational. However I lose the ability to access the AP. I cannot send untagged traffic to it. Whenever I add vlan1 back I am then unable to connect anything to the AP's I can configure the AP again.. but the ability to use the AP is gone. I have to then remove vlan1 and then it works again. I thought you could have one untagged member but it just doesn't seem to work that way.Also very difficult to troubleshoot when working from home. then you have a wifi hungry wife and kids.. and well they don't like you messing with their internet.
-
@shclark3 You can for sure have 1 untagged network on an interface..
My AP management IP is like that.. they don't have a gui on them.. Because they are managed by the controler. Also on this untagged vlan.. In my setup this is vlan2 on my switch, and my APs also handle multiple ssids via tagged vlans.. But to them this untagged vlan is vlan 1 (their default).. Since this is untagged doesn't matter.. My switches manages this vlan via vlan 2 to them.
-
@shclark3 said in Trouble Setting up 2 Vlans on one AP:
@Gblenn I think I'm going to return the net gear. and do just that today.
I had to remove it from the equation and the AP is now just on a POE injector connected to the PF SENSE. The thing is It's still not working the way I would like it to. I have both vlans operational. However I lose the ability to access the AP. I cannot send untagged traffic to it. Whenever I add vlan1 back I am then unable to connect anything to the AP's I can configure the AP again.. but the ability to use the AP is gone. I have to then remove vlan1 and then it works again. I thought you could have one untagged member but it just doesn't seem to work that way.Also very difficult to troubleshoot when working from home. then you have a wifi hungry wife and kids.. and well they don't like you messing with their internet.
I think you should try to simplify things further, and perhaps see if you can go back to VLAN Port mode on your 2100 (default settings)?
You really shouldn't have to mess with VLAN tag 1 at all in this case... Perhaps someone else can help you more with the specifics about setting up things under the Switch section on the 2100. Or check out this video... it's for an 1100 but it should be pretty much the same and may provide some assistance. I beleive when Lawrence refers to group 0 being the switch on a chip, that would be group 5 in your case??
Youtube Video -
@johnpoz said in Trouble Setting up 2 Vlans on one AP:
@shclark3 You can for sure have 1 untagged network on an interface..
My AP management IP is like that.. they don't have a gui on them.. Because they are managed by the controler.
Yep, that is what you get with that TPLink EAP650 if you run the Omada Controller SW, and of course any Omada switches as well. So simple to manage compared to going into the UI of each single device.
-
@shclark3 said in Trouble Setting up 2 Vlans on one AP:
@Gblenn I think I'm going to return the net gear. and do just that today.
I had to remove it from the equation and the AP is now just on a POE injector connected to the PF SENSE. The thing is It's still not working the way I would like it to. I have both vlans operational. However I lose the ability to access the AP. I cannot send untagged traffic to it. Whenever I add vlan1 back I am then unable to connect anything to the AP's I can configure the AP again.. but the ability to use the AP is gone. I have to then remove vlan1 and then it works again. I thought you could have one untagged member but it just doesn't seem to work that way.Also very difficult to troubleshoot when working from home. then you have a wifi hungry wife and kids.. and well they don't like you messing with their internet.
You need to configure the Management VLAN. Iknow TP-Link has such a setting.
-
@NightlyShark said in Trouble Setting up 2 Vlans on one AP:
@shclark3 said in Trouble Setting up 2 Vlans on one AP:
@Gblenn I think I'm going to return the net gear. and do just that today.
I had to remove it from the equation and the AP is now just on a POE injector connected to the PF SENSE. The thing is It's still not working the way I would like it to. I have both vlans operational. However I lose the ability to access the AP. I cannot send untagged traffic to it. Whenever I add vlan1 back I am then unable to connect anything to the AP's I can configure the AP again.. but the ability to use the AP is gone. I have to then remove vlan1 and then it works again. I thought you could have one untagged member but it just doesn't seem to work that way.Also very difficult to troubleshoot when working from home. then you have a wifi hungry wife and kids.. and well they don't like you messing with their internet.
You need to configure the Management VLAN. Iknow TP-Link has such a setting.
You don't need to, but you can if you want. Without any changes it should definitely be accessible as before via the IP it has picked up.
-
First, configure mvneta1 interface with an IP address in a MGMT network that you choose (not vlan). And use this same network in the switch and AP for management purposes.
Checking your screenshots, everything seems to be correct at the pfSense side.
Check your netgear, make sure the MGMT network is correct (untagged) and in the same network as mvneta1 in pfsense, check if this same port is configured to receive vlan20 and vlan30 tagged, and the downlink has the same configuration.The port connecting pfSense to Netgear switch should be like this:
VLAN 1 Untagged (MGMT of the switch)
VLAN 20 Tagged
VLAN 30 TaggedNetgear Switch to AP:
VLAN 1 Untagged (MGMT of the AP)
VLAN 20 Tagged
VLAN 30 taggedThen, assign the wifi networks to use VLAN 20 and VLAN 30 respectively.
