Help

[agustintorre]

Hello, I am trying to learn more about my cable connection, ping, hop, latency, all that etc.
So I was wondering if anyone can tell me what the highlighted in red means??
Thanks.

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 486.17Kb/s
running 10s inbound test (server to client) . . . . . . 4.56Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06

------ 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 = 110.15 msec; the Packet size = 1360 Bytes; and
No packet loss was observed.
This connection is receiver limited 92.16% of the time.
This connection is network limited 7.81% 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
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End

[trogers]

Hello, I am trying to learn more about my cable connection, ping, hop, latency, all that etc.
So I was wondering if anyone can tell me what the highlighted in red means??
Thanks.

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 486.17Kb/s
running 10s inbound test (server to client) . . . . . . 4.56Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode = This is correct. If it shows half duplex then it is not good.
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 110.15 msec; the Packet size = 1360 Bytes; and
No packet loss was observed.
This connection is receiver limited 92.16% of the time.
This connection is network limited 7.81% of the time.


Your connection is receiver limited means the TCP Window is set too low for your bandwidth and signal round trip time (RTT). Sometimes it may not be a fault in TCP Window but a problem with signal round trip time. In your case, RTT is at 110ms which is within the normal values of 90-130ms. So Your TCP Window is set too low for the bandwidth. It should be 130560.

"Network limited" means traffic congestion in the network is limiting your throughput, and thus speed.

[agustintorre]

Your connection is receiver limited means the TCP Window is set too low for your bandwidth and signal round trip time (RTT). Sometimes it may not be a fault in TCP Window but a problem with signal round trip time. In your case, RTT is at 110ms which is within the normal values of 90-130ms. So Your TCP Window is set too low for the bandwidth. It should be 130560.
"Network limited" means traffic congestion in the network is limiting your throughput, and thus speed.

So should I change my tcp to130560??
Thanks.

[trogers]

So should I change my tcp to130560??
Thanks.

I think you have used TCP Window at 65280 to try to get lower ping times even though speed will be lower. If your ping times are not lower as intended, then you should set TCP Window to 130560.

[agustintorre]

O ok ya when you gave me the new tweak to make my packets smaller it worked!! lowerd by 10.... umm i dont now wat its called, but it was my ping that lowerd.
I will just keep my tcp to what it is now thanks for the help trogers.

[agustintorre]

lol... this is kinda wierd my speed hasent reely lowerd with the lowering of tcp, but my ping has lowerd!!:D

<a href="http://www.speedtest.net"><img src="http://www.speedtest.net/result/72754171.png"></a>

[agustintorre]

sorry wrong link

http://www.speedtest.net/result/72754171.png

[trogers]

sorry wrong link

http://www.speedtest.net/result/72754171.png

Much depends on the latency (RTT).

Throughput = TCP Window x 8 divided by latency

If latency falls, throughput increases and vice versa.

In the nitro test, your latency is 110ms. In this speedtest, your latency is only 76ms.

[agustintorre]

ok thanks