@Gareth_    See here:   https://community.meraki.com/t5/Wireless-LAN/Air-Marshall-Rogue-SSID-s/td-p/39859   I recommend you simply whitelist it as such:       ... View more

VLAN support over MESH, that's a nice new feature that has been sorely lacking for a long time. ... View more

I'm East Coast, n76 ... View more

Although I should mention, I am able to get in through my OKTA/SAML setup.  However my personal account I can't, which is through the main website dashboard. ... View more

Same issue here ... View more

Thanks guys   Yeah all I had at the time was the IP, but I ended up just searching the AutoVPN Route Table to find which network the subnet lived in, then client list from there. Just sort of realized it was a little more difficult than I thought it should be, or remember it being.   MAC does work, just wish IP would too. ... View more

  @PhilipDAth wrote: I suspect now that 16.x is in beta, that it will enable the release of newer faster hardware. I am aware that Meraki has heard our complaints, is fully aware, and is supposedly taking action on this very thing. The when? Not sure, hoping sooner than later. ... View more

My scanner random disconnect issues started at several warehouses the moment 27.6 was pushed.   So after not being able to be onsite at the several warehouse locations, and trying to work with onsite to get a packet capture (unsuccessful), I ended up rolling back from 27.6 to 25.13 at one site and 26.8.1 at the other.    Several days have passed, and magically no more issues.   >.<   This is a real bummer, as I was really hoping to make 27.6 the new stable code.  And not being able to get a valid packet capture means Meraki support won't be able to do anything about it, so I have to basically avoid 27.X train for as long as I can at this point.    Hopefully someone else will run into the issue and also be physically onsite to be able to capture the issue first-hand so they can get a fix. ... View more

Best Windows 10 tool (by far) is this:  https://www.helge-keck.com/   When you connect to your wireless, fire it up and select the Network Name your connected to. Then click on Dashboard and it will give you plenty of info, plus more. ... View more

Unfortunately, trying to troubleshoot this issue is very difficult when I'm not physically at the location.   I've actually upgraded several warehouse sites to 27.6, they all use Zebra scanners, and every single one of them has been having non-stop issues with connectivity on the scanners every since upgrading, so I'm rolling back to 25.13 (been running for over a year on this code no issues)   I don't care what the firmware version is, I only care that it's stable. ... View more

What firmware version were you running before you downgraded to 25.11?   There are a ton of variables with a setup like this and it's difficult to pinpoint the exact issue. Its very possible that the AutoRF is not running optimal channels, so you could have AP's near enough that are on the same frequency, which means that you really only have a single cell instead of two cells. MR32's don't support RX-SOP unfortunately, so that's a shame.  If you can, try setting up a static power and channel plan on a portion of the building or wherever your getting complaints. Also I'm assuming the SSID the teachers are using is 5GHz only? ... View more

n76 here   just got about 50 email alerts for almost all networks showing devices down etc. ... View more

Yeah its a tough situation to tshoot.   I shipped a Macbook to the site to use that as a capture tool.   AP is right above the client and it will be connected but then just 'disconnect' and can't connect for X minutes. There are other AP's also nearby that provide good secondary coverage as well. So there are plenty of chances to reconnect, but also no reason to lose connection to begin with.   One thing I see in Wireless Health is authentication failures, but this has pretty much always been an issue and i know 27.6 was supposed to have fixed the false positives for that reporting, not sure if thats true or not.  ... View more

You'll have to confirm on your firewall if the ports are allowed:   https://documentation.meraki.com/General_Administration/Other_Topics/Upstream_Firewall_Rules_for_Cloud_Connectivity ... View more

Not much else to go on here, your AP does not have Internet access. Could be a million things that have nothing to do with the Meraki AP.   You could try connecting to the same switch yourself on that port and see if you have Internet access and go from there.  ... View more

