| reply to stevemayman
Re: [Other] MTU quandry! When TCP/IP communicates with it needs to set certain things so that the traffic has no issues before it can proceed. example when you want to hit www.google.com your linksys tells your PC that 1492 is the right MTU for communicating with google. However, when the packet is moving to google that MTU may actually change by another device (such as a VPN) and drop the MTU to 1300. the user is not involved in this process and hence does not notice this issue and in reality this is really the case as every where you visit might have a different capability for example if you change your PCs MTU to 1492, than it might effect the local LAN speed. As an example Gigabit Ehernet can handle Jumbo Frames (MTU of 9216)..
Again, I would leave all the local LAN PCs alone as they communicate with each other... what I would do is to look at the cabling and make sure that there is no collision occuring as these collisions cause more problems than a miss guided MTU ...  |
|
| Thanks. That points me in the right direction. I guess your advice would be to set our routers to "Auto" and to leave our PCs at the default settings. For those that have already been manually set, will using DrTCP and deleting the MTU value essentially reset them to dynamically adjusting?
In your last paragraph you mentioned cabling issues and making sure there are no collisions. You don't mean the physical cables do you? I am guessing that this is beyond the scope of this forum, but is there a good place I could look to help me sort it out?
This may indeed be the problem because we have a Linksys WAP/4-port router at one end of the office connected to a Linksys 8-port switch at the other end of the office with a cat-5 cable. All the ports on each device are full. Things seem to work well most of the time, but the network freezes occasionally for 30 to 60 seconds. Sometimes we power cycle the WAP which gets things going again.
Any ideas?
Thanks again!
Steve |
|
|
|
| wow, great information... you see the 8 port switch should not see any collisions as they are full duplex(you have mentione that above) but the WAP uses a 4 port HUB... this is the reason why sometimes on a busy day broadcasts from multiple PCs can Freeze the network... to improve the situation is to add a switch and plug all the devices attached to the WAP hub on to the switch than by connecting the switch to the WAP will give you a smoother network reliability...
I hope that made sense |
|
| Yes, that made perfect sense. I would gladly buy a switch in hopes of fixing the problem. Unfortunately when I took another look at the router it turned that it is a switch after all. I guess there is no magic bullet for us, but thanks for your help!
Steve |
|
 cdruGo ColtsPremium,MVM
join:2003-05-14
Fort Wayne, IN
kudos:5
 ·Frontier FiOS
| reply to Da Geek Kid
said by Da Geek Kid:When TCP/IP communicates with it needs to set certain things so that the traffic has no issues before it can proceed. example when you want to hit www.google.com your linksys tells your PC that 1492 is the right MTU for communicating with google. However, when the packet is moving to google that MTU may actually change by another device (such as a VPN) and drop the MTU to 1300. the user is not involved in this process and hence does not notice this issue and in reality this is really the case as every where you visit might have a different capability for example if you change your PCs MTU to 1492, than it might effect the local LAN speed. As an example Gigabit Ehernet can handle Jumbo Frames (MTU of 9216).. The issue with MTU is that you want to get the maximum amount of data in each packet to minimize the effect of packet overhead. Each packet has a little bit of overhead. Straight TCP/IP over Ethernet has relatively little. PPPoE adds a little more (hence the 1492 instead of 1500). VPN has quite a bit more, etc. Normally the two machines will try to negotiate a happy number were the sending computer sends data that completely fills what the receiving computer (or some computer inbetween) will accept.
However in some cases there is a chance that a packet needs to get fragmented. For instance if the sending computer sends a 1500 byte packet but the path takes the packet across a PPPoE link in route to the receiving computer, it will get split up into a 1492 byte packet and a 8 byte packet. In the case of the 8 byte packet you are "paying" the overhead for another 1484 bytes of data, but you aren't actually sending it so that slice of bandwidth is gone.
Typically speaking you want to set your MTU as high as possible between you and your ISP and let the rest of everything handle itself automatically. If you are on PPPoE, set it at 1492. Most other DSL and cable connections are 1500. If you have something else, well it could be different.
--
Quis custodiet custodes ipsos? |
|
