hi!
My MTU value is set to 1492 in the router and also in OS.
Used stuff like Dr. TCP, TCPOptimizer and DFUE-Speed.
speedguide.net always shows me 1448. would be glad if you could give me some ideas!
MTU won't change
One question,CBFH wrote:hi!
My MTU value is set to 1492 in the router and also in OS.
Used stuff like Dr. TCP, TCPOptimizer and DFUE-Speed.
speedguide.net always shows me 1448. would be glad if you could give me some ideas!
Do you have Path MTU discovery enabled? if so it could be your provider has hard set the 1448 MTU in their Routers and that is what the analyzer is picking up. Path MTU discovery reads the fastest MTU the along the entire path between you and the target site and adjusts your MTU automatically to compensate, the 1500 you set is just a suggested. You could turn Path MTU Discovery off but I wouldn't reccommend it.
My dsl modem is integrated into the router (Siemens SX541 WLAN). All I can say is, that I have turned off path mtu discovery. When I set the mtu value in the router below 1448, then speedguide shows exactly the value i configured. But above 1448 there seems to be no other value possible. As I have noticed, there are many more people in the www having exactly the same problem. But I didn't find a solution for that. I don't know whether this depends on my ISP (Freenet/germany) or is a limit of the rasppoe driver that came with win xp. Someone mentioned something with pppoA protocol, but I have no experiences referring to that. I also read about registry entries in wrong directories set by Dr TCP and some other tools. Maybe you can tell me, where the values and strings have to be. .. Finally I'm very confused because I can't figure out where the problem is. Hope you can help. If you need system specs, please tell me. Thank you! edit: I can remember the time, when the ISP recommended the MTU at 1454. To this time the MTU at 1454 was working... when I remember right.Then the limit of 1454 was put aside by the ISP... as I have read in the forums...if it's true, then maybe this is the reason for that. Maybe the router overwrites the values set in the OS also for path mtu discovery in the same way as he does for mtu value. mhpf... I don't know - now I depend on you 