Interpreting the network Trace route cmd

Thread Starter

KeepItSimpleStupid

Joined Mar 4, 2014
4,019
Traceroute Check for: '*.*.*.*' *redacted

traceroute to my public IP (redacted), 10 hops max, 60 byte packets
1 45.79.12.202 (45.79.12.202) 1.024 ms 45.79.12.201 (45.79.12.201) 0.986 ms 45.79.12.202 (45.79.12.202) 0.971 ms
2 45.79.12.0 (45.79.12.0) 0.942 ms 45.79.12.6 (45.79.12.6) 0.341 ms 45.79.12.0 (45.79.12.0) 0.927 ms
3 ae-37.a01.dllstx04.us.bb.gin.ntt.net (192.80.16.21) 3.026 ms ae8-21.cr6-dal3.ip4.gtt.net (173.205.38.101) 0.915 ms ae-37.a01.dllstx04.us.bb.gin.ntt.net (192.80.16.21) 3.012 ms
4 ae-9.r11.dllstx09.us.bb.gin.ntt.net (129.250.2.165) 1.525 ms et-0-0-67.cr11-dal3.ip4.gtt.net (89.149.139.205) 0.882 ms ae-9.r10.dllstx09.us.bb.gin.ntt.net (129.250.4.177) 1.464 ms
5 ae-1.a01.dllstx09.us.bb.gin.ntt.net (129.250.3.30) 1.444 ms 0.ae16.BR1.DFW13.ALTER.NET (204.255.168.65) 1.417 ms ae-1.a01.dllstx09.us.bb.gin.ntt.net (129.250.3.30) 1.420 ms
6 0.ae12.BR2.DFW13.ALTER.NET (204.255.168.157) 1.565 ms 5.023 ms 1.055 ms
7 Bundle-Ether1100.PHLAPA-LCR-21.verizon-gni.NET (140.222.231.25) 38.284 ms G4-1.PHLAPA-PHLAPAMK-ERXG18.verizon-gni.net (130.81.197.247) 40.657 ms Bundle-Ether1000.PHLAPA-LCR-22.verizon-gni.NET (140.222.231.27) 35.619 ms
8 G2-1.PHLAPA-PHLAPAMK-ERXG18.verizon-gni.net (130.81.197.245) 41.173 ms pool-108-16-181-100.phlapa.east.verizon.net (108.16.181.100) 60.781 ms G1-0.PHLAPA-PHLAPAMK-ERXG18.verizon-gni.net (*.*.*.*) 41.739 ms (IP address redacted)

The above is a reverse traceroute to my public IP address. The actual puplic IP address has been redacted.

Correct me if I'm wrong. It takes 3.012 ms round trip to get from 45.79.12.0 to 192.80.16.21?

It takes the sum of all the hops to get to my public IP address? The one with 60.781 ms.

Notice that as soon as the packet hits Verizon, everything goes to crap. 35.6+41.1+41.7

i think this is unacceptable.


This
PING my public IP from my computer 56(84) bytes of data.
64 bytes from my network to my public IP: icmp_req=1 ttl=64 time=32.1 ms
64 bytes frommy network to my public IP: icmp_req=2 ttl=64 time=30.8 ms
64 bytes from my network to my public IP: icmp_req=3 ttl=64 time=28.8 ms
is a ping from my network to my public IP.

usually this time is <1ms.

I'm having all sorts of issues like a name server response isn;t fast enough. gmail complains that something is wrong. one drive has a hard time connecting.

An NDT speed test gets: 1.07 Mbps down and and 660 kpbs up. I used to have a solid 2.8 and 680K with a 3 Mbps provision.

It also gets:
Network latency: 388 msec round trip time


Jitter: 656 msec


and

Your system: -
Plugin version: - (-)
TCP receive window: 208896 current, 208896 maximum
0.19 % of packets lost during test
Round trip time: 57 msec (minimum), 713 msec (maximum), 388 msec (average)
Jitter: -
0.00 seconds spend waiting following a timeout
TCP time-out counter: 466
154 selective acknowledgement packets received

