@george1421 that did the trick!
Thx for the support!

@sebastian-roth thx for the support!

@george1421 that did the trick!
Thx for the support!

@george1421 THX!

@sebastian-roth can you see something in the file attached?

N_EKS - appliance_MX-MX64 N_EKS_IF-LAN.pcap

@george1421 then i’ll get

18:47:45.022319 IP 192.168.5.121.2070 > 95.0.0.85.69: 30 RRQ “undionly.kpxe” octet tsize 0
18:47:45.061293 IP 192.168.5.121.2071 > 95.0.0.85.69: 35 RRQ “undionly.kpxe” octet blksize 1456

@george1421 the answer from Meraki Support:

The two sites are using MTU 1432 size due to protocol overhead. This is the recommended value. The best option here is to adjust the MTU of the PXE. Increasing the MTU would result in an MTU greater than 1500 which may lead to fragmentation. Also, Meraki does not support Jumbo size MTU. Should you require further assistance, please do not hesitate to reach out to us asap.

@george1421 i’ve changed the block size and rebooted the device.
But that did not solve the problem.
If i ask meraki support to increase the MTU for the site-to-site VPN, will that solve it?

@george1421

Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04

@sebastian-roth thx for your reply, but i doesn’t have a CLI on the Meraki Firewall. I have to contact support i guess.

@george1421 the max MTU size is 1404.
I’ve installed the FOG server on a Linux Ubuntu.