Meraki

RaphaelL

Yep pretty sure I also have experienced this behavior on a small MS.

RaphaelL

No. It is my MX at home. Directly plugged into my ONT. My PC is a client behind the MX. My PC is bulding a VPN tunnel to a VPN appliance somewhere else. The MX is displaying the packets in the wrong sequence but are received in the right sequence.

RaphaelL

I can't quite find the exact answer I got months ago. It was something that the packet capture engine is not prioritized by the CPU. So It can miss packets or show them in the incorrect order.

RaphaelL

Hi , Just encountered once again a very special behavior on the MX plateform ( running 19.1.5 ). Testing scenario : I'm capturing IPSec ( VPN tunnel from my computer to a VPN gateway ) trafic on my PC and on my MX which performs L3 routing for my LAN. My goal is to capture all ESP packets and compare the ESP Sequence to quantify the number of ESP packets inbound that are out of order. To my biggest surprise the 2 traces are way different. As you can see the exact same packet with the same IP ID and the same ESP sequence appears out of order only on the pcap taken on a MX. Conclusion : The packet capture engine on the MX is way to unpredictable. Packets are routed and forwarded in the correct order , but they will be scrambled in the captures making troubleshoot harder. Yes. I had a case opened in the past. Yes they said this is expected. Reason #34591 that I dislike MXs.

RaphaelL

Might be far fetch but can you capture the beacons to confirm that 802.11r is not enabled ?

RaphaelL

Hi , Have you tested this with a more recent MS firmware ? MS 17.1.4 is stable RC.

RaphaelL

No since the frames will be forwarded and not routed. ( L2 vs L3 )

RaphaelL

Hi , Where are you reading this info ? Also there is a firmware bug related to Device utilization stuck at 100%. What firmware are you running ?

RaphaelL

Hi , https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Device_Uptime Requirements and Limitations Device uptime is supported on all Cisco Meraki switch models and most access points. Support for other products is planned for future availability.

RaphaelL

Bonjour , Peux-tu nous partager les configurations du wifi qui est sous Meraki ? Est-ce que la TV supporte seulement 2.4ghz ?

RaphaelL

Forgot to reply to my own post lol. Support told me this is a known issue that won't be fixed since this will be replaced by Assurance Endpoints

RaphaelL

Easiest way to troubleshoot those issues would be to take packet captures. 1- Capture on LAN side of the MX Spoke 2- Capture on the Site-To-Site VPN interface of the VPN spoke 3- Capture on the Site-To-Site VPN interface of the VPN Hub if you see the DHCP requests on all 3 , the problem is not on your Meraki environnement

RaphaelL

THIS is what I like to read ! I will speak for the rest of the group but we dedicate a lot of our time on the dashboard and also here on the community. To see that someone from Meraki reads our suggestions / critics is good way to tell us that we have a voice and can influence Meraki and hopefully make the experience even better ! - Raphael & and the rest.

RaphaelL

6 or 7 ( who is counting ) The scaling of the timeline is super odd. Increments of 16-17 minutes and doesn't line up with the graph below.

RaphaelL

5 - This is what I was refering to.

RaphaelL

It is not as bad as I expected , however they need to re-organize the info on the left. It is scattered. 1- I would put in a block all SSID / radio related info. 2- Put the notes right below the address 3- Group uptime and firmware in the same section. 4-I have the same 'bug' , SSID id '0' is displayed instead of the name of the SSID. Odd text wrapping for long client names ( you know these damn client names that are created with mDNS instead of DHCP that people have requested for years to change the processing order of a client name xxxxxxxx-4a0c-4148-a1ee-cf390578ab3c 🙃 ) 5-Centering of the client info is also messed up. Some collums are centered and some are not. The info shouldn't take 1/2 of my screen. Put all that text in a small (!) icon. Need help with your UI ? 1-800-Raphael

RaphaelL

Wow ! This is a spoke right ?

RaphaelL

This was also added to the change log : Added support for Catalyst and Meraki SD-WAN fabric Interconnect

RaphaelL

I fear we were wrong on this one.

RaphaelL

As a big/large Meraki customer , we are not ready at all to fully unleash the potential of Wifi7. I wonder how many customer are ready ? PoE and link speed ( in some cases cabling ) are some of these points that I'm refering to.

RaphaelL

Good eye !

RaphaelL

Hi , The section "dashboard configuration" should cover what you are trying to achieve : https://documentation.meraki.com/MR/Encryption_and_Authentication/Configuring_RADIUS_Authentication_with_WPA2-Enterprise In dashboard, navigate to Wireless > Configure > Access control. Select your desired SSID from the SSID drop down (or navigate to Wireless > Configure > SSIDs to create a new SSID first). For Security choose Enterprise with my RADIUS server. Under RADIUS click Add server Enter the following information in the table: Host IP or FQDN*: IP address or FQDN of your RADIUS server, reachable from the access points. Auth port: UDP port of the RADIUS server listens on for Access-Requests; 1812 by default. Secret: RADIUS client shared secret

RaphaelL

802.11r is currently ( always has been ) bugged with every Windows OS. A "fix" is coming early 2025. Advised to turn 802.11r off until then.

RaphaelL

Would it be possible to share the tcp 3-way hanshake ? I'm curious to see mtu/mss and tcp options ( Window scaling for example )

RaphaelL

General known issues If voice and data are configured to use the same VLAN DHCP discovery messages may not be correctly forwarded from client devices after being authenticated via 802.1x on the voice VLAN I don't understand this one. This was introduced in MS 15 and Meraki told us they won't fix it. Then why is it a known issue.

About RaphaelL

RaphaelL

Raphael Letourneau

Community Record

Badges