Which AccessPoint would be recommended - Multiple or Single SSID
-
@johnpoz Yes, it can do it as well in the standalone mode. But if you pair it with the controller you can have variable VLANs
-
@gamienator-0 said in Which AccessPoint would be recommended - Multiple or Single SSID:
But if you pair it with the controller you can have variable VLANs
Its not that it can't do them - its the administration, and limit of devices that can not send the auth to assign them.. Just trying to save you some headache.. iot devices do not support enterprise - And to be honest billy coming over his laptop or phone doesn't just auto use a different eap other then psk..
Dynamic vlans don't help you with dlna - if that what your thinking.
-
@gamienator-0 said in Which AccessPoint would be recommended - Multiple or Single SSID:
There is a multicast bug in the firmware
That TP-Link multicast bug is still around? I had it in an AP I bought 11 years ago, which prevented me from running IPv6 on my guest WiFi. It also affected some switches. I recall when I tried to get it fixed, the support said it worked the way it was supposed to, but I eventually reached 2nd level support, who agreed it was a bug. There never was an update for mine, so I wound up getting a Unifi AC-Lite a couple of years ago.
-
@johnpoz thank you about that very much. I’m just really curious if I’m able to do that.
To separate my network was a long to do, cause I trust don’t trust a couple of my devices like my LED Controller, washing machine or TV. Since then I have to tinker with mDNS, Multicast anyway. One SSID for all is the cherry on the top. I don’t mind using PSK and with a MAC access list.
-
@gamienator-0 said in Which AccessPoint would be recommended - Multiple or Single SSID:
Since then I have to tinker with mDNS, Multicast anyway
And why is that? I have all my iot stuff in a IOT vlan - have to do zero with mdns or anything with multicast.. What exactly are you wanting to do that requires mdns or multicast - I love how people say they don't trust something and throw up a barrier, and then just break it anyway ;)
-
Mmm, for me using multiple SSIDs, one for each VLAN, is significantly simpler to setup and manage than trying to apply VLANs to clients based on auth or MAC.
-
@stephenw10 exactly - now if I had vlans for every dept and had like 20 dept or something in an enterprise - for sure would use 802.1x and dynamic vlans etc..
But for iot, or washing machine, tV - just throw them in iot SSID vlan and there you go.. If you don't want them talking to each for example just use a AP/Client isolation on your AP, or if wired private vlans on your switch, etc.
-
@johnpoz said in Which AccessPoint would be recommended - Multiple or Single SSID:
@gamienator-0 said in Which AccessPoint would be recommended - Multiple or Single SSID:
Since then I have to tinker with mDNS, Multicast anyway
And why is that? I have all my iot stuff in a IOT vlan - have to do zero with mdns or anything with multicast..
Well I still want to use them, for example on my TV, there is a DLNA Client. For that I want him to see my NAS, but only that for example. And AFAIK I need to Setup proper multicast forwarding.
-
@gamienator-0 said in Which AccessPoint would be recommended - Multiple or Single SSID:
for example on my TV, there is a DLNA Client
For what service - while DLNA makes it easy for grandma - if you know what its wanting to talk to, say plex server or something - just allow that port through your firewall.. Jumping through hoops and punching discovery/multicast holes in your network security because you don't want to open 1 port from a specific client to a specific destination is a going the wrong direction from a security point of view with firewalling and segmentation of your network if you ask me.
If X needs to discover Y to work - I wouldn't trust either of them and would put them on the same network.
-
@jknott said in Which AccessPoint would be recommended - Multiple or Single SSID:
@gamienator-0 said in Which AccessPoint would be recommended - Multiple or Single SSID:
There is a multicast bug in the firmware
That TP-Link multicast bug is still around? I had it in an AP I bought 11 years ago, which prevented me from running IPv6 on my guest WiFi. It also affected some switches. I recall when I tried to get it fixed, the support said it worked the way it was supposed to, but I eventually reached 2nd level support, who agreed it was a bug. There never was an update for mine, so I wound up getting a Unifi AC-Lite a couple of years ago.
This is exactly why you should stay away from tp-link, linksys, d-link and the likes.
Firmware updates are scarce - if they even exist.