Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.protocols.tcp-ip    |    TCP and IP network protocols.    |    14,669 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 12,912 of 14,669    |
|    pk to Pascal Hambourg    |
|    Re: Path MTU    |
|    03 Jun 09 18:23:42    |
      From: pk@pk.invalid              On Wednesday 3 June 2009 17:43, Pascal Hambourg wrote:              > Hello,       >       > David Schwartz a écrit :       >>       >> I can't figure out what you're talking about. What does "enable PMTU       >> on our end-points" mean? You mean enable PMTU detection?       >       > PMTU discovery, I guess.       >       >> If the       >> endpoints do PMTU detection, it doesn't matter what the middle does.       >> The endpoints will figure out the largest packet that arrives       >> unfragmented.       >       > Unless some device in the middle behaves badly and does not send an ICMP       > "fragmentation needed (and DF set)" (or ICMPv6 "packet too big" if using       > IPv6) message when discarding too big a packet. As an example I can       > think about some xDSL architectures cascading PPPoE links (MTU 1492) and       > L2TP tunnels with MTU 1500 at the link layer level without intermediate       > routing.              Right, or another problem is when there is some device in the return path       that blocks such ICMP packets, so the source doesn't receive the PMTU       information, thus breaking the PMTU discovery process.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca