Hi,   We are having a situation where we have an application that works perfectly fine in legacy. As soon as we migrate to SDWAN, the application starts rebooting and doesn't register. After analysis we found the application is sending certain bytes of MTU and expecting the same which works perfectly fine on legacy network. Unfortunately we are also not able to set the MTU under DHCP for this particular application. My question is: 1. Are we adding additional bytes for the VPN tunnel? Will MX report 1500 bytes or will it adjust the reporting value to the "available to the end point/user" (i.e., Total MTU minus the header that it's going to use/add for establishing its VPN)? 2. Can MX change the LAN side MTU? Or can it handle fragmentation/defragmentation within the box itself at the L2 level making it transparent to the application end points that there is some "VPN" in the path and the original payloads are being fragmented?  ... View more