HELLLP lol...I previously used the Speedcorp patch w/o any problems...decided to play with Cablenut 4.02 (WinME here) I uninstalled the Speedcorp patch prior to installing cablenut...installed the fast cable css file..played with it- decided the old patch was faster...removed patch w/option in program, then tried to re-install Speedguide...this is what I get now...
TCP options string = 020405c20103030201010402
MTU = 1514
Your MTU value seems to be larger than the Ethernet specs, consider lowering it to 1500 or 1496.
If you're on DSL that uses PPPoE, the maximum allowed packet size is 1492.
MSS = 1474
Maximum useful data in each packet = 1474, which is equal to MSS.
Default Receive Window (RWIN) = 256960
RWIN Scaling (RFC1323) = 2 bits
Unscaled Receive Window = 64240
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
518848 (MSS x 44 * scale factor of 8)
259424 (MSS x 44 * scale factor of 4)
129712 (MSS x 44 * scale factor of 2)
64856 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 10278.4 kbps (1284.8 KBytes/s) @ 200ms
Your RcvWindow limits you to: 4111.36 kbps (513.92 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 20 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
Somethings adding an extra 14 bytes and I have no idea what. Checked the registry and all the mtu/mss values read 1500/1460..what's going on here? Any ideas?
[ 03-26-2001: Message edited by: DainBramage ]
Problem w/ Cablenut Patch
-
Lobo
Everything looks fine but your MAXMTU, MSS will be automatticaly set by Windows 40 less than MTU, go here for tool to set MTU to 1500:Please go to:www.dslreports.com/front/drtcp.html
Download DR. TCP to your desktop
Where it says adapter settings, select your adapter, the only thing you need to do is select your adapter set MAX MTU to 1500, play with it until apply lights up click it, reboot, and repost test here
Download DR. TCP to your desktop
Where it says adapter settings, select your adapter, the only thing you need to do is select your adapter set MAX MTU to 1500, play with it until apply lights up click it, reboot, and repost test here
-
DainBramage
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which is equal to MSS.
Default Receive Window (RWIN) = 256960
RWIN Scaling (RFC1323) = 2 bits
Unscaled Receive Window = 64240
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 10278.4 kbps (1284.8 KBytes/s) @ 200ms
Your RcvWindow limits you to: 4111.36 kbps (513.92 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 20 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
Worked...thanks! Was weird...Speedcorp proggy was reporting 1500/1460 (read from registry) but DrTCP fixed it...
[ 03-26-2001: Message edited by: DainBramage ]
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which is equal to MSS.
Default Receive Window (RWIN) = 256960
RWIN Scaling (RFC1323) = 2 bits
Unscaled Receive Window = 64240
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 10278.4 kbps (1284.8 KBytes/s) @ 200ms
Your RcvWindow limits you to: 4111.36 kbps (513.92 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 20 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
Worked...thanks!
Was weird...Speedcorp proggy was reporting 1500/1460 (read from registry) but DrTCP fixed it...[ 03-26-2001: Message edited by: DainBramage ]