3 replies
by robo_dev
The actual MTU is 'Packet size' + 28, you need to allow for the header when using ping command to determine MTU. So when you give a length of 1500, you're trying to send 1528 byte packets which is too big.
To test for 1500 byte packets, the magic number is 1472
But, ping www.google.com -f -l 1472 is not likely to work either, in most cases about 1460 is the most that will typically fly over the internet. You typically should be able to get a 1472 byte ping response from your own router, however.
The MTU and the RWIN are not as directly linked as one would think because both pathMTU discovery, which is active in many internet routers, pretty much makes things very optimal most of the time.
RWIN is the TCP windowing size. This is the amount of data that a sender on a network will send before requiring an acknowledgment from the receiver. This is usually the parameter that gets tweaked on 'speed up' software for slower links.
A higher RWIN number allows a sender to send more data over a slow link, before requiring an acknowledge packet.
BUT, if the link drops a lot of packets, a high RWIN can slow things down, since it will have to resend all data after the dropped packet is resent.
The reality is that it really doesn't matter. With a sufficiently high RWIN, you shouldn't really have to worry about the occasional partial packet because of the MTU setting. And, as I said, most systems automatically set MTU, so you really can't control it anyway, except to make it smaller. Some systems set RWIN dynamically as well.
So the long answer to a short question is that there is nothing wrong with your configuration. A RWIN of 32767 is totally OK. Personally I've never noticed a dramatic difference after tweaking mtu/rwin settings.
by avila
Hi,
I recommend you to use TCPOptimizer (just google it for download, it's free), if remember correctly it sets the best configuration for your computer.
Regards,
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending