From: grahn+nntp@snipabacken.se   
      
   On Wed, 2013-06-12, Moe Trin wrote:   
   > On Wed, 12 Jun 2013, in the Usenet newsgroup comp.protocols.tcp-ip, in   
   article   
   > , Barry Margolin   
   wrote:   
   >   
   >>Jorgen Grahn  wrote:   
   >   
   >>> My take on this is: you cannot really change the MTU on an interface   
   >>> -- you can only tell the interface the actual MTU on the link.   
   >   
   > [fermi ~]$ uname -o   
   > GNU/Linux   
   > [fermi ~]$ whatis ip ifconfig   
   > ip           (7)  - Linux IPv4 protocol implementation   
   > ip           (8)  - show / manipulate routing, devices, policy routing   
   >     and tunnels   
   > ifconfig     (8)  - configure a network interface   
   > [fermi ~]$   
   >   
   > It's going to depend on the O/S - or more correctly, the network   
   > stack, but go for it.  Most IPv4 stacks allow MTU to be set as easily   
   > as network mask or IP address.   
      
   Perhaps I was unclear -- I never claimed there were no tools for   
   "changing" the MTU, just that I don't expect meaningful results when   
   the endpoints on an Ethernet disagree about it.   
      
   When I've done this in Linux (to create and capture a TCP stream with   
   small segments, so I later could replay it over a link with actual   
   lower MTU) things stopped working in unexpected ways.  Lots of trouble   
   and wasted time.   
      
   (Later I discovered the route(8) 'mss' option -- a much better fit for   
   my problem.)   
      
   /Jorgen   
      
   --   
     // Jorgen Grahn    O  o   .   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)