Page 1 of 1

Ill take a whack at it.

Posted: Wed Apr 04, 2001 2:54 pm
by HalfLifer
Is this good?
TCP options string = 020405b4010303030101080a000000000000000001010402

MTU = 1500
MTU is fully optimized for broadband.

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

Default Receive Window (RWIN) = 513920
RWIN Scaling (RFC1323) = 3 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)
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) @ 200ms
Your RcvWindow limits you to: 8222.72 kbps (1027.84 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 22 hops
TTL value is ok.

Timestamps (RFC1323) = ON
Note: Timestamps add 12 bytes to the TCP header of each packet, reducing the space available for useful data.

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349)= 00000000

Posted: Wed Apr 04, 2001 2:57 pm
by g-c0de
bandwidth * delay product:
Your RcvWindow limits you to: 20556.8 kbps (2569.6 KBytes/s) @ 200ms
Your RcvWindow limits you to: 8222.72 kbps (1027.84 KBytes/s) @ 500ms

whoa that looks a little bit too over tweaked

Posted: Wed Apr 04, 2001 3:00 pm
by Lobo
Why such a large RWIN although if it works with no packet loss at night fine and why are timestamps on :)

Posted: Wed Apr 04, 2001 5:12 pm
by Lobo
Our patch does not turn on timestamps nor does Cablenuts, I was just wondering :confused:

Posted: Thu Apr 05, 2001 6:57 am
by HalfLifer
Oh, I turned it on. With that rwin, or any rwin, I NEVER get packetloss, at any given time. And Yes, I can hit a max of 5.5mbps/1.3mbps.

Posted: Thu Apr 05, 2001 8:48 am
by Lobo
Cool, wish I could :)