Well the PPPoE issue has been resolved, wish I could say the same for the congestion issues.. The Speed test was my best out of 10 to 10 different servers in my region. The speedtest is utilizing multiple TCP streams mind you so this is both of my "3Mb/s connections". For example when I am not experiencing the congestion issues I pull just shy of 6Mb/s down/1.65 up.
Ping to gateway IP:
Pinging 10.29.15.1 with 32 bytes of data:
Reply from 10.29.15.1: bytes=32 time=282ms TTL=126
Reply from 10.29.15.1: bytes=32 time=325ms TTL=126
Reply from 10.29.15.1: bytes=32 time=470ms TTL=126
Reply from 10.29.15.1: bytes=32 time=410ms TTL=126
Reply from 10.29.15.1: bytes=32 time=309ms TTL=126
Reply from 10.29.15.1: bytes=32 time=380ms TTL=126
Reply from 10.29.15.1: bytes=32 time=359ms TTL=126
Reply from 10.29.15.1: bytes=32 time=274ms TTL=126
Reply from 10.29.15.1: bytes=32 time=374ms TTL=126
Reply from 10.29.15.1: bytes=32 time=399ms TTL=126
Reply from 10.29.15.1: bytes=32 time=497ms TTL=126
Reply from 10.29.15.1: bytes=32 time=539ms TTL=126
Reply from 10.29.15.1: bytes=32 time=372ms TTL=126
Reply from 10.29.15.1: bytes=32 time=294ms TTL=126
Reply from 10.29.15.1: bytes=32 time=353ms TTL=126
Reply from 10.29.15.1: bytes=32 time=499ms TTL=126
Reply from 10.29.15.1: bytes=32 time=185ms TTL=126
Reply from 10.29.15.1: bytes=32 time=142ms TTL=126
Reply from 10.29.15.1: bytes=32 time=340ms TTL=126
Reply from 10.29.15.1: bytes=32 time=250ms TTL=126
Reply from 10.29.15.1: bytes=32 time=500ms TTL=126
Reply from 10.29.15.1: bytes=32 time=252ms TTL=126
Reply from 10.29.15.1: bytes=32 time=375ms TTL=126
Reply from 10.29.15.1: bytes=32 time=313ms TTL=126
Reply from 10.29.15.1: bytes=32 time=97ms TTL=126
Reply from 10.29.15.1: bytes=32 time=126ms TTL=126
Reply from 10.29.15.1: bytes=32 time=299ms TTL=126
Reply from 10.29.15.1: bytes=32 time=273ms TTL=126
Reply from 10.29.15.1: bytes=32 time=255ms TTL=126
Reply from 10.29.15.1: bytes=32 time=242ms TTL=126
Reply from 10.29.15.1: bytes=32 time=363ms TTL=126
Reply from 10.29.15.1: bytes=32 time=221ms TTL=126
Reply from 10.29.15.1: bytes=32 time=379ms TTL=126
Reply from 10.29.15.1: bytes=32 time=213ms TTL=126
Reply from 10.29.15.1: bytes=32 time=254ms TTL=126
Reply from 10.29.15.1: bytes=32 time=503ms TTL=126
Reply from 10.29.15.1: bytes=32 time=223ms TTL=126
Reply from 10.29.15.1: bytes=32 time=187ms TTL=126
Reply from 10.29.15.1: bytes=32 time=315ms TTL=126
Reply from 10.29.15.1: bytes=32 time=357ms TTL=126
Ping statistics for 10.29.15.1:
Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 539ms, Average = 320ms
Pathping (50 trace routes summed together) to gateway address:
Tracing route to 10.29.15.1 over a maximum of 30 hops
0 [192.168.0.12]
1 192.168.0.254
2 10.29.15.1
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [192.168.0.12]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.254
2/ 100 = 2% |
2 295ms 2/ 100 = 2% 0/ 100 = 0% 10.29.15.1
Trace complete.
Traceroute to gateway address:
Tracing route to 10.29.15.1 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.254
2 455 ms 225 ms 217 ms 10.29.15.1
Trace complete.
Performing the same tests to the gateway of my Verizon modem produces nearly identical results.
Eric