PATHMTU

2009-12-11 Thread Christy Brogan
We are currently moving from z/VM 5.3 to z/VM 5.4. We are wondering what to do with TCPIP and the new PATHMTU and PATHMTUAGE . Currently we have left it out so it is disabled and apparently defaults to Path MTU Discovery Aging Interval of 10 minutes (per NETSTAT GATE). In looking at the TCPIP

Re: PATHMTU

2009-12-11 Thread Quay, Jonathan (IHG)
of which are external network providers in our case), AND that firewalls had to allow the ICMP traffic through. There is also a rumor floating around that PATHMTU results in the do not fragment' bit always being set on. Which seems very scary and wrong. From

Re: PATHMTU

2009-12-11 Thread Miguel Delapaz
, this makes the algorithm faster and more accurate, but it is not a requirement. If we never receive the ICMP packet, the stack will eventually adjust the MTU as above. There is also a rumor floating around that PATHMTU results in the “do not fragment’ bit always being set on. Which seems very scary

Re: PATHMTU

2009-12-11 Thread Christy Brogan
: | | | |Re: PATHMTU

Re: PATHMTU

2009-12-11 Thread David Boyes
a rumor floating around that PATHMTU results in the do not fragment' bit always being set on. Which seems very scary and wrong. That was true of a buggy release of the Windows TCP stack a long while ago. That's been fixed mostly, but since most people use Ethernet inside their network