You must be one of the rare .0000001% of network admins that do not experience signal/connectivity/throughput degradation over time. I am not one of those lucky few, and when there's an issue with my Meraki WAPs (or even my Unifi WAPs or home WAP) the first fix is power cycle. That's usually all that is needed to clear out any issues. It would be nice to be able to schedule a weekly rolling reboot of WAPs at a time when nobody is on campus and actively needing the network. ... View more

I'm curious as to what the WAP is plugged in to. Most connectivity issues (working fine, then not with no change) with WAPs come down to a bad wire, a bad switch, or a bad WAP. I had one WAP that would randomly go to repeater mode and then back. Cable was fine, I re-tipped the ends, tried a different port, tried a different Meraki WAP, and always got the same result. I put a different brand WAP in place of it, and within a day I was alerted that the WAP had dropped down to 100mb from the 1000mb. I replaced the Cisco POE switch (SG300-28MP) a different brand of POE switch and haven't had a problem with that WAP since. Meraki does a bad job of defining why a WAP isn't functioning properly in many of these cases.   I've found that the model of switches that I inherited are junk, and have had 3 fail in the last month. Cisco reliability and stability ain't what it used to be! ... View more

On Sept 1, Apple released the 13.7 update that pertains to Covid tracing. My guess, since it's only started happening in the last couple weeks and only to iPhones, is the update is intent on trying to keep the same IP address for continuity of tracking. We all know how that goes when it comes to DHCP requests.   ETA- iOS 14 is only a week old, so while the randomized MAC address might be the issue, it wouldn't have started a couple weeks ago. ... View more

Yes, all configurations will be reset when removing the device from one network to move it to another one.   You should be able to create a template from the device before moving it, and then assign the template to be allowed on the network you're moving it to.   Edit- It's been awhile since I've moved MS devices (never moved an MX), so I can't remember what settings didn't move, but it wasn't like a full wipe of the device. ... View more

@edefosse - I wouldn't think that you needed to trunk the port connected to the WAP. It can remain an access port with only the single VLAN tagged. The MR shouldn't need a VLAN set on it, as it should use whatever is set on the port it's connected to. In fact, you may run into more problems by trying to set the VLAN on the WAP interface. However, if you're using VLAN tagging on the SSIDs, then yes you should trunk the port.   If you have any managed switches downstream of the MS, just make sure you change their native VLAN first, otherwise you'll probably have to physically connect to them to make the change. I like simplicity in my network design so I have zero trunk ports downstream of my MS edge switches. I do only have one SSID in bridge mode and a public one using Meraki DHCP.   A good practice to use on the MS, depending on available ports, is to make the VLAN changes to a different port than your current uplink. Then move the uplink to that port. That way, if something doesn't work properly, you can switch back and make further changes as needed. The local interface page for the MS is.... severely lacking, to put it kindly. ... View more

Just speaking from a security standpoint, you should never use VLAN 1 as the native/management VLAN. ... View more

I would make a batch file with the following commands to run, then run as administrator-     netsh wlan delete profile name="xxx" interface="Wi-Fi" (where xxx = duplicated wifi name, copy/paste for all duplicate instances) netsh int ip reset netsh winsock reset shutdown -f -r -t 5     It's definitely a Windows issue. On the machines that you're seeing this on, is there OEM wireless software installed? On Dell laptops there's a ridiculous OEM program called "Dell Unified Wireless Suite" that has wreaked havoc for me on occasion. I always remove any OEM wireless software and just force drivers only install. ... View more

One thing to remember, especially with Dell laptops, is that the OEM uses some proprietary software/drivers that don't always get along with WAPs. If a Dell has the "Unified Wireless Driver" software (or whatever it's called), you should definitely uninstall that POS software, uninstall the driver, reboot and let Windows reinstall the drivers. Unfortunately, most of the time you won't be able to update the driver and are stuck with whatever 3 year old driver Dell has released. I refuse to use HP products, so not sure if they're still as bad as Dell for that. ... View more

@ww   Interesting! I just compared two WAPs in the same building, one had VLAN specified and one didn't. So, removed VLAN from the one, reboot, and presto.  ... View more

@BlakeRichardson  Screenshots of the overall picture of the WAPs, and then a specific WAP or two? ... View more

@Nash- I eliminated every single trunk port in my networks except at the edge uplinks. Each site utilizes 1 VLAN on the interior, and 1 VLAN on the exterior- no tagging. 90% of the traffic is wireless, with no VOIP or anything else substantial, so no point to over-complicate it. It's a mix of two point-to-point sites and three in a mesh, all connecting to a single switch before control is handed off to the county network. Sites are on separate scopes via the Windows server and the MS320s. ... View more

