Jump to content
Sign in to follow this  
scumbucketsex

hi im new here, sorry to bother you all but is this right?

Recommended Posts

I am out of idea. But I still suspect someone may be tapping your line. If you are staying in a hostel or apartment, this can be a possibility. Maybe you can do a visual check of the telephone wiring from the mains and up to your room.

If I have any new ideas I will message you.

Share this post


Link to post
Share on other sites

If your latency goes to normal (meaning not more than 300 ms), you need to use my original ccs file. The last adjustment is to compensate for the high latency.

You can try pinging your ISP 4-5 times and note if there are wide fluctuations in latency. A single test may not be indicative..

Share this post


Link to post
Share on other sites

this is what i am getting now, can you tell me if any better:

TCP options string = 020405b40103030101010402

MTU = 1500

MTU is fully optimized for broadband.

MSS = 1460

Maximum useful data in each packet = 1460, which equals MSS.

Default TCP Receive Window (RWIN) = 128480

RWIN Scaling (RFC1323) = 1 bits (scale factor of 2)

Unscaled TCP Receive Window = 64240

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)

64240 (MSS x 44) 

bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 5139.2 kbps (642.4 KBytes/s) @ 200ms

Your TCP Window limits you to: 2055.68 kbps (256.96 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 58 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349) = 00000000 (0)

Share this post


Link to post
Share on other sites

click START to re-test

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 290.38Kb/s

running 10s inbound test (server to client) . . . . . . 439.06kb/s

Your PC is connected to a Cable/DSL modem

Information: Other network traffic is congesting the link

click START to re-test

Share this post


Link to post
Share on other sites

WEB100 Enabled Statistics:

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 290.38Kb/s

running 10s inbound test (server to client) . . . . . . 439.06kb/s

------  Client System Details  ------

OS data: Name = Windows XP, Architecture = x86, Version = 5.1

Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_04

------  Web100 Detailed Analysis  ------

Cable modem/DSL/T1 link found.

Link set to Full 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 = 326.11 msec; the Packet size = 1460 Bytes; and

No packet loss - but packets arrived out-of-order 7.91% of the time

This connection is network limited 99.97% 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

Packet size is preserved End-to-End

Server IP addresses are preserved End-to-End

Client IP addresses are preserved End-to-End

Share this post


Link to post
Share on other sites

WEB100 Kernel Variables:

Client: localhost/127.0.0.1

AckPktsIn: 215

AckPktsOut: 0

BytesRetrans: 0

CongAvoid: 187

CongestionOverCount: 0

CongestionSignals: 0

CountRTT: 198

CurCwnd: 27740

CurMSS: 1460

CurRTO: 690

CurRwinRcvd: 128480

CurRwinSent: 16304

CurSsthresh: 2920

DSACKDups: 0

DataBytesIn: 0

DataBytesOut: 567940

DataPktsIn: 0

DataPktsOut: 389

DupAcksIn: 17

ECNEnabled: 0

FastRetran: 0

MaxCwnd: 27740

MaxMSS: 1460

MaxRTO: 710

MaxRTT: 490

MaxRwinRcvd: 128480

MaxRwinSent: 16304

MaxSsthresh: 2920

MinMSS: 1460

MinRTO: 430

MinRTT: 180

MinRwinRcvd: 64240

MinRwinSent: 16304

NagleEnabled: 1

OtherReductions: 0

PktsIn: 215

PktsOut: 389

PktsRetrans: 0

X_Rcvbuf: 103424

RcvWinScale: 7

SACKEnabled: 3

SACKsRcvd: 27

SendStall: 0

SlowStart: 1

SampleRTT: 470

SmoothedRTT: 460

X_Sndbuf: 103424

SndWinScale: 1

SndLimTimeRwin: 0

SndLimTimeCwnd: 10138500

SndLimTimeSender: 2595

SndLimTransRwin: 0

SndLimTransCwnd: 1

SndLimTransSender: 1

SndLimBytesRwin: 0

SndLimBytesCwnd: 567940

SndLimBytesSender: 0

SubsequentTimeouts: 0

SumRTT: 64570

Timeouts: 0

TimestampsEnabled: 0

WinScaleRcvd: 1

WinScaleSent: 7

DupAcksOut: 0

StartTimeUsec: 586948

Duration: 10143852

c2sData: 2

c2sAck: 2

s2cData: 2

s2cAck: 2

half_duplex: 0

link: 100

congestion: 1

bad_cable: 0

mismatch: 0

spd: 0.00

bw: 34.16

loss: 0.000001000

avgrtt: 326.11

waitsec: 0.00

timesec: 10.00

order: 0.0791

rwintime: 0.0000

sendtime: 0.0003

cwndtime: 0.9997

rwin: 0.9802

swin: 64.0000

cwin: 0.2116

rttsec: 0.326111

Sndbuf: 8388608

aspd: 2.06005

Checking for mismatch on uplink

(speed > 50 [0>50], (xmitspeed < 5) [0.29<5]

(rwintime > .9) [0>.9], (loss < .01) [1.0E<.01]

Checking for excessive errors condition

(loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.99>.6],

(loss < .01) [1.0E<.01], (MaxSsthresh > 0) [2920>0]

Checking for 10 Mbps link

(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]

(xmitspeed < 9.5) [0.29<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 [34.16>50], (Rwintime > 90) [0>.90]

(RwinTrans/CwndTrans = 1) [0/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>.95], (RwinTrans/sec > 30) [0>30],

(SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]

Checking for congestion

(cwndtime > .02) [0.99>.02], (mismatch = 0) [0=0]

(MaxSsthresh > 0) [2920>0]

estimate = 34.16 based on packet size = 11Kbits, RTT = 326.11msec, and loss = 1.0E-6

The theoretical network limit is 34.16 Mbps

The NDT server has a 8192.0 KByte buffer which limits the throughput to 196.25 Mbps

Your PC/Workstation has a 125.0 KByte buffer which limits the throughput to 3.00 Mbps

The network based flow control limits the throughput to 0.64 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'

Server Data reports link is 'T1', Server Acks report link is 'T1'

Share this post


Link to post
Share on other sites

Web100 reports the Round trip time = 326.11 msec; the Packet size = 1460 Bytes; and

No packet loss - but packets arrived out-of-order 7.91% of the time

This connection is network limited 99.97% of the time.

Your PC/Workstation has a 125.0 KByte buffer which limits the throughput to 3.00 Mbps

The network based flow control limits the throughput to 0.64 Mbps

Your latency is now 326 ms. First it was about 500 ms. Then 600 ms and now 300+ ms. These are wide fluctuations.

Share this post


Link to post
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...