Comments on: TCP/IP MTU and MSShttp://itknowledgeexchange.techtarget.com/itanswers/tcpip-mtu-and-mss/
Fri, 09 Dec 2016 16:23:18 +0000hourly1By: buchankashttp://itknowledgeexchange.techtarget.com/itanswers/tcpip-mtu-and-mss/#comment-89646
Sat, 19 Mar 2011 20:44:20 +0000#comment-89646” It may be that you are seeing the packets before they hit the wire and are fragmented when reaching the destination. Try capturing on both sides and see if the results are similar. ”

That was it! The capture was at the sending device, which I thought Wireshark would show them already divided into pieces, but it only shows the segments divided in the receiving device! Thanks a lot!!

Also, if the MSS should be at 536, is it possible that a single IP packet could contain two TCP segments or each IP packet must contatain exactly one TCP segment?

Thanks again

]]>By: buchankashttp://itknowledgeexchange.techtarget.com/itanswers/tcpip-mtu-and-mss/#comment-89172
Wed, 09 Mar 2011 20:20:20 +0000#comment-89172Hey, sorry about the delay, I have been very busy at work. And sorry, I meant WIRESHARK!! Don’t know where I got this fire from…

It would take sometime to mount the setup again to print an output. Do you really think that would be necessary?

Basically, the question is why host A is sending host B (and vice-versa) a TCP segement with over 4000 bytes within my LAN, since the LAN IP MTU size is 1500 bytes and TCP MSS is 1460. Shouldn’t this segment be broken into 1460 or 1500 pieces? In Wireshark it shows just a single message with 4000-byte long received.

Also, the jumbo packet feature in my ethernet adapter is set to 1514 bytes.

Thanks!

]]>By: sixballhttp://itknowledgeexchange.techtarget.com/itanswers/tcpip-mtu-and-mss/#comment-88771
Mon, 28 Feb 2011 14:48:01 +0000#comment-88771Just a quick question, did you intentionally mention FIRESHARK, or were you elluding to WIRESHARK – as they do completely different functions..

Also, please post some of the output of your analyzer so we can better assist you