Yes, both WAN of hub and spoke support 1500 bytes ... View more

As per meraki support the packet is not received in the other side of vpn. So we don't have any idea. ... View more

Is that mean the MX just drop the packet? Thanks ... View more

I don't think that MX is informing the client device that the packet needs to be fragmented.   ... View more

When i tried to ping the spoke MX with 1500bytes it gives the packet fragmentation message w/c is expected. But when i tried around 1399 up to around 1450 bytes, it just timed out. Edit: 1398 works but not 1400 is timed out     Edit: I have 2 different spokes MX here with different behavior when i ping with 1500bytes   ... View more

Yes, the client device is aware that it cannot send over 1392 bytes, but based on the packet capture the device still keep trying to send around 1500 bytes multiple times. Then we will get a timeout error. Currently we don't have any idea what to do 😄 😄 😄 ... View more

its over TCP.  They just inform us that the header DF is set to 1. Unfortunately we don't have idea where to change any settings since its only a biometrics. Some of our sites works fine, I can ping other vpn subnet with 1500 bytes and those biometric devices sync with the server. But some of sites are dropping the packets from the biometric. ... View more

Our biometric devices in different sites cannot sync to our main office server since we are using AutoVPN. When the support from meraki identified that biometric devices send above the MTU (i think around 1500bytes). They stop replying on the case and left the ticket open. Thanks for your reply. ... View more

We tried to reach out meraki support but they not responding if the case is related to MTU. ... View more