Are you testing between just two specific APs?   I wouldn't let the power go over 17dBm personally, but again this comes down to the design that was done. You'll run into power mismatch issues with power levels being too high (client can hear AP well, but AP can't hear client well scenario).   Looks like your using the older version of the radio settings page, I would personally use the new version if I were you. You'll want to turn client balancing OFF as well, that prevents clients from joining an AP if the AP things it already has too many which = bad for voice. ... View more

Just to confirm are you using an iPhone to test with? For the sake of testing, I would try with 802.11r disabled and see if it makes any difference, or fully on.   Your on the right path, using a 'test SSID' will allow you to figure out where the trouble areas are on your own.    I'm going to assume the port configurations for each AP are correct, and all on the same L2 network. So assuming that, what I would do is have this new SSID only broadcast on AP's with tags, and then pick two AP's near each other and just walk back and forth and confirm if roaming is having an issue or not.   I would tune your power levels, or at least see where Meraki is having them land on. You want it to be around 11 - 17dBm range, so if you have AP's at 5dBm or 30dBm then that's not good. This allows for proper TX power matching between clients and APs (again this also comes down to the RF design).   Another thing to consider (not sure what country your in) is if your using DFS channels (UNII-2 and UNII-2e), which has impact on roaming. Clients are not allowed to actively scan and probe on DFS, they can only listen for beacons, so its takes longer for them to discover if there is an AP on a DFS channel for it to roam to, which means a delay in the roaming etc. 802.11k is supposed to help with this but its not perfect, so its something to consider.   If all configurations are good, and your still having issues, its going to come down to the RF design which is a physical thing and these forums won't really be able to assist you with other than recommend you have an outside source perform a survey and come up with better AP locations.   Have a look at this guide here (although I recommend ignoring the SSID bandwidth limiting they suggest): https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/Wireless_VoIP_QoS_Best_Practices   This link here is about Cisco WLCs, but they go over some RF design stuff that is worth a review: https://mrncciew.files.wordpress.com/2012/12/brkewn-2000-voice-over-wifi-best-practices.pdf   ... View more

@mikeset116 wrote: should i then change the minum bit rate from 12 to 6 , this will be for the same SSID 5 and 2,4 GHZ For 2.4GHz, unless you need 802.11b support (only you will know this), then set it to 12Mbps to cut-off/disable those slow 802.11b rates.   For 5GHz you can set to 6Mbps without any issue. ... View more

The better option is as follows:   You will need to contact Meraki support and ask them to enable the feature/option to configure an SSID as 2.4GHz only.   When you have that turned on, then create a new SSID and make it 2.4GHz only. Those legacy devices will then need to connect to this new SSID.   Then make the existing SSID that you have now, 5GHz only   Done and done You still have 2.4GHz support, but on a dedicated SSID. This might require more effort on your end as you'll need to reconfigure those devices to connect to this new SSID, but in my opinion its worth it. ... View more

Off the cuff, few things I would do.   Upgrade to 27.6 firmware Your TX power levels are defaulted, I would look at making sure the power level on each AP is where it should be. This of course requires survey work to know. Relying on Meraki AutoTX/RRM is not a good idea I would make your SSID's 5GHz only and 2.4GHz only. Dual-Band can cause issues with voice. Make sure your voice clients are only connected to the 5GHz one. I would also set your minimum data rate on 5GHz to 6Mbps Set your channel width to 20MHz on 5GHz Make sure you don't have RXSOP enabled 802.11r will only help iOS devices (FYI), not sure what clients your using You need to be 100% certain that the AP ports are configured correctly. They need to be on the same VLAN for the SSID the clients are using, otherwise you'll never get fast roaming if your swapping L3 domains.   Now of course, you could have the perfect configuration and still have issues if your actual wireless (RF) design is not adequate. No config can fix that. You have to ensure proper overlap from one AP cell to the next to ensure proper and seamless roaming for the client from AP1 to AP2 etc.  This goes back to making sure the wireless design was done properly with a site survey etc. ... View more

Few things I don't like:   SecureConnect will automatically place these MR access-points in the same VLAN as the management VLAN of the switch they are connected to. Not a fan of this and they should allow in the future the ability to specify management VLAN for wireless. I don't always use the same VLAN for switch and AP subnets.   Assuming authenticated, the "Allowed VLANs : All VLANs"   I specifically go out of my way to only allow VLANs with SSID's tied to them (and management for AP) on these ports. Hopefully they allow this to be configured in the future. ... View more

I've been having that same Chrome issue the last few days as well. Gets old quick. ... View more