is this a good for cable?
-
project
is this a good for cable?
i was just wondern if this was good for cable modem or not if not could ya give me some hints on what would be good to do.
TCP options string = 020405b4010303000101080a0000000000000000
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) = 17520
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 17520
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)
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: 700.8 kbps (87.6 KBytes/s) @ 200ms
Your RcvWindow limits you to: 280.32 kbps (35.04 KBytes/s) @ 500ms
Consider increasing your RWIN value to optimize TCP/IP for broadband.
MTU Discovery (RFC1191) = ON
Time to live left = 23 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) = OFF
IP type of service field (RFC1349)= 00000000
TCP options string = 020405b4010303000101080a0000000000000000
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) = 17520
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 17520
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)
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: 700.8 kbps (87.6 KBytes/s) @ 200ms
Your RcvWindow limits you to: 280.32 kbps (35.04 KBytes/s) @ 500ms
Consider increasing your RWIN value to optimize TCP/IP for broadband.
MTU Discovery (RFC1191) = ON
Time to live left = 23 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) = OFF
IP type of service field (RFC1349)= 00000000
-
Lobo
-
Steve12345
- Member
- Posts: 56
- Joined: Sun Mar 25, 2001 12:00 am
-
Steve12345
- Member
- Posts: 56
- Joined: Sun Mar 25, 2001 12:00 am
-
Steve12345
- Member
- Posts: 56
- Joined: Sun Mar 25, 2001 12:00 am
-
Steve12345
- Member
- Posts: 56
- Joined: Sun Mar 25, 2001 12:00 am
Lobo buggy man says he doesn't know how to.
Buggyman
Little Nut
Member # 5
posted April 03, 2001 07:42 PM
--------------------------------------------------------------------------------
ME???
sounds like something Lobo would tell yah!
But hate to disappoint yah!
But I do not know how... and that why when I look at my speed I do this...
[ April 03, 2001: Message edited by: Buggyman ]
--------------------
Running at Broken Warp Speed! Compliments of AT&T Broadband!
--------------------------------------------------------------------------------
Posts: 19 | From: Jacksonville, Florida | Registered: Apr 2001 | IP: Logged

Buggyman
Little Nut
Member # 5
posted April 03, 2001 07:42 PM
--------------------------------------------------------------------------------
ME???
sounds like something Lobo would tell yah!
But hate to disappoint yah!
But I do not know how... and that why when I look at my speed I do this...
[ April 03, 2001: Message edited by: Buggyman ]
--------------------
Running at Broken Warp Speed! Compliments of AT&T Broadband!
--------------------------------------------------------------------------------
Posts: 19 | From: Jacksonville, Florida | Registered: Apr 2001 | IP: Logged