No duplex mismatch condition was detected.The test did not detect a cable fault.No network congestion was detected.
0.9381 % of the time was not spent in a receiver limited or sender limited state.
0.0039 % of the time the connection is limited by the client machine's receive buffer.
Optimal receive buffer: - bytes
Bottleneck link: -
129 duplicate ACKs set



Lnk speed is about 5.8k and I'm supposedly 8800 ft form the central office. I don't know line attenuation nor if I'm connected to ADSL, ADSL2 or ADSL2+.

verizon support just wants to send out a tech and there isn't much he can do. The resuts are time of day dependent.

Does this mean that the time to reach my IP address

I need confirmation that Verizon sucks and how I might go about getting it fixed?

This is a wireless link, but on a direct wired link I've seen jitter at 1.5 SECONDS.

I have a Actiontec GT784 modem which has the following commands

Usage: adslctl start [--up] [--mod <a|d|l|t|2|p|e|m|M3|M5>] [--lpair <(i)nner|(o)uter>]
[--trellis <on|off>] [--snr <snrQ4>] [--bitswap <on|off>] [--sesdrop <on|off>]
[--sra <on|off>] [--CoMinMgn <on|off>] [--i24k <on|off>] [--phyReXmt <0xBitMap-UsDs>]
[--Ginp <0xBitMap-UsDs>] [--TpsTc <0xBitMap-AvPvAaPa>] [--monitorTone <on|off>]
[--forceJ43 <on|off>] [--toggleJ43B43 <on|off>]
adslctl stop
adslctl connection [--up] [--down] [--loopback] [--reverb]
[--medley] [--noretrain] [--L3] [--diagmode] [--L0]
[--tones] [--normal] [--freezeReverb] [--freezeMedley]
adslctl configure [--mod <a|d|l|t|2|p|e|m|M3|M5>] [--lpair <(i)nner|(o)uter>]
[--trellis <on|off>] [--snr <snrQ4>] [--bitswap <on|off>] [--sesdrop <on|off>]
[--sra <on|off>] [--CoMinMgn <on|off>] [--i24k <on|off>] [--phyReXmt <0xBitMap-UsDs>]
[--Ginp <0xBitMap-UsDs>] [--TpsTc <0xBitMap-AvPvAaPa>] [--monitorTone <on|off>]
[--forceJ43 <on|off>] [--toggleJ43B43 <on|off>]
adslctl bert [--start <#seconds>] [--stop] [--show]
adslctl afelb [--time <sec>] [--tones] [--signal <1/2/8>]
adslctl qlnmntr [--time <sec>] [--freq <msec>]
adslctl inm [--start <BB_THRESH 10*dB> <INMIATO> <INMIATS>] [--stop] [--show]
adslctl snrclamp [--shape <shapeId>] [--bpshape [bpIndex-bpLevel,]]
adslctl nlnm [--show ] [--setThld <Thld_Num_Tones>]
adslctl diag [--logstart <nBytes>] [--logpause] [--logstop] [--loguntilbufferfull <nBytes>]
[--loguntilretrain <nBytes>]
adslctl info [--state] [--show] [--stats] [--SNR] [--QLN] [--Hlog] [--Hlin] [--HlinS] [--Bits]
[--linediag] [--reset] [--vendor] [--cfg]
adslctl profile [--show] [--save] [--restore]
adslctl --version
adslctl –help

I haven;t played with them while online because I mostly run in Bridge mode.
 

eetech00

Joined Jun 8, 2013
1,869
Traceroute Check for: '*.*.*.*' *redacted
The above is a reverse traceroute to my public IP address. The actual puplic IP address has been redacted.
What do you mean "reverse" traceroute?
Correct me if I'm wrong. It takes 3.012 ms round trip to get from 45.79.12.0 to 192.80.16.21?
No. The numbers are relative to the origin of the device that initiated the trace route.
It takes the sum of all the hops to get to my public IP address? The one with 60.781 ms.
No. the hop delays are not cumulative. They are relative to the origin of the device that initiated the trace route.

eT
 
Top