Jump to content

RaulJimenez

Members
  • Posts

    110
  • Joined

  • Last visited

  • Speed Test

    My Results

Posts posted by RaulJimenez

  1. Guaynabo :

    ping -n 23 www.google.com

    Pinging www.l.google.com [64.233.161.104] with 32 bytes of data:

    Reply from 64.233.161.104: bytes=32 time=59ms TTL=244

    Reply from 64.233.161.104: bytes=32 time=63ms TTL=244

    Reply from 64.233.161.104: bytes=32 time=62ms TTL=243

    Reply from 64.233.161.104: bytes=32 time=59ms TTL=243

    Request timed out.

    Reply from 64.233.161.104: bytes=32 time=57ms TTL=244

    Request timed out.

    Reply from 64.233.161.104: bytes=32 time=59ms TTL=244

    Reply from 64.233.161.104: bytes=32 time=57ms TTL=243

    Reply from 64.233.161.104: bytes=32 time=59ms TTL=243

    Reply from 64.233.161.104: bytes=32 time=65ms TTL=244

    Reply from 64.233.161.104: bytes=32 time=64ms TTL=244

    Reply from 64.233.161.104: bytes=32 time=56ms TTL=243

    Reply from 64.233.161.104: bytes=32 time=57ms TTL=243

    Reply from 64.233.161.104: bytes=32 time=61ms TTL=244

    Reply from 64.233.161.104: bytes=32 time=59ms TTL=244

    Reply from 64.233.161.104: bytes=32 time=60ms TTL=243

    Reply from 64.233.161.104: bytes=32 time=56ms TTL=243

    Reply from 64.233.161.104: bytes=32 time=58ms TTL=244

    Reply from 64.233.161.104: bytes=32 time=58ms TTL=244

    Reply from 64.233.161.104: bytes=32 time=59ms TTL=243

    Reply from 64.233.161.104: bytes=32 time=60ms TTL=243

    Reply from 64.233.161.104: bytes=32 time=70ms TTL=243

    Ping statistics for 64.233.161.104:

        Packets: Sent = 23, Received = 21, Lost = 2 (8% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 56ms, Maximum = 70ms, Average = 59ms

  2. not even 50 cents per customer. so a complaint costs them 50 cents a customer? they dick with the speeds and save transmission fees.

    as for being conformist, no, i'm not. i have simply given up the hope for anything in PR to change for the better. am currently waiting to see if the newest financial misstep by the administration manages to drop puerto rico's credit rating to junk bond status. then the statement from the administration that things are being done to deal with this minor setback. mwahahahaha

    Bro you must be some real bad ass Estadist freak :)

  3. resolparabot : maybe you know what the fuck this is, when im downloading something say the speed is at 217kbps and the thing is downloading and then all of sudden the lights of the modem stop blinking on the receiving end and after a couple seconds it resumes downloading, it keeps doing that over and over till the file is downloaded. Is that due to packet loss??

  4. trogers and company , I'm trying to optimize my connection as possible but I dont where where exactly to start using this tweak technique, most of the time i try a tweak it gets slower. here are my tests

    thanks a lot.

    WEB100 Kernel Variables:

    Client: localhost/127.0.0.1

    AckPktsIn: 914

    AckPktsOut: 0

    BytesRetrans: 32120

    CongAvoid: 279

    CongestionOverCount: 0

    CongestionSignals: 2

    CountRTT: 865

    CurCwnd: 48180

    CurMSS: 1460

    CurRTO: 340

    CurRwinRcvd: 65535

    CurRwinSent: 16304

    CurSsthresh: 32120

    DSACKDups: 0

    DataBytesIn: 0

    DataBytesOut: 3579920

    DataPktsIn: 0

    DataPktsOut: 2452

    DupAcksIn: 40

    ECNEnabled: 0

    FastRetran: 1

    MaxCwnd: 65700

    MaxMSS: 1460

    MaxRTO: 370

    MaxRTT: 220

    MaxRwinRcvd: 65535

    MaxRwinSent: 16304

    MaxSsthresh: 32120

    MinMSS: 1460

    MinRTO: 300

    MinRTT: 100

    MinRwinRcvd: 46555

    MinRwinSent: 16304

    NagleEnabled: 1

    OtherReductions: 2

    PktsIn: 914

    PktsOut: 2452

    PktsRetrans: 22

    X_Rcvbuf: 103424

    RcvWinScale: 2147483647

    SACKEnabled: 0

    SACKsRcvd: 0

    SendStall: 0

    SlowStart: 71

    SampleRTT: 110

    SmoothedRTT: 110

    X_Sndbuf: 103424

    SndWinScale: 2147483647

    SndLimTimeRwin: 5380386

    SndLimTimeCwnd: 4636706

    SndLimTimeSender: 2605

    SndLimTransRwin: 1

    SndLimTransCwnd: 2

    SndLimTransSender: 1

    SndLimBytesRwin: 2207520

    SndLimBytesCwnd: 1372400

    SndLimBytesSender: 0

    SubsequentTimeouts: 0

    SumRTT: 100910

    Timeouts: 1

    TimestampsEnabled: 0

    WinScaleRcvd: 2147483647

    WinScaleSent: 2147483647

    DupAcksOut: 0

    StartTimeUsec: 44530

    Duration: 10023877

    c2sData: 2

    c2sAck: 2

    s2cData: 9

    s2cAck: 3

    half_duplex: 0

    link: 100

    congestion: 0

    bad_cable: 0

    mismatch: 0

    spd: 0.00

    bw: 3.34

    loss: 0.000815661

    avgrtt: 116.66

    waitsec: 0.34

    timesec: 10.00

    order: 0.0438

    rwintime: 0.5370

    sendtime: 0.0003

    cwndtime: 0.4628

    rwin: 0.5000

    swin: 0.7891

    cwin: 0.5013

    rttsec: 0.116659

    Sndbuf: 103424

    aspd: 9.80657

    Checking for mismatch on uplink

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

    (rwintime > .9) [0.53>.9], (loss < .01) [8.15<.01]

    Checking for excessive errors condition

    (loss/sec > .15) [8.15>.15], (cwndtime > .6) [0.46>.6],

    (loss < .01) [8.15<.01], (MaxSsthresh > 0) [32120>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) [8.15<.01], (mylink > 0) [3.0>0]

    Checking for Wireless link

    (sendtime = 0) [3.0E=0], (speed < 5) [0<5]

    (Estimate > 50 [3.34>50], (Rwintime > 90) [0.53>.90]

    (RwinTrans/CwndTrans = 1) [1/2=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.53>.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.46>.02], (mismatch = 0) [0=0]

    (MaxSsthresh > 0) [32120>0]

    estimate = 3.34 based on packet size = 11Kbits, RTT = 116.66msec, and loss = 8.15661E-4

    The theoretical network limit is 3.34 Mbps

    The NDT server has a 101.0 KByte buffer which limits the throughput to 6.76 Mbps

    Your PC/Workstation has a 63.0 KByte buffer which limits the throughput to 4.28 Mbps

    The network based flow control limits the throughput to 4.29 Mbps

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

    Server Data reports link is '10 Gig', Server Acks report link is 'Ethernet'

    =====================================================

    TCP options string = 020405b4

    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) = 65535

    RWIN Scaling (RFC1323) = 0 bits

    Unscaled TCP Receive Window = 65535

    Note: TCP 1323 Options need to be enabled for RWIN over 2^16 (65535). Windows 9x might also need the MS Vtcp386 fix.

    For optimum performance, consider changing RWIN to a multiple of MSS.

    Other RWIN values 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 (Note this is not a speed test):

    Your TCP Window limits you to: 2621.4 Kbps (327.675 KBytes/s) @ 200ms

    Your TCP Window limits you to: 1048.56 Kbps (131.07 KBytes/s) @ 500ms

    MTU Discovery (RFC1191) = ON

    Time to live left = 119 hops

    TTL value is ok.

    Timestamps (RFC1323) = OFF

    Selective Acknowledgements (RFC2018) = OFF

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

    ==================================================

    :::.. Download Stats ..:::

    Connection is:: 3281 Kbps about 3.3 Mbps (tested with 2992 kB)

    Download Speed is:: 401 kB/s

    Tested From:: https://testmy.net

    Test Time:: Wed Feb 15 2006 16:32:12 GMT-0500 (Eastern Standard Time)

    Bottom Line:: 59X faster than 56K 1MB download in 2.55 sec

    Diagnosis: Awesome! 20% + : 51.27 % faster than the average for host (onelinkpr.net)

    Validation Link:: https://testmy.net/stats/id-3ZBGCEVML

  5. Ok I check the info on the splitter that is on the modem side (2nd splitter). The splitter is 1-120dbv and then saying 6 dbv. also 1-5000 MHz. The name is (I think) MCR-DCR (something like that). This is a 3 way splitter. In, Out and Tap. The cable modem is connected with Out, while TV with Tap. The In is getting cable from the 1st splitter (I have to open some box in my wall to get that splitter detail (too lazy after office to do that.....will do in the weekend). Hope this info is enough for you to help me out.

    After seeing the way Onelink Tech is working.....I am right now not comfortable calling them to do anything here....

    Yes I think we are almost there, first thing I want you to do is change the cable modem from the OUT to the TAP and put the TV's in the OUT portion and then post here the numbers again.

  6. Downstream Value 

    Frequency 573000000 Hz

    Signal To Noise Ratio 38.2 dB

    Power Level 10.6 dBmV

    The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading

    Upstream Value

    Channel ID 3

    Frequency 33000000 Hz

    Power 40.7 dBmV

    9.07 PM

    those levels are good. They could be better but it won't affect speed in any way . The only thing that I would do in your case is ask onelink to provide you with a DC COUPLER TAP with an insertion loss of 6db. that would put you around +4 or less and 46+ upstream.

  7. Yes.....I took the cable with 2 room installation (free offer). From outside the cable comes into my living room (that was the only possibility in my apartment from outside cable box to inside my apartment). There is a spliter over here which takes one end to my bedroom and the other to my penthouse room. Here is where my Xbox is, so I told Adelphia tech to install cable modem there. So they again put a spliter there and have 1 end to my modem and another to TV. Now I have wireless router connected to modem & Xbox, my computer connects with router.

    The funny thing is when they install Powerlink (Nov 26, 2005), everything was looking good. Even the speeds were good. But now....maybe thats why these days my LIVE sessions are so screwed up.  What can I do to get a good upstream level then.

    Also, why downstream is in negative...can u expain a bit abt that...maybe I need something positive...to get a good download speed....

    Also what are these log file entries....I always leave my modem and router on....should I keep my modem in standby to stop onelink from messing with my modem.

    Yes , actually your downstream levels do not bother me at all, downstream levels need to be -15 to +15 for the modem to receive the signal from the CMTS ( that is onelink signal) now what you are striving for is basically getting as close as possible to 0dbMv. Lets do this analogy ... comparing signals to light... too BRIGHT a signal meaning +15  up and it will be very difficult for the modem to see and too low -15 down and it wont see anything at all. since you are at -4dbmV is not a concern because is actually getting close to 0dbMv.

    Now here comes my concern, upstream levels need to be in the +35 up to 55+ at maximum. This is the signal your modem transmit to the cable end (onelink) . So basically you have signal coming to you (DOWNSTREAM) and signal going to them (UPSTREAM).

    Here is the best configuration for 2 tv's and cable modem :

    You should have a 3 way splitter here. Put the modem on the 3.5db leg of the splitter, and the TVs on the 7db legs. you will see how much signal you lose on each leg by looking at the splitter. If you can give me a bit of more info on the splitters you have i'll gladly help you out.

    Remember cable loses signal over distance. And I think your best setup is running the cable modem straight from the first split instead. First let me know what kind of splitters yo have and then i'll help you out.

    If after this your upstream levels are not good you definitely need to call Onelink( OUCH! ) for them to fix their upstream/downstream level at their cable box that supplies to your house.

×
×
  • Create New...