<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The border router will do like any other router on the world. If the DF bit is set (common case) or if it's IPv6, it will not fragment but send an ICMP.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">Le 8 août 2017 à 13:34, Moacir Ferreira <<a href="mailto:moacirferreira@hotmail.com" class="">moacirferreira@hotmail.com</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div id="divtagdefaultwrapper" dir="ltr" style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-size: 12pt; font-family: Calibri, Helvetica, sans-serif;" class=""><div style="margin-top: 0px; margin-bottom: 0px;" class="">True! But in some point of the network it may be necessary to make the MTU 1500. For example, if your data need to cross the Internet. The border router in between your LAN and the Internet will have to fragment a large frame back to a normal one to send it over the Internet. This router will just "die" if you have a heavy load.<span class="Apple-converted-space"> </span><br class=""></div><br class="">Moacir<br class=""><br class=""><div style="color: rgb(49, 55, 57);" class=""><hr tabindex="-1" style="display: inline-block; width: 919.234375px;" class=""><div id="divRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" style="font-size: 11pt;" class=""><b class="">From:</b><span class="Apple-converted-space"> </span>Fabrice Bacchella <<a href="mailto:fabrice.bacchella@orange.fr" class="">fabrice.bacchella@orange.fr</a>><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Tuesday, August 8, 2017 12:23 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Moacir Ferreira<br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span><a href="mailto:users@ovirt.org" class="">users@ovirt.org</a><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [ovirt-users] Users Digest, Vol 71, Issue 37</font><div class=""> </div></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">Le 8 août 2017 à 11:49, Moacir Ferreira <<a href="mailto:moacirferreira@hotmail.com" class="">moacirferreira@hotmail.com</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div id="divtagdefaultwrapper" dir="ltr" class="" style="font-style: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; font-size: 12pt; font-family: Calibri, Helvetica, sans-serif;"><div class="" style="margin-top: 0px; margin-bottom: 0px;">This is by far more complex. A good NIC will have an offload engine (LSO - Large Segment Offload) and, if so, the NIC driver will report a MTU of 64K to the IP stack. The IP stack will then send data to the NIC as if the MTU were 64K and the NIC will fragment it to the size of the "declared" MTU on the interface so PMTUD will not be efficient in such scenario. If all this takes place in the server, then you get no problem. But if a standard router is configured to support 9K jumbo frame in one interface (i.e.: LAN connection) and 1500 in another (i.e.: WAN connection) then the router will be responsible for the fragmentation.</div></div></div></blockquote><br class=""></div><div class="">That's happen only if the bit don't fragment is not set, otherwise router are not allowed to do that and send back a "packet to big" ICMP, it's called path mtu discovery. To my knowledge, it's usually set, and even mandatory on IPv6.</div></div></div></div></div></blockquote></div><br class=""></div></body></html>