paralaje
01-26-08, 05:14 PM
hi i have WIMAX 2MB, can u give me some advice about tcpOptimizer?
« SpeedGuide.net TCP Analyzer Results »
Tested on: 01.26.2008 16:57
IP address: 190.0.xx.xx
TCP options string: 020405b40103030001010402
MSS: 1460
MTU: 1500
TCP Window: 64240 (multiple of MSS)
RWIN Scaling: 0
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 2570kbps (321KBytes/s)
BDP limit (500ms): 1028kbps (128KBytes/s)
MTU Discovery: ON
TTL: 96
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)
***************************
http://nitro.ucsc.edu/
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 109.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 718.08kb/s
------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_03
------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 562.42 msec; the Packet size = 1460 Bytes; and
No packet loss was observed.
C2S throughput test: Packet queuing detected: 11.22%
S2C throughput test: Packet queuing detected: 14.71%
This connection is receiver limited 78.23% of the time.
Increasing the the client's receive buffer (62.0 KB) will improve performance
This connection is network limited 21.61% of the time.
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF
Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
« SpeedGuide.net TCP Analyzer Results »
Tested on: 01.26.2008 16:57
IP address: 190.0.xx.xx
TCP options string: 020405b40103030001010402
MSS: 1460
MTU: 1500
TCP Window: 64240 (multiple of MSS)
RWIN Scaling: 0
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 2570kbps (321KBytes/s)
BDP limit (500ms): 1028kbps (128KBytes/s)
MTU Discovery: ON
TTL: 96
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)
***************************
http://nitro.ucsc.edu/
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 109.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 718.08kb/s
------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_03
------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 562.42 msec; the Packet size = 1460 Bytes; and
No packet loss was observed.
C2S throughput test: Packet queuing detected: 11.22%
S2C throughput test: Packet queuing detected: 14.71%
This connection is receiver limited 78.23% of the time.
Increasing the the client's receive buffer (62.0 KB) will improve performance
This connection is network limited 21.61% of the time.
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF
Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address