Meraki

RaphaelL · ‎Oct 10 2025

Confirmed by support this is not a bug. The doc as mentionned will be modified. I have been advised by our development team the feature of packet capture is available in switch port page for Read-only user as by desgin in a new dashboard UI version. Our KB Packet Capture Overview will be updated accordingly.

RaphaelL · ‎Oct 10 2025

I haven't tested all the ways to do it but this is one of them : Might also be accessible with the new UI from Intelligent packet capture

RaphaelL · ‎Oct 10 2025

Hi , https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Packet_Capture_Overview ( this will be updated ) Read-only and monitor-only are able to perform disruptive actions ( without any logs 😍 ) such as Cable-tests and port cycles. And now it's getting worse. These roles are now able to perform packet captures on your switches. Does that make any sense ? Absolutly not. Who thought that this was a good idea ..? I feel like Meraki isn't taking security seriously.

RaphaelL · ‎Oct 9 2025

Maybe this one ? https://developer.cisco.com/meraki/api-v1/get-device-wireless-status/ Unefficient since it's a per device call but seems to be the only one.

RaphaelL · ‎Oct 9 2025

That's odd since I already have 2 these in my firewall rules. I deleted them and re-added without problems.

RaphaelL · ‎Oct 9 2025

it does : ;QUESTION crl.microsoft.co. IN A ;ANSWER crl.microsoft.co. 3600 IN A 104.215.95.187 crl.microsoft.co. 3600 IN A 52.164.206.56 I just tested it in my lab and it works. No idea how you are getting this error, that's curious

RaphaelL · ‎Oct 8 2025

Hi Raphael This is a known issue that is resolved in firmware version MR 31.1.6 (Stable release candidate). Please upgrade the devices and let me know if the issue still occurs. I just wished ( real bad ) that MR firmware would include more fixes instead of "General fixes and improvement". This would prevent me from opening a ton of cases. Will try that firmware and report

RaphaelL · ‎Oct 7 2025

Cool great ! That event was also present in Wireless health I assume ? (but no PCAP was found) I will investigate with support.

RaphaelL · ‎Oct 7 2025

That means that it can run the current latest firmware. In that case that would be MR 32.X.X

RaphaelL · ‎Oct 7 2025

Not recommended at all : https://documentation.meraki.com/General_Administration/Firmware_Upgrades/MR_Mixed_Firmware_Networks

RaphaelL · ‎Oct 7 2025

Hi , Been trying proactive PCAP for the last couple of days and I'm a bit disapointed. I was trying to troubleshoot a random DHCP message that occurs ( DHCP no offer during roams ). However the proactive PCAP module doesn't seem to capture DHCP errors. Looking at the documentation : https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Packet_Capture_Overview Automated packet captures are limited to client association/authentication failures but from experience and from : https://community.meraki.com/t5/Wireless/Proactive-PCAP/m-p/258387 and GIdenJoe's screenshot you can see that it also covers DNS issues. Is the documentation incorrect ? Is it limited only to assoc/auth or the typical assoc/auth/dhcp/dns like we are used to from Wireless Health ?

RaphaelL · ‎Oct 7 2025

Somehow this was removed : Resolved an issue that resulted in MX appliances not performing TCP MSS clamping for IPsec VPN peers. (MX-2492)

RaphaelL · ‎Oct 6 2025

No , this is because Meraki prefers to identify clients with mDNS. Your client is sending mDNS packets containing a GUID. This was discussed many times over the years : https://community.meraki.com/t5/Security-SD-WAN/Computer-name-not-displaying-properly-in-Description/m-p/62285

RaphaelL · ‎Oct 6 2025

Did more digging this morning. {"ssid":"DIRECT-E6-HP OfficeJet 3830","bssids":[{"bssid":"E7","contained":false,"detectedBy":[{"device":"KK","rssi":138},{"device":"AS","rssi":3},{"device":"J7","rssi":8},{"device":"TK","rssi":11}]}] AirMarshal flags this BSSID at 130++db on a single AP. Going to RF Spectrum the RSSI ( in dbm ) is -70dbm which is low and makes more sense since the other APs are already reading this BSSID with a low value. Tested with MR 30.7 and MR31.1.8 same results. It's always 1 AP on the lot that is showing odd values. Also why are the values inconsistent? AirMarshal RSSI = db RF Spectrum RSSI + Client page = dbm

RaphaelL · ‎Oct 6 2025

What signal ? Wireless signal ? Cellular signal ?

RaphaelL · ‎Oct 3 2025

That's what I'm thinking but I don't think Meraki is displaying RSSI in negative. I have never seen a negative value with Airmarshal. https://documentation.meraki.com/MR/Monitoring_and_Reporting/Location_Analytics RSSI - 95 = signal strength in dBm Still 137 doesn't make sense at all. I can also find frequently values of 255. Something is off

RaphaelL · ‎Oct 3 2025

Hi , I'm trying to understand the values returned by AirMarshal. I'm seeing SSIDs near my APs with some anormal values : I'm no wireless expert but a RSSI of 137db seems impossible. I can find approx 100ish other SSIDs on multiple sites with those values. Has anyone ever seen that ?

RaphaelL · ‎Oct 2 2025

https://developer.cisco.com/meraki/api-v1/api-index/ this is the way I use.

RaphaelL · ‎Oct 1 2025

No directly from the dashboard minutes ago , annnnnnnnd it's gone 🤔

RaphaelL · ‎Oct 1 2025

Increased CPU & memory utilization on MR57 APs The rest of the changelog is bugged and not properly displayed. This patch was not announced by the firmwarebot also.

RaphaelL · ‎Oct 1 2025

Any idea why MR45/55 have a backup version different than the other ? Shouldn't it be MR 31.1.8.1 ?

RaphaelL · ‎Oct 1 2025

Important note MR45/55 APs are not supported on MR 32.x.x and will instead upgrade to the backup version (MR 31.1.8)* if they are in networks configured for MR 32.x.x versions, and thus, new features will not be available. Bug fixes General stability, performance, and experience improvements APs intermittently stop sending beacons & responding to clients on 5GHz (Wi-Fi 6e) APs not responding to probe/auth requests from clients on 2.4 & 5GHz (Wi-Fi 6, 6e) Multi/Broadcast packets (RA/DHCP) not forwarded by APs (Wi-Fi 7) Mesh not forming 6GHz 160MHz (Wi-Fi 6e) *was corrected moments ago

RaphaelL · ‎Oct 1 2025

Yours is even worse lol

RaphaelL · ‎Oct 1 2025

The version is out

RaphaelL · ‎Oct 1 2025

Nice find ! aphael doesn't sound quite like Raphael. "R"s are important !

About RaphaelL

RaphaelL

Raphael Letourneau

Community Record

Badges