dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
23
share rss forum feed


FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS

1 edit
reply to houkouonchi

Re: Anyone having problems in the Riverside County area?

ONT -> Ethernet -> Netgear WNDR3700 Router
The actiontec is after the netgear only to feed data to the STBs.

It's been setup this way for ~2years now with no issues. If you go to SpeedTest.net and run a test to the Irvine (Hosted by GoFiber) server does it work for you? I just get an error.

Netflix bugs out after a few minutes and start buffering on and off even at low quality. Anything sensitive to streaming seems to give me issues.

Ping seems to be off as well, I used to get sub 10ms ping times to nearby servers.

Some speed tests:

SpeedTest.net (DreamHost - LA)




SpeedTest.net (Gofiber - Irvine)
Fails to load

SpeedTest.net (Internode - LA)



SpeedTest.net (Charter - Monterey Park)



SpeedTest.net (Atlantic Metro - Los Angeles)






PingTest






Verizon's speed test gives me the following:

SendBufferSize set to [65536]
running 10s outbound test (client to server) . . . . . 32.57Mb/s
running 10s inbound test (server to client) . . . . . . 23.45Mb/s

------ Client System Details ------
OS data: Name = Windows 8, Architecture = x86, Version = 6.2
Java data: Vendor = Oracle Corporation, Version = 1.7.0_09

------ Web100 Detailed Analysis ------
Client Receive Window detected at 157440 bytes.
45 Mbps T3/DS3 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 = 13.17 msec; the Packet size = 1460 Bytes; and
There were 465 packets retransmitted, 1880 duplicate acks received, and 2325 SACK blocks received
The connection stalled 1 times due to packet loss
The connection was idle 0.21 seconds (1.90%) of the time
This connection is receiver limited 3.37% of the time.
This connection is sender limited 64.99% of the time.
This connection is network limited 31.64% 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


houkouonchi

join:2002-07-22
Ontario, CA
Reviews:
·Verizon FiOS

said by FutureX2001:

------ Web100 Detailed Analysis ------
Client Receive Window detected at 157440 bytes.
45 Mbps T3/DS3 link found.
Link set to Half Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Your receive window is super small at only 150 kilobytes. Mine is 3 megabytes (my upload results are super low cause i am doing a lot of uploading while i did the speedtest:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [8192]
running 10s outbound test (client to server) . . . . . 11.05Mb/s
running 10s inbound test (server to client) . . . . . . 149.73Mb/s
 
------ Client System Details ------
OS data: Name = Linux, Architecture = amd64, Version = 2.6.39.4-web10g
Java data: Vendor = Oracle Corporation, Version = 1.7.0_09
 
------ Web100 Detailed Analysis ------
Client Receive Window detected at 3145728 bytes.
100 Mbps FastEthernet link found.
Link set to Half Duplex mode
No network congestion discovered.
Good network cable(s) found
Alarm: Duplex mismatch condition found: Host set to Full and Switch set to Half duplexD
 

I think something is messed up with the irvine test server as it hung for a very long time and then gave me super low results:



Your latency seemed oddly high to me though. Sometimes speedtest.net is not very accurate for that though. Can you show me a traceroute to 208.97.141.21 (that is the DH speedtest.net server that you got 19ms to). I usually get 3-8ms to it. Probably would if i was not uploading a ton ATM:


--
300/150 mbit Bonded Verizon FiOS connection FTW!


FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS

I'm going to have to keep an eye on it over the next few days, today's test seemed fine:



Pinging 208.97.141.21 with 32 bytes of data:
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=7ms TTL=252
Reply from 208.97.141.21: bytes=32 time=13ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252
Reply from 208.97.141.21: bytes=32 time=16ms TTL=252
Reply from 208.97.141.21: bytes=32 time=12ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252
Reply from 208.97.141.21: bytes=32 time=42ms TTL=252
Reply from 208.97.141.21: bytes=32 time=16ms TTL=252
Reply from 208.97.141.21: bytes=32 time=18ms TTL=252
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=14ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=20ms TTL=252
Reply from 208.97.141.21: bytes=32 time=12ms TTL=252
Reply from 208.97.141.21: bytes=32 time=11ms TTL=252
Reply from 208.97.141.21: bytes=32 time=21ms TTL=252
Reply from 208.97.141.21: bytes=32 time=16ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252
Reply from 208.97.141.21: bytes=32 time=12ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252

Ping statistics for 208.97.141.21:
Packets: Sent = 47, Received = 47, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 42ms, Average = 12ms



FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS
reply to houkouonchi

I ran the verizon speed test again... didn't change anything on the computer:

SendBufferSize set to [65536]
running 10s outbound test (client to server) . . . . . 32.44Mb/s
running 10s inbound test (server to client) . . . . . . 57.97Mb/s

------ Client System Details ------
OS data: Name = Windows 8, Architecture = x86, Version = 6.2
Java data: Vendor = Oracle Corporation, Version = 1.7.0_09

------ Web100 Detailed Analysis ------
Client Receive Window detected at 281600 bytes.
45 Mbps T3/DS3 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 = 12.25 msec; the Packet size = 1460 Bytes; and
There were 307 packets retransmitted, 2727 duplicate acks received, and 3035 SACK blocks received
The connection stalled 1 times due to packet loss
The connection was idle 0.21 seconds (2.09%) of the time
This connection is receiver limited 5.17% of the time.
This connection is sender limited 76.47% of the time.
This connection is network limited 18.36% 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
Information: Network Address Translation (NAT) box is modifying the Client's IP address



FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS

Just an update, the problem went away for 3 weeks until tonight:




Verizon
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [65536]
running 10s outbound test (client to server) . . . . . 34.32Mb/s
running 10s inbound test (server to client) . . . . . . 2.94Mb/s
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