DJVageli Posted January 2, 2005 CID Share Posted January 2, 2005 I went to this site and took a internet test (all around) http://miranda.ctd.anl.gov:7123/ Now does anybody in this site understand these things? WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 439.27Kb/s running 10s inbound test (server to client) . . . . . . 4.52Mb/s ------ Client System Details ------ OS data: Name = Windows XP, Architecture = x86, Version = 5.1 Java data: Vendor = Sun Microsystems Inc., Version = 1.4.2 ------ Web100 Detailed Analysis ------ Cable modem/DSL/T1 link found. Link set to Half Duplex mode No network congestion discovered. Good network cable(s) found Normal duplex operation found. Web100 reports the Round trip time = 208.53 msec; the Packet size = 1380 Bytes; and No packet loss was observed. This connection is receiver limited 86.68% of the time. This connection is network limited 13.29% 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: ON Information: Network Middlebox is modifying MSS variable Server IP addresses are preserved End-to-End Quote Link to comment Share on other sites More sharing options...
DJVageli Posted January 2, 2005 Author CID Share Posted January 2, 2005 And this: Checking for mismatch condition (cwndtime > .3) [0.13>.3], (MaxSsthresh > 0) [0>0], (PktsRetrans/sec > 2) [0>2], (estimate > 2) [50.49>2] Checking for mismatch on uplink (speed > 50 [0>50], (xmitspeed < 5) [0.43<5] (rwintime > .9) [0.86>.9], (loss < .01) [1.0E<.01] Checking for excessive errors condition (loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.13>.6], (loss < .01) [1.0E<.01], (MaxSsthresh > 0) [0>0] Checking for 10 Mbps link (speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0] (xmitspeed < 9.5) [0.43<9.5] (loss < .01) [1.0E<.01], (mylink > 0) [3.0>0] Checking for Wireless link (sendtime = 0) [3.0E=0], (speed < 5) [0<5] (Estimate > 50 [50.49>50], (Rwintime > 90) [0.86>.90] (RwinTrans/CwndTrans = 1) [1/1=1], (mylink > 0) [3.0>0] Checking for DSL/Cable Modem link (speed < 2) [0<2], (SndLimTransSender = 0) [1=0] (SendTime = 0) [3.0E-4=0], (mylink > 0) [3.0>0] Checking for half-duplex condition (rwintime > .95) [0.86>.95], (RwinTrans/sec > 30) [0.1>30], (SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10] Checking for congestion (cwndtime > .02) [0.13>.02], (mismatch = 0) [0=0] (MaxSsthresh > 0) [0>0] estimate = 50.49 based on packet size = 10Kbits, RTT = 208.53msec, and loss = 1.0E-6 The theoretical network limit is 50.49 Mbps The NDT server has a 8192.0 KByte buffer which limits the throughput to 306.90 Mbps Your PC/Workstation has a 126.0 KByte buffer which limits the throughput to 4.74 Mbps The network based flow control limits the throughput to 4.79 Mbps Client Data reports link is 'T1', Client Acks report link is 'T1' Server Data reports link is 'Ethernet', Server Acks report link is 'Ethernet' Quote Link to comment Share on other sites More sharing options...
MICROWAVE Posted January 2, 2005 CID Share Posted January 2, 2005 DJVageli , yeah I know what most of it is, its stuff that doest help you,unless your trouble shooting an issue.I have tested on that site before and it has some issues that are totally wrong and it is not very accurate at times but it can see web conditions and indicate if there is a overall INTERNET backup or a bottleneck with your ISP.....lots and lots of useless information unless you have a specific reason to need such data....but it is fun to look at , at least a few times.....LOL.... its been around awhile I think it in northern California. Microwave Quote Link to comment Share on other sites More sharing options...
VanBuren Posted January 2, 2005 CID Share Posted January 2, 2005 Alot of that info is above my knowledge and i think MICROWAVE is right, alot of that info is not very useful. VanBuren Quote Link to comment Share on other sites More sharing options...
VanBuren Posted January 2, 2005 CID Share Posted January 2, 2005 This is what i get TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Another client is currently being served, your test will begin within 45 seconds Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 7.13Mb/s running 10s inbound test (server to client) . . . . . . 7.31Mb/s The slowest link in the end-to-end path is a 10 Mbps Ethernet subnet click START to re-test ------ Web100 Detailed Analysis ------ 10 Mbps Ethernet link found. Link set to Half Duplex mode No network congestion discovered. Good network cable(s) found Normal duplex operation found. Web100 reports the Round trip time = 318.9 msec; the Packet size = 1380 Bytes; and No packet loss was observed. This connection is receiver limited 68.33% of the time. This connection is network limited 31.65% of the time. Contact your local network administrator to report a network problem 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: ON Information: Network Middlebox is modifying MSS variable Server IP addresses are preserved End-to-End Client IP addresses are preserved End-to-End rwintime: 0.6833 sendtime: 0.0003 cwndtime: 0.3165 rwin: 2.9297 swin: 64.0000 cwin: 2.9375 rttsec: 0.318903 Sndbuf: 8388608 Checking for mismatch condition (cwndtime > .3) [0.31>.3], (MaxSsthresh > 0) [0>0], (PktsRetrans/sec > 2) [0>2], (estimate > 2) [33.01>2] Checking for mismatch on uplink (speed > 50 [0>50], (xmitspeed < 5) [7.13<5] (rwintime > .9) [0.68>.9], (loss < .01) [1.0E<.01] Checking for excessive errors condition (loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.31>.6], (loss < .01) [1.0E<.01], (MaxSsthresh > 0) [0>0] Checking for 10 Mbps link (speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0] (xmitspeed < 9.5) [7.13<9.5] (loss < .01) [1.0E<.01], (mylink > 0) [10.0>0] Checking for Wireless link (sendtime = 0) [3.0E=0], (speed < 5) [0<5] (Estimate > 50 [33.01>50], (Rwintime > 90) [0.68>.90] (RwinTrans/CwndTrans = 1) [1/1=1], (mylink > 0) [10.0>0] Checking for DSL/Cable Modem link (speed < 2) [0<2], (SndLimTransSender = 0) [1=0] (SendTime = 0) [3.0E-4=0], (mylink > 0) [10.0>0] Checking for half-duplex condition (rwintime > .95) [0.68>.95], (RwinTrans/sec > 30) [0.1>30], (SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [10.0<=10] Checking for congestion (cwndtime > .02) [0.31>.02], (mismatch = 0) [0=0] (MaxSsthresh > 0) [0>0] estimate = 33.01 based on packet size = 10Kbits, RTT = 318.9msec, and loss = 1.0E-6 The theoretical network limit is 33.01 Mbps The NDT server has a 8192.0 KByte buffer which limits the throughput to 200.68 Mbps Your PC/Workstation has a 375.0 KByte buffer which limits the throughput to 9.18 Mbps The network based flow control limits the throughput to 9.21 Mbps Client Data reports link is 'Ethernet', Client Acks report link is 'Ethernet' Server Data reports link is '10 Gig', Server Acks report link is 'Ethernet' VanBuren Quote Link to comment Share on other sites More sharing options...
DJVageli Posted January 2, 2005 Author CID Share Posted January 2, 2005 Ok, i knew that the information was inaccurate and kind of weird,the reason I posted it was I thought maybe it showed anything important that I didnt know about.Oh well,thanks for the replies Microwave and Vanburen Quote Link to comment Share on other sites More sharing options...
xs1 Posted January 2, 2005 CID Share Posted January 2, 2005 click START to re-test Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 360.44Kb/s running 10s inbound test (server to client) . . . . . . 2.14Mb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link always tells me this ------ Client System Details ------ OS data: Name = Windows NT, Architecture = x86, Version = 5.1 Java data: Vendor = Microsoft Corp., Version = 1.1.4 ------ Web100 Detailed Analysis ------ Cable modem/DSL/T1 link found. Link set to Half Duplex mode Information: throughput is limited by other network traffic. Good network cable(s) found Normal duplex operation found. Web100 reports the Round trip time = 136.06 msec; the Packet size = 1380 Bytes; and There were 145 packets retransmitted, 215 duplicate acks received, and 240 SACK blocks received The connection stalled 1 times due to packet loss The connection was idle 0.38 seconds (3.8%) of the time This connection is network limited 99.97% of the time. Contact your local network administrator to report a network problem Contact your local network admin and report excessive packet reordering 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: ON Information: Network Middlebox is modifying MSS variable Server IP addresses are preserved End-to-End Client IP address not found. For IE users, modify the Java parameters click Tools - Internet Options - Security - Custom Level, scroll down to Microsoft VM - Java permissions and click Custom, click Java Custom Settings Edit Permissions - Access to all Network Addresses, click Eanble and save changes Quote Link to comment Share on other sites More sharing options...
MICROWAVE Posted January 2, 2005 CID Share Posted January 2, 2005 Ok, i knew that the information was inaccurate and kind of weird,the reason I posted it was I thought maybe it showed anything important Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.