Hi,    This is because you still have licences that have not expired. I think you might be able to convert them to MX84 and increase the length of the overall licensing. Support needs to do this (I think).    Also, I would delete the screenshots and put new ones up with the serial numbers, MAC address and order numbers blanked out.  ... View more

Same for me on a MR52 network.    It does say that 27.5.10 (which I also can not upgrade to) is the initial stable firmware for MR44.  ... View more

This will likely be my upgrade path for the home office if that's the case.   We were thinking MR36 but this a great middle ground price wise with the MR46. ... View more

If this is an external scan then I assume you have port forwarding under your firewall settings for ports 22 and 30005? That should give you the IP address of the device. ... View more

Looks like this has now been added.  ... View more

I took this as a slight cop-out. Hasn't v15 been in beta  for over 2 years?   I don't think there has been a stable release candidate for v15 either!?! I was under the impressions that the different  stages were derived by the number of "stable" beta installs without reported issues? ... View more

Maybe they were doing an update to deploy IPv6 .... ? 😀 ... View more

Yes, and I've just received all the emails to say kit is now back up ... View more

I know that my client kit is not offline because they have not txt me yet (a lot are hospitality and open at the moment).    My kit is reporting offline via the emails, but very much up and working. On the status pages, it still says it can connect to the Meraki Cloud.      ... View more

Ah OK.    Thanks for confirmation. I've used the make a wish.  ... View more

You should be able to tag the ports and then choose the tag to get an alert for.    So tag all the ports except port 9 as "port notify" and then on the alerts pages choose this (I've tagged certain ports for cameras):     ... View more

I have a case open with support. Our MR52s are capped at 14dBm on the 2.4Ghz band, no matter what override or other settings we choose.    In fact, if I override the profile to 30dBm, after saving it sets the target to 14dBm.  ... View more

If it's a service such as RDP from one site to the other, check the firewall rules in Windows.   We had a similar issue with a client and till systems trying to communicate with each other across VLANs/Site-to-Site VPN. ... View more

Hello, here is a another topic:   https://community.meraki.com/t5/Wireless-LAN/Impact-of-iOS-14-random-MAC-on-IPSK-and-Meraki-functions/m-p/93536#M13781     Good point, I hadn't thought of the blacklisting. We do this in two ways, device and/or email address (if public and on splash page). Normally device isn't easy to change, but email is. Now both are essentially easy to change. ... View more

Let's hope that AnyConnect for Meraki does not require further licences! ... View more

Which firmware are you running?   I have found this problem and it has been added to the list of known issues (although Meraki claim the client doesn't disconnect). I, however, have experienced the client disconnecting.    I've moved to WPA2 and WPA3 transition and that seems to have solved the problem for me. ... View more

Wireless firmware versions MR 27.3 changelog Bug fixes Reduced aggregate upload throughput on 2.4 & 5GHz radio for Windows clients (MR45/MR55) Malformed packets received by the BLE radio may cause the MR to reboot (MR42/MR52/MR53/MR84) Wireless clients passing minimal amounts of traffic may be displayed as wired clients (All MRs) If a client roamed from an MR, and then after 5 minutes roamed back to the original MR, the association was rejected on 802.11w-required SSIDs (802.11ax MRs) Interoperability issues with some older clients and/or drivers resulted in the clients getting into states where they could not pass any traffic (802.11ac Wave 2 MRs) Scanning radio could enter an invalid state and lead to the MR rebooting (802.11ac Wave 2 MRs) Known issues Under certain conditions, successful WPA2-PSK connections are reported as failed under Wireless Health event logs (All MRs) Downstream VOIP RTP Packet Loss (MR42/MR42E/MR52/MR53/MR53E/MR84) Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (All MRs)       Looks like they are now acknowledging part of the issue at least. Having moved to WPA3, I don't see the issues any more for the last week in the dashboard. In fact f I look at the failed connections report for the last 2 months, it has no failed connections.... ... View more

I have tried with MR 27.2 and still getting the issue. ... View more

I don't believe that Sky give out the ISP credentials, you are forced to use their router unfortunately. It's one of the main reasons I have a BT line at home and just the Sky Q TV service and my Meraki stack running it all.    You may have to configure things differently -what's the purpose of the Z3, is this to also connect to a work/office VPN? ... View more

We have an MX84 and would be happy to run any beta testing if we can be included in the next phase.  ... View more

I have a full Meraki stack at home (mainly for the home office), but of course all of the usual residential stuff is also connected.    I have found that Nest, Ring etc need to be whitelisted. I'm not sure why exactly, but when I added a new Nest smoke alarm the app kept saying to check internet connection. Went into the dashboard, saw the new MAC address, clicked whitelist and then it worked. My only guess is they are trying to communicate in a way that Meraki thinks is suspicious or not using proper certificates.    Had to whitelist my ovens too 🙄 I don't like doing it but it works. At least I can put them all on a different VLAN and outside the scope of my work stuff + VPN. ... View more