Meraki

RaphaelL

Not sure if it's only me but the 2 links do not work : http://cs.co/9006CuCs6 / http://cs.co/9001Q4ALF

RaphaelL

Hi , I just found out that weather channels 120,124,128 are no longer restricted in Canada / IC : https://www.csagroup.org/global-certification-regulatory-update/canada-releases-rss-247-issue-4-updated-rules-for-licence-exempt-wireless-devices/?srsltid=AfmBOopLkEdBpOeWj7kI1N9AKIWbFLM6seNwtVGQXn1_s-9RZOACBAwq They are still greyed out and can't be used in my RF Profile. 1- Will they become available with a firmware update ? 2- Will it cause client compatibility issues ? 3- Am I missing something obvious ?

RaphaelL

That really scared me for a moment 😥 Interesting , was the deprecation of TLS 1.0 announced anywhere ? looks like I have missed it

RaphaelL

Hi , This should be the one : GET /organizations/{organizationId}/devices/uplinksLossAndLatency ( getOrganizationDevicesUplinksLossAndLatency )

RaphaelL

And if you take a pcap you see the lldp / cdp packets ? Can you see the info in any other cdp/lldp endpoint such as GET /devices/{serial}/lldpCdp

RaphaelL

No , as you can see I'm receving both cdp and lldp info from 2 vendors. And I'm using the same endpoint that you provided but any cdp/lldp related endpoint should work just fine.

RaphaelL

I'm able to see all my non-Meraki devices via LLDP and CDP: { "nodes": [ { "derivedId": "x", "mac": "x", "type": "discovered", "root": true, "discovered": { "lldp": null, "cdp": { "platform": "Cisco C6816-X-LE", "deviceId": "x", "address": "x", "capabilities": [ "Router", "Switch", "IGMP conditional filtering" ], "managementAddress": "x" } } } "nodes": [ { "derivedId": "x", "mac": "x", "type": "discovered", "root": true, "discovered": { "lldp": { "systemName": "x", "chassisId": "x", "systemDescription": "Arista Networks EOS version 4.32.5M running on an Arista Networks DCS-7050SX3-48YC8C", "systemCapabilities": [ "S-VLAN Component of a VLAN Bridge" ], "managementAddress": "x" }, "cdp": null } }

RaphaelL

You are right. Unselected ports have a different color combo that doesn't match the port key. Only when you select the port , that the colors match. Theres a first for everything

RaphaelL

I have a case open about a very similar issue but for SecurePort. Still awaiting if this is a known issue or not

RaphaelL

The colors from the port key tab do not even match the real colors used... that's pretty basic imo warning =

RaphaelL

Seems to be affecting any switches with the new view

RaphaelL

So you did create a L3 rule to block UDP 5353 on your corp ssid ? And yes M2U is enabled and is enabled by default

RaphaelL

Hi , We have a fairly large Meraki setup. Approx 5500 APs scatered on 800 sites. Some sites are super small , and some have more than 40-50 APs. https://www.ciscolive.com/c/dam/r/ciscolive/apjc/docs/2025/pdf/BRKEWN-2046.pdf This document seems to suggest that we should block mDNS to save some airtime. This video is also a great one : https://www.youtube.com/watch?v=miRV8qDOKBE We have 4 SSIDs. 2 of them are for Guests with L2 isolation , 1 for IOT and 1 for Corp ( no L2 isolation on both ). We have 0 use case for mDNS on Corp. For people that have medium to large campuses , what do you do about it ? EDIT : IGMP snooping is enabled , Flood unknown multicast is disabled , Multicast to Unicast conversion is enabled.

RaphaelL

Exact same result on my APs.

RaphaelL

Correct ! "dhcpRelayServerIps": [ "10.1.1.1", "10.2.2.2", "10.3.3.3", "10.4.4.4" ]

RaphaelL

Hi , I enabled this feature earlier but I can't find the new info anywhere ? Am I blind ? I couldn't find the documentation related to this feature.

RaphaelL

Music to my ears !

RaphaelL

Well a MTU of 1000 on the wireless wouldn't make any sense for that kind of issues. It would break more things than Webex and Teams. TCP TLS packets are (always?) sent with DF bit set, so they would be dropped and nothing would work.

RaphaelL

Isn't that expected ? https://documentation.meraki.com/SASE_and_SD-WAN/MX/Operate_and_Maintain/Monitoring_and_Reporting/Appliance_Status/MX_Uplink_Settings Note: Modifying the following items will result in WAN interfaces being reset. State (enabled/disabled) of any WAN interface Addressing method (static/DHCP) of any WAN interface State (enabled/disabled) of any LAN interface This will result in a loss of connectivity on both Internet uplinks for up to 2 minutes. Therefore, it is recommended to only make changes during a planned maintenance window so that disruption is minimal. How long does it take to failover ?

RaphaelL

I wouldn't be surprised to finaly see a sunset on L2TP. Something like MX 26 to be the last version offering support for it.

RaphaelL

I have never used SM , but I was surprised that no one ( either from Meraki lol ) posted about here except for this post that you commented on earlier. Like you said Intune and Jamf probably have most of the market share

RaphaelL

First Meraki product to have the CalVer format

RaphaelL

Security appliance firmware versions MX 26.1.1 changelog What's new Expanded BGP attribute support to include outbound well-known and custom communities and increased route integrity with inbound filtering. Client VPN now supports IKEv2 for establishing connections. VPN full-tunnel exclusion now includes source-based and NBAR application-based exclusion definitions. Added support for encrypted (TLS) syslog Legacy products notice When configured for this version, Z3(C) devices will run MX 19.2.4. When configured for this version, MX64(W), MX65(W), MX84, MX100, and vMX100 devices will run MX 18.107.13. Other The product complies with EN 18031-1:2024 and EN 18031-2: 2024

RaphaelL

also why is it I can't disable IPV6 on the WAN if I don't want to use it? I really feel you...

RaphaelL

I just checked my last firmware upgrade on 2025-08-03 All my networks were scheduled to start at the same time. From the same template : "time": "2025-08-03T03:53:16Z" "time": "2025-08-03T03:41:16Z" "time": "2025-08-03T03:31:16Z" "time": "2025-08-03T02:40:17Z" "time": "2025-08-03T03:36:17Z" "time": "2025-08-03T03:57:16Z" Standalone networks : "time": "2025-08-03T02:40:16Z" "time": "2025-08-03T02:40:16Z" "time": "2025-08-03T02:48:17Z" "time": "2025-08-03T02:40:17Z" "time": "2025-08-03T02:38:16Z" Again I might be wrong but from what I recall all non-templated networks start at the same time ( +/- 3 mins ) and all child network from the same template are in sequence.

About RaphaelL

RaphaelL

Raphael Letourneau

Community Record

Badges