XG-7100, Ubiquiti Unifi AP and VLAN configuration
-
AP connected (via POE switch) to port 3.
-
You need VLANs 100 and 200 both tagged on uplink ports 9 and 10 (Interfaces > Switches, VLANs). pfSense will not see the traffic unless you send up the uplink ports.
You have to decide how you want to talk to the APs. I hear that they have managed to finally add a management VLAN to the code so that is now an option.
Traditionally you would manage the APs on an untagged VLAN and use tagged VLANs for wireless networks. Nothing stopping you from putting a wireless network on the untagged VLAN either.
You have to decide what is tagged and what is untagged and where and make the switching layer (including the switch in the 7100) do that.
On my inter-switch link I would tag all traffic but I am a little "funny" that way.
-
Thank you for that. I now have 9t and 10t on VLAN 100/200.
It is now possible that I am further confusing myself/the problem ;)
If I plug the AP in to port 8 (VLAN 200) and connect to 'M' (also VLAN 200), I connect and get an IP address. If I connect using a wireless network sans VLAN, they also connect to VLAN 200 and I get an IP address. However, another wireless network with VLAN doesn't connect/challenge for credentials. I have tried this tagged and untagged, same result.
If I plug the AP in to port 2 (tagged on default VLAN 4091), the wireless networks disappear. Odd!
Back in any of the untagged VLAN default 4091 ports (3 thru 6) and I can connect but only with wireless networks without VLAN.
There is likely something obvious that I am missing, just can't quite see it at the moment.
-
Port 8 is shown there as both tagged and a PVID on VLAN 200. Honestly, I don't know what the switch would do with that but your description would be a distinct possibility (both tagged and untagged input traffic being on VLAN 200) and tagged 200 on the uplinks.
Allow me to state again:
You have to decide how you want to talk to the APs. I hear that they have finally added a management VLAN to the code so tagging that on the AP ports is now an option. I have not seen that personally yet.
Traditionally you would manage the APs on an untagged VLAN and use tagged VLANs for wireless networks. Nothing stopping you from putting a wireless network on that untagged VLAN either (Don't set a VLAN in the wireless network configuration).
Traditionally you would set the "management" VLAN to be both untagged and the PVID on ETH8, tagged on 9 and 10. Then you would set the SSID VLANS as tagged on ports 8, 9, and 10.
They would correspond to pfSense interfaces VLAN 100 on lagg0 and VLAN 200 on lagg0 for assignment, firewall rules, DHCP servers, etc.
-
Don't get me wrong, I am very grateful for your help, but like I said at the beginning, this is my first foray in to the world of VLAN and I am still learning the language and know I have a way to go before I understand it.
I guess what I was trying to get was an example configuration that I could replicate. I have seen a number around and am still reading through those to better understand them and the terms used.
Being honest, I am not fully understanding your penultimate statement. First you mentioned '"management" VLAN to be both untagged and the PVID on ETH8, tagged on 9 and 10' and then 'SSID VLANS as tagged on ports 8, 9, and 10' which appears to read as port 8 being both untagged and tagged at the same time. Like I say, for now, I am trying to learn the language but at the same time establish a working setup.
Not wanting to repeat myself, but I want it to be clear, I am very grateful for your responses and help both you and the others have given thus far.
-
Well, you cannot expect a complete course in the ISO model and network design on a forum.
People tend to think that they should be entitled to a complete education in the subject matter at-hand just because they purchased a product capable of such things.
That is not true.
If you do not know, you should hire someone who does. Just like you would if you bought a car and needed to change the transmission.
-
Hmm, OK. Not sure I have expressed any level of entitlement. But if that is what you think, that is your prerogative.
Yes, I have purchased a Netgate product. No, I do not expect free courses on firewall configuration as a consequence of that purchase. I am not an expert nor do I do this for a living. Yes, I have configured firewalls for my needs over a number of years, both hardware and software ones. No I haven't used VLANs, so that is now on my list of things to know more about.
Thank you for your observation on the uplink ports, that helped. But it appears that being a hobbyist and wanting to learn is not sufficient.
I should add that in my youth, I worked on many cars (as a hobbyist with my Dad) and replaced many a part, including a gearbox on one occasion.
-
I told you exactly what you need to do here:
Traditionally you would set the "management" VLAN to be both untagged and the PVID on ETH8, tagged on 9 and 10. Then you would set the SSID VLANS as tagged on ports 8, 9, and 10.
They would correspond to pfSense interfaces VLAN 100 on lagg0 and VLAN 200 on lagg0 for assignment, firewall rules, DHCP servers, etc.
-
Yes you did :)
Over the weekend, I had a little more time to digest what you said and have now managed to get what I was after, so thank you for your help.
The only problem now is with getting RADIUS assigned VLANs on the AP. I found comments about enabling "Tunneled Reply" in EAP, which I have done and the response appears correct, but no joy so far. Job for another time.
-
Using dynamic VLANs will require all of those VLANs to be tagged and configured to pfSense.
But if that is the case it is likely just a matter of getting the correct RADIUS Reply Attributes from the RADIUS server to the AP and/or Controller software. (not sure what is actually talking to the RADIUS server on the UBNT gear)
