Pinan
Hypnotic Tweaker
ExMod 2000-03
join:2000-09-02
Murrieta, CA
|  XP users: There is no tweak yet to raise MTU......
from 1480. This is caused by the internal PPPoE connection software in WinXP, for PPPoE users only. Changing to RASPPPoE is so far the only way to achieve 1492 IPMTU.
Non PPPoE users will have 1500 MTU, providing no routers or whatever, are interfering.
The good news is that this is not important, as that little of a change will prove negligible, speed wise. So relax and enjoy your new OS. Us anal Tweakers will come up with a way to raise it after awhile, if not simply to satisfy our need for perfection, and closure. 
--
Never mistake kindness for weakness.
This is The United States of America! |
|
R2
R Not
Premium,MVM
join:2000-09-18
Long Beach, CA
clubs: | But I want those 12 bytes!!!!!! |
|
LinuxMan40
join:2001-03-08
Centreville, VA
| reply to Pinan
Maybe this will shed some light of hope!
Here is link to Microsoft web site to change the mtu in Windows XP
»support.microsoft.com/support/kb···1/65.ASP
It work for me! |
|
Pinan
Hypnotic Tweaker
ExMod 2000-03
join:2000-09-02
Murrieta, CA
| We of course have seen that, and have not seen it work for posters using the built in PPPoE software. You of course are using RASPPPoE.
--
Never mistake kindness for weakness.
This is The United States of America!
[text was edited by author 2001-10-27 13:00:18] |
|
turfboy
join:2001-10-17
Palm Springs, CA
| reply to Pinan
DWORD VALUE = MTU ---here is my fix for xp
sorry bout the autoquote...
I tend to disagree..when i change this value my MTU changes.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\Tcpip\Parameters\Interfaces\{C9***8A8-D39 A-4FBE-8A9F-8FA***EC20**}
DWORD VALUE = MTU
Value Data = (decimal)1480
--
Toeknee |
|
JSY
Premium
join:2000-04-05
Elmhurst, NY
clubs: |  reply to Pinan
Re: XP users: There is no tweak yet to raise MTU......
I am a non-PPPOE user, and maybe I'm confused by it all, but I can only ping through with the highest at 1472 bytes. Is the remaining 28 bytes overhead? Or am I doing something wrong? Oh, yes - WinXP using RR Cable. Thanks.. |
|
Lanik
Lab-nik
Premium,ExMod 2002-03
join:2001-06-25
Bay Area |  Nope the remaining 28 bytes are the TCP/IP protocol header.
--
McLarenF1 -- can I have one please pretty please? |
|
Pinan
Hypnotic Tweaker
ExMod 2000-03
join:2000-09-02
Murrieta, CA | reply to turfboy
Re: DWORD VALUE = MTU ---here is my fix for xp
Have you gotten it to 1492 with this? You did not state. |
|
redxii
too big to fail
Premium,Mod
join:2001-02-26
Texas
Host:
/dev/null
Broadband Tweaks
Suddenlink
ISDN
Fiber Optic
| reply to turfboy
Too many variables for different computers. Have to have a solid fix that will work on every computer. Not every one might have CurrentControlSet00#.
--
C:\bin\laden>DEL OSAMA.EXE
Improve your 56K Internet Experience! |
|
R2
R Not
Premium,MVM
join:2000-09-18
Long Beach, CA
clubs:
| reply to Lanik
Re: XP users: There is no tweak yet to raise MTU......
Actually, the remaining 28 bytes are the ICMP (8) and IP (20) headers, but who's counting?
_____________
As for the ControlSet #'s, those are just for various backup settings. The "CurrentControlSet" is the one that is being used, eh, currently. Here is how Microsoft describes it for Win2K:The numbered ControlSet00n subkeys, such as ControlSet001 and ControlSet002, contain control sets that can be used to start and run Windows 2000. Most systems have two numbered control sets, an original and a backup copy of a control set that has been used to start the system successfully, but the system can maintain as many as four control sets. Windows 2000 maintains backup copies so that you can undo configuration changes that might otherwise prevent you from starting the system.
Windows 2000 identifies the control set that was last used successfully, the current control set, and the default control set. These designations are stored in the Select subkey.
Windows 2000 automatically maintains the control sets and selects one of them when the system starts. It bases this selection on settings in the Select subkey and on the success or failure of system startup. When the system starts, users can also select the LastKnownGood control set during the boot loader procedure.
All the numbered control set subkeys, including the one that appears in the CurrentControlSet subkey, can have the same subkeys and entries. The standard location for MTU in Win2K is:HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{inte rface} For WinNT, the location was:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\{interface}\Parameters\Tcpip -- and one time I saw a Win2K system use this same spot for a PPPoE connection.
The key that turfboy lists in ControlSet003 should be set the same in the CurrentControlSet -- or it will not be current. Or, if you desire, you should set it exactly the same in ALL ControlSets and then it will always be current.
Additionally, turfboy's key appears to be the STANDARD location for MTU in Win2K -- as long hex number is for his NIC. I would be surprised if this was successful -- since DrTCP adjusts this location as well. The hex number that turfboy lists will be specific to his system, so it is not a universal number.
I would have to wonder if this is not the interface number of his NIC? If it is not for his NIC, then this would be far more intriguing.
[text was edited by author 2001-10-28 10:58:23] |
|
jatoki
join:2001-06-07
Chagrin Falls, OH | reply to Pinan
Thanks for allowing a better night's sleep....
I ram/rumbled around "regedit" way too long last night trying to boost the MTU -- before I came upon your XP explanation. Thank you, good sir. |
|
Bob Carrick
Premium,ExMod 2002
join:2000-04-24
New York, NY
| reply to Pinan
Re: XP users: There is no tweak yet to raise MTU......
I've got a registry patch, that you can merge into the registry that I will be testing today to hopefully solve this problem. If so I'll post in this forum and let y'all know.
--
Bob
»www.carricksolutions.com - The largest PPPoE FAQ & How To database on the web, including EnterNet, WinPoet, MacPoet, Access Manager and RASPPPoE |
|
R2
R Not
Premium,MVM
join:2000-09-18
Long Beach, CA
clubs:
| The big question -- is it a "problem"?
What is the value of 12-bytes?
I know, it can be argued that every byte counts, but in terms of download speed, it is not likely to make a HUGE difference.
_______________________________________________
I find this whole thing funny. NTS-EnterNet have argued for years that 1454 is the EXACT best size packet for PPPoE. There is web site that gives a detailed explanation as to why this MUST be true.
Yet, WindowsXP uses a size of 1480. Hmmm... Is Microsoft wrong? Why aren't they agreeing with NTS?
And what is the extra 12 bytes for? Everyone knows the PPPoE wrapper is 8 bytes -- so what is up with the 20-byte snip? What is going on?
I would love to see the explanation behind the decision to limit the MTU to 1480 -- but I doubt I will ever see it...
_______________________________________________
Question: what happens in WindowsXP/PPPoE if you try to ping your largest packet size? Is it 1464 or 1452???
[text was edited by author 2001-11-01 11:15:05] |
|
Bob Carrick
Premium,ExMod 2002
join:2000-04-24
New York, NY
| 1480 seems to be a problem for some people unfortunately. Most people do not ever need to go below 1454, which is why NTS uses that value. 6 of one 1/2 dozen of the other. I've tested this MTU tweak ran tweak tests from 2 sites and it still reports an MTU of 1480 so this leads me to believe it does not work either.
--
Bob
»www.carricksolutions.com - The largest PPPoE FAQ & How To database on the web, including EnterNet, WinPoet, MacPoet, Access Manager and RASPPPoE |
|
R2
R Not
Premium,MVM
join:2000-09-18
Long Beach, CA
clubs: | Why is 1480 a problem and 1492 not?
Or is it that 1480 is a problem and users must use the NTS 1454?
(I never used PPPoE so my questions are out of interest only). |
|
Bob Carrick
Premium,ExMod 2002
join:2000-04-24
New York, NY
| reply to Pinan
I'm trying to find out why 1480. I believe 1480 is the appropriate number if using PPPoE over ATM (if your ISP has ATM in between you and it's SMS unit). Some people need 1454 depending on how their ISP has set up their network.
--
Bob
»www.carricksolutions.com - The largest PPPoE FAQ & How To database on the web, including EnterNet, WinPoet, MacPoet, Access Manager and RASPPPoE |
|
R2
R Not
Premium,MVM
join:2000-09-18
Long Beach, CA
clubs: | The one argument I saw in favor of 1454 was because of the ATM issue. It would be interesting to see this same argument used for 1480.
Again, I don't have any answer or even any insight. I just find the differences amusing... Thanks Bob. |
|
Pinan
Hypnotic Tweaker
ExMod 2000-03
join:2000-09-02
Murrieta, CA | For me it's an anal thing. Gotta have that 1492.;)
Thanks Bob, let us know. |
|
Anon | reply to Pinan
It appears that XP pppoe client has problems. Using the same ethernet modem on two different machines at different time the through put on the win 98 2nd edition runs about 800-976 (down) kbits/sec where as the XP using XP pppoe runs at 200-350 kbit/sec. Both of these systems use the same dsl line (one system connecte to the dsl line at a time).
does any one have suggestions on how to improve my down load speed...
Thansk |
|
Lanik
Lab-nik
Premium,ExMod 2002-03
join:2001-06-25
Bay Area
| You might need to get your XP tweaked. Most people don't notice a difference but there have been a few reports of the same. Ether case please click a link on top "new topic" if you want to get your XP tweaked.
--
McLarenF1 -- can I have one please pretty please? |
|