@NolanHerring Oh, they're set in that section of the individual setup page! I had an problem with an AT&T supplied switch that caused issues with my DHCP/DNS for a few sites. It was a MetroLan mesh network with MS320s at the edge of each site relaying DHCP to a Windows server. Long story short, reservations that had existed before me were failing, so I had to change some devices to static IP and remove the reservations. Worked fine for devices like network printers and computers, but the MR34s refused to accept or use their static settings.   I recently switched to a new mesh and equipment, still using the MS320s at the sites, and still have multiple random 'bad ip assignment' or 'bad DNS' for no discernible reason. Some will be fine for 3+ days and then just decide 'whatever dude, here's a message'. Could be a single one at 4am, or multiple, or varying times between 80% at one site. If it was all WAPs attached to a specific switch, somewhere along the line, doing it at the same time, at least I'd know what the heck to trace. But this? Quite aggravating, really. ... View more

@BrechtSchamp - A Catalyst 9200L is way more switch than needed for an offline scenario, not to mention cost prohibitive and 24port is the smallest (I believe).   @Tomek I would recommend a SG300-10MP or SG350-10MP switch if you need a managed swtich with some POE ports. Newer and much better than a 2960! ... View more

@NolanHerring - Do you have any 2.4ghz devices running on the MR52s? I had run into an issue with 26.3 and devices like wireless printers dropping and not reconnecting. No issues like that with my MR34s. ... View more

@NolanHerring This was just me testing on my own. I've run into a bug that I worked with support on previously which pertained to the MR34 and WPA2 DHCP rejection. I had to roll back to 25.13 because teachers are starting to report and I have quite a few Brother wireless printers at the site that has the MR52s. Zero connection issue with the 25.13 firmware.   Basically, I reset the network interface on the printer and started fresh. It connected and would accept a print job. I could see it on the WAP in the dashboard. Then it would drop from the WAP with a Reason Unknown message, but the printer itself would have a solid wi-fi light. I could reset the WAP, watch the printer connect to the WAP next door, and then repeat the process of dropping with Reason Unknown. The printer has the latest firmware from Brother and is less than a year old. It's a model I have a few of at multiple sites and haven't had an issue with it previously.   I started a case with support just to inform them of the bug. Unfortunately I don't have the ability to test this one any further! ... View more

@Charlie I would advise against using the 26.3 Beta firmware with the MR52. Now that staff is starting to return (school district) I discovered a bug where devices on the 2.4ghz band (printer in this case) would Disassociate:Reason Unknown after a minute or two of connection and would not reconnect unless the WAP was reset and then it would just repeat the issue a minute or two later. ... View more

From what I can tell, a DHCP relay should work on all but the VLAN 40.   Essentially it should look like this (I think): VLAN 1 Int IP 172.28.0.250 Enable IGMP DHCP Relay to 172.28.4.254   Rinse and repeat, except for VLAN 40 which should not be able to have a relay set.  Again, this is my experience with my MS320s which are a bit more robust on L3, but I do have some MS220s that are comparable to the 120 and that looks like an appropriate config for them.  I can check later when I won't interfere with business functions. ... View more

@Adam2104  What is the IP address of your DHCP server and the IP address of the interface on the MS120 from the Routing and DHCP page? ... View more

Do you have DHCP Scopes setup?  We have a single domain that uses 5 different /19 scopes across our sites, with MS320s setup to relay to Windows DHCP servers.  However, the one that has it's interface IP set in the same scope as the DHCP server cannot be set to relay.  If I recall right, the web interface won't allow you to make this change if that's the case.  I wouldn't imagine it's much different for the MS120. ... View more

@MMoss  (I realize I erred in saying MR32 in my previous response, as it was actually MR34)   The earliest one I found was from 25.1 "Condition under investigation prevents DHCP offers from being sent over the air (MR34)"  This was right at the beginning of my school year and teachers were freaking out.  I was able to get with support and engineering so they could gather info while it was happening.  That Known Issue dissappeared in 25.5 without showing up in the Bug Fix section.  However, I stuck with a 24.x firmware until just recently.  I could deal with the abysmal throughtput on 2.4GHz way more than having to reboot 104 WAPs over 3 different sites practically daily.   I recently had a couple random MR34 issues on 26.2, but I chalk that up to 'ghosts' in the firmware upgrade process.  A couple randomly didn't come online properly, while a couple weren't allowing connections.  For that I used the remove/reset/reassign trick. ... View more

@MMoss I discovered this issue quite some time ago on the 25.x firmware for the MR34.  Essentially, the SSID that uses Local LAN for client assignment would not complete DHCP requests properly, while the SSID that uses Meraki DHCP had no problems.  I ended up forcing Meraki to downgrade me to a 24.x firmware until they could implement a fix, even though that firmware had major issues with 2.4ghz band.    The 26.2 firmware has been mostly stable for me on all MR34/MR42/MR52 across my sites.  Any AP that I've found to be problematic has been removed from the network dashboard, hardware reset, and then reintroduced to a network.   (edited to change MR32 to MR34) ... View more

Have you looked into the Meraki Narrow Patch Antennas?  That may be a solution, albeit and expensive one. ... View more

I had this issue with a MS320, and eventually the SFP ports failed.  I only discovered it due to power outages during a construction phase, and then some extensive troubleshooting. ... View more

@jbright  No, standard Cisco POE switches.  We can't afford that many Meraki devices and licenses as a public school district.   Would be nice to have something that should be "basic functionality" in the dashboard. ... View more