Tweak Test Results

Get help and discuss anything related to tweaking your internet connection, as well as the different tools and registry patches on the site. TCP Optimizer settings and Analyzer results should be posted here.
Post Reply
User avatar
cablenut
Advanced Member
Posts: 863
Joined: Fri Aug 25, 2000 12:00 am
Location: Indianapolis, IN

Tweak Test Results

Post by cablenut »

Lobo wanted to see my tweak test here it is:

TCP options string = 0204059c01010402

MTU = 1476

MTU is not at an optimal value... Consider increasing your MTU to 1500 for optimal throughput.

MSS = 1436

Maximum useful data in each packet = 1436, which seems to be equal to MSS.

MSS is not fully optimized for broadband (although it might work well for slower connections). Consider increasing your MTU value.

Default Receive Window (RWIN) = 63184
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 63184

RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
252736 (MSS x 44 * scale factor of 4)
189552 (MSS x 44 * scale factor of 3)
126368 (MSS x 44 * scale factor of 2)
63184 (MSS x 44)

bandwidth * delay product:

Your RcvWindow limits you to: 5054.72 kbps (631.84 KBytes/s) @ 100ms
Your RcvWindow limits you to: 2527.36 kbps (315.92 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1010.944 kbps (126.368 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = true

Time to live = 245 hops

Timestamps (RFC1323) = false

Selective Acknowledgements (RFC2018) = true

IP type of service = x

[ 03-06-2001: Message edited by: cablenut ]
Head webcheese and geek guru @ http://www.cablenut.com
User avatar
cablenut
Advanced Member
Posts: 863
Joined: Fri Aug 25, 2000 12:00 am
Location: Indianapolis, IN

Post by cablenut »

Post your tweak results in this thread for good ol' Cablenut to look at :)
Head webcheese and geek guru @ http://www.cablenut.com
User avatar
Qwijib0
Posts: 8268
Joined: Sun Jan 14, 2001 12:00 am
Location: Tucson, Arizona Processor: GenuineIntel Member #4896

Post by Qwijib0 »

TCP options string = 020405b4010303030101080a000000000000000001010402

MTU = 1500

MTU is at optimal value

MSS = 1460

Maximum useful data in each packet = 1448, which is less than MSS because of Timestamps, or other TCP options used

Default Receive Window (RWIN) = 373760
RWIN Scaling (RFC1323) = 3 bits
Unscaled Receive Window = 46720

RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
256960 (MSS x 44 * scale factor of 4)
192720 (MSS x 44 * scale factor of 3)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)

bandwidth * delay product:

Your RcvWindow limits you to: 29900.8 kbps (3737.6 KBytes/s) @ 100ms
Your RcvWindow limits you to: 14950.4 kbps (1868.8 KBytes/s) @ 200ms
Your RcvWindow limits you to: 5980.16 kbps (747.52 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = true

Time to live = 19 hops

Timestamps (RFC1323) = true

Selective Acknowledgements (RFC2018) = true

IP type of service = 0
If your browser can't read unicode, you should probably switch! ;)
User avatar
dannjr
Posts: 2233
Joined: Tue Jul 11, 2000 12:00 am
Location: Chicago

Post by dannjr »

TCP options string = 0204059c0103030301010402

MTU = 1476

MTU is not at an optimal value... Consider increasing your MTU to 1500 for optimal throughput.

MSS = 1436

Maximum useful data in each packet = 1436, which seems to be equal to MSS.

MSS is not fully optimized for broadband (although it might work well for slower connections). Consider increasing your MTU value.

Default Receive Window (RWIN) = 371712
RWIN Scaling (RFC1323) = 3 bits
Unscaled Receive Window = 46464

For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
252736 (MSS x 44 * scale factor of 4)
189552 (MSS x 44 * scale factor of 3)
126368 (MSS x 44 * scale factor of 2)
63184 (MSS x 44)

bandwidth * delay product:

Your RcvWindow limits you to: 29736.96 kbps (3717.12 KBytes/s) @ 100ms
Your RcvWindow limits you to: 14868.48 kbps (1858.56 KBytes/s) @ 200ms
Your RcvWindow limits you to: 5947.392 kbps (743.424 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = true

Time to live = 247 hops

Timestamps (RFC1323) = false

Selective Acknowledgements (RFC2018) = true

IP type of service = MAJOR SECRET
User avatar
dannjr
Posts: 2233
Joined: Tue Jul 11, 2000 12:00 am
Location: Chicago

Post by dannjr »

TCP options string = 0204059c010303030101080a000000000000000001010402

MTU = 1476

MTU is not at an optimal value... Consider increasing your MTU to 1500 for optimal throughput.

MSS = 1436

Maximum useful data in each packet = 1424, which is less than MSS because of Timestamps, or other TCP options used

MSS is not fully optimized for broadband (although it might work well for slower connections). Consider increasing your MTU value.

Default Receive Window (RWIN) = 510712
RWIN Scaling (RFC1323) = 3 bits
Unscaled Receive Window = 63839

For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
252736 (MSS x 44 * scale factor of 4)
189552 (MSS x 44 * scale factor of 3)
126368 (MSS x 44 * scale factor of 2)
63184 (MSS x 44)

bandwidth * delay product:

Your RcvWindow limits you to: 40856.96 kbps (5107.12 KBytes/s) @ 100ms
Your RcvWindow limits you to: 20428.48 kbps (2553.56 KBytes/s) @ 200ms
Your RcvWindow limits you to: 8171.392 kbps (1021.424 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = true

Time to live = 247 hops

Timestamps (RFC1323) = true

Selective Acknowledgements (RFC2018) = true

IP type of service field = shhh Its a secret
User avatar
Philip
SG VIP
Posts: 11761
Joined: Sat May 08, 1999 5:00 am
Location: Jacksonville, Florida

Post by Philip »

Hmm... Is QoS of 111 the best ?

;)
User avatar
Prey521
Posts: 34932
Joined: Sat Feb 05, 2000 12:00 pm
Location: Humble, Tx

Post by Prey521 »

Originally posted by Philip:
Hmm... Is QoS of 111 the best ?

;)
<Prey Scratching Head> This must be one of those tech terms which I know nothing of :D
owned by pac0z atm

User avatar
dannjr
Posts: 2233
Joined: Tue Jul 11, 2000 12:00 am
Location: Chicago

Post by dannjr »

:D :D :D
User avatar
blebs
Posts: 12819
Joined: Sat Dec 02, 2000 12:00 am
Location: North Canton, Ohio

Post by blebs »

SpeedGuide.net TCP/IP Analyzer
TCP properties for IP = 24.xxx.xxx.xxx
TCP options string = 020405b4010303020101080a000000000000000001010402

MTU = 1500

MTU is at optimal value

MSS = 1460

Maximum useful data in each packet = 1448, which is less than MSS because of Timestamps, or other TCP options used

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:
256960 (MSS x 44 * scale factor of 4)
192720 (MSS x 44 * scale factor of 3)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)

bandwidth * delay product:

Your RcvWindow limits you to: 20556.8 kbps (2569.6 KBytes/s) @ 100ms
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) = true

