Forum Discussion

Gparker's avatar
Gparker
Network Novice
2 months ago

Routing\DNS Problems

I have weird issues getting to some sites on the internet. I also have issue using a VPN client. 

I decided to run a tracert from a command prompt and found that it takes 15 hops to get to 8.8.8.8

I've attached a screenshot. From my knowledge, it should not go to 192.0.0.1 at all, but it does 5 times. Then goes to a 10.177. . address, which shouldn't happen either.  I called T-mobile support and they didn't know what to do.

Really odd. The command I ran is: tracert 8.8.8.8.

Are there any network engineers out there?

thank you!

 

  • KBrown's avatar
    KBrown
    Newbie Caller
    2 months ago

    I see this exact same issue... even if I manually specify my own DNS servers on my computer statically, any and all trace routes have some type of network loop or something going on. It's super strange and I've actually worked in IoT/eSIM professionally in Systems Engineering / aka some DevOps and some additional side SMS/SMPP work too.

    Can someone from T-Mobile Home Internet support provide us a valid network reasoning for this and/or look into this potential SERIOUS Issue - Users need help ASAP - many don't even know it!

    • Using DNS - Note; Your text editor / forum page here doesn't allow any double colons posted together without spaces (: :) - So, there is a minor issue where I cannot post the IPv6 dns/ping/tracert results which looks slightly better than IPv4 routed traffic - as it wont allow anything with "double colons" to be submitted.
    • Using IP/IPv4 and trace routing Google's primary public DNS server...

    C:\Windows\System32>tracert 8.8.8.8

    Tracing route to dns.google 8.8.8.8
    over a maximum of 30 hops:

      1     1 ms    71 ms    <1 ms  TMO-G4SE.lan 192.168.12.1
      2     1 ms     1 ms     1 ms  192.0.0.1
      3    57 ms    33 ms    43 ms  192.0.0.1
      4    26 ms    29 ms    38 ms  192.0.0.1
      5    25 ms    39 ms    37 ms  192.0.0.1
      6     *        *        *     Request timed out.
      7     *        *        *     Request timed out.
      8     *        *        *     Request timed out.
      9     *        *        *     Request timed out.
     10    44 ms    37 ms     *     10.177.61.22
     11    90 ms    63 ms    44 ms  10.177.61.8
     12    78 ms    71 ms    78 ms  10.177.60.149
     13    62 ms    36 ms    76 ms  10.177.60.146
     14    53 ms    37 ms    76 ms  10.177.5.211
     15     *        *       53 ms  10.164.178.151
     16    84 ms    68 ms    77 ms  72.14.211.140
     17    52 ms    37 ms    76 ms  74.125.251.183
     18    71 ms    77 ms    70 ms  142.251.231.247
     19    57 ms    38 ms    78 ms  dns.google 8.8.8.8

    Trace complete.

    C:\Windows\System32>

    • And for good measure a ping with name resolution to 8.8.8.8 via IPv4

      C:\Windows\System32>ping 8.8.8.8

      Pinging 8.8.8.8 with 32 bytes of data:
      Reply from 8.8.8.8: bytes=32 time=68ms TTL=46
      Reply from 8.8.8.8: bytes=32 time=53ms TTL=46
      Reply from 8.8.8.8: bytes=32 time=77ms TTL=46
      Reply from 8.8.8.8: bytes=32 time=70ms TTL=46

      Ping statistics for 8.8.8.8:
          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
          Minimum = 53ms, Maximum = 77ms, Average = 67ms

    Thank you very much!

    Kevin Brown