This setup was quick, easy, and worked! However, maintenance was a pain as I now had 3 new SSIDs that I needed to track the passwords for and getting devices onto the new network(s) – and any future devices – was a pain. Iteration 1 of the setup was to create 4 VLANs (Trusted, Guest, IoT, and Kids) and have them map to different SSIDs and manually specify the port VLAN on the switches – using a VLAN trunk for the wired APs and the link aggregation to the router. Do I need 4Gbps between the router and the switch? Probably not, but I’m not using the ports anyways, and why not?! Additionally all the APs have a wired uplink to the switch. 1 Qotom 6-port i5 mini-PC running pfSense Community Edition 2.6.0īetween the Qotom and the switch I have a 4-port link aggregation.My home networking consists of the following equipment: Good thing I have all the technology required to lock this down! I knew this day would come but was just surprised it had come so fast/soon. the fallback) look like the following: DEFAULT Huntgroup-Name = '', Auth-Type := Acceptīack to our “midnight surfer” – I woke up one night to some giggling to find my son had decided to use an old phone we have to watch tiktok videos. So, have your last user in the user’s config file (i.e. Instead, you should use the fallback network in the switch config and scope the Default user to only authenticate for devices on the APs via a huntgroup. This is regardless of specifying a fallback network in the switch configuration or not. TL DR – Having DEFAULT Accept auth-type that assigns a specific VLAN, works for WLAN clients on Unifi APs but does not work for MAC-based authentication on Unifi Switches. I’ll give a bit of an abbreviated journey so you can relive the fun, but the important takeaway is how to do MAC-based port authentication on the switch while also doing it on the WLAN, and having both have the same fallback VLAN. We may have had an issue with a young “midnight surfer” on the internet one night, and it has since taken me a wild ride of VLANs, schedules, traffic shaping, RADIUS servers and SSIDs. Hopefully this helps someone else out there. The printer has been online for over 20 days, whereas before it would fall off the network sometimes before it even fell asleep. Also require clients to use rates at or above the specified value: ▢.Group Rekey Interval: GTK rekeying every 3600 seconds.Broadcasting APs: I have it set to just the 1 where closest to the printer.With the above article in hand, I created a new SSID that was only on the 2.4Ghz with the following settings (Unifi Controller 7.0.23):

That at least gave me some hope, as I was using a single SSID for both 5Ghz and 2.4Ghz – you know, like a sane person. After a bit of searching, I stumbled upon this Brother article (granted I’m printing from a Windows PC and my specific printer is a Brother MFC-L2750DW). After enough frustration, I finally took some time to sit down and fix the problem.

Cloudberry server on synology