Time to live = 50 hops

Timestamps (RFC1323) = true

Selective Acknowledgements (RFC2018) = true

IP type of service field = 00000000
Success is a lousy teacher. It seduces people into thinking they can't lose. -Bill Gates
Lobo

Post by Lobo »

OK here's mine, pretty neat huh:
SpeedGuide.net TCP/IP Analyzer
TCP properties for IP = x
TCP options string = 02040551010303000101080a000000000000000001010402

MTU = 1401

MTU is not at an optimal value... Consider increasing your MTU to 1500 for optimal throughput.

MSS = 1361

Maximum useful data in each packet = 1349, which is less than MSS because of Timestamps, or other TCP options used

MSS is not fully optimized for broadband (although it might work well for slower connections). Consider increasing your MTU value.

Default Receive Window (RWIN) = 14867
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 14867

For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
261312 (MSS x 48 * scale factor of 4)
195984 (MSS x 48 * scale factor of 3)
130656 (MSS x 48 * scale factor of 2)
65328 (MSS x 48)

bandwidth * delay product:

Your RcvWindow limits you to: 1189.36 kbps (148.67 KBytes/s) @ 100ms
Your RcvWindow limits you to: 594.68 kbps (74.335 KBytes/s) @ 200ms
Your RcvWindow limits you to: 237.872 kbps (29.734 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = true

Time to live = 53 hops

Timestamps (RFC1323) = true

Selective Acknowledgements (RFC2018) = true

IP type of service field = 00000000


:eek:
Lobo

Post by Lobo »

Works goog Phillip, right on the money, keep up good work, you & friend :)
User avatar
Buggyman
Posts: 587
Joined: Thu Jan 25, 2001 12:00 am
Location: Somewhere in Florida

Post by Buggyman »

TCP options string = 020405b401010402

MTU = 1500

MTU is at optimal value

MSS = 1460

Maximum useful data in each packet = 1460, which seems to be equal to MSS.

Default Receive Window (RWIN) = 64240
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 64240

RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
256960 (MSS x 44 * scale factor of 4)
192720 (MSS x 44 * scale factor of 3)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)

bandwidth * delay product:

Your RcvWindow limits you to: 5139.2 kbps (642.4 KBytes/s) @ 100ms
Your RcvWindow limits you to: 2569.6 kbps (321.2 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1027.84 kbps (128.48 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = true

Time to live = 241 hops

Timestamps (RFC1323) = false

Selective Acknowledgements (RFC2018) = true

IP type of service field = (Classified Info)

Precedence (QoS) = 000
Delay = 1
Throughput = 1
Reliability = 1
Cost = 0

[ 03-07-2001: Message edited by: Buggyman ]
No Question is a dumb Question when it comes to Tweaking!
Post Reply