Question

Has ping / tracert been blocked on 5g network?

  • 18 October 2022
  • 79 replies
  • 3966 views


Show first post

79 replies

Userlevel 7
Badge +8

Testing with a Garuda Linux client with a verbose ping to 8.8.8.8 currently it runs with roughly 100 ms latency but out of 43 packets sent 13 received responses so roughly 70% packet loss. Running a speedtest I am still obtaining 275-300 down and meh… 21 mbps upload so the bandwidth is there but the ICMP traffic is impaired or throttled. I sort of suspect it has something to do with throttling for one reason or another. I suppose it may be related to changes with the CGNAT solution but probably a throttling of the traffic. Testing with a MacBook Pro via a thunderbolt to ethernet adapter the response times are worse than with either of the Linux clients I have used but still bad either way. 

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets

1  www.webgui.nokiawifi.com (192.168.12.1)  2.145 ms  0.376 ms  0.279 ms

2  192.0.0.1 (192.0.0.1)  0.533 ms  0.698 ms  0.449 ms

3  * 192.0.0.1 (192.0.0.1)  27.721 ms  29.890 ms

4  * * 192.0.0.1 (192.0.0.1)  35.968 ms

5  192.0.0.1 (192.0.0.1)  30.243 ms *  46.172 ms

6  * * *

7  * * *

8  * * *

9  * * *

10  10.164.162.176 (10.164.162.176)  509.603 ms * *

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  *^C

Pretty clear it is useless without using a VPN.

I noticed about 4 days ago that most pings now fail.  If I do a continuous ping(-t) roughly 1 in 20 gets a response, and all are over 100 ms.  Using pinginfoview, I can set the port it uses, and they work.

 

TMobile needs to fix this.  Lots of people use ping to check connectivity, and it’s just going to make them look bad.

Same here in Littlerock AR.  I am a Citrix Admin (Working remote 100% of the time); I always have the end user ping our NetScaler gateway to see that the response time is when they say their remote session is sluggish.

Now even I cannot get a reliable ping response, but I am still able to work remotely.

Seems like ICMP has been throttled.

Not good.

Might have to go back to SuddenLink.

Cannot use this connection if I cannot even ping a remote site.

On the bright side, a new ISP is coming to my area with fiber, still under construction but fingers crossed they are better than SuddenLink and Century Link

 

Example:

Pinging google.com [142.250.72.46] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 142.250.72.46: bytes=32 time=117ms TTL=110
Request timed out.
Request timed out.
Request timed out.

 

With all the Request time outs, my Internet is fine.

 

If I RDP into a computer at work and ping a remote site, I get great ping responses.

 

Userlevel 7
Badge +8

I am in east TN with the Nokia gateway and I ran a quick test with a Macbook Pro and a Linux client. With the Macbook Pro the pings have a significant delay where several request time out messages were reported prior to an actual response typically 140+ ms between responses. I went to a Linux client and did a forced ipv6 ping based upon a prior test. I get a similar response performing IPv6 and IPv4. Both have extreme delay times and are not very useful Of the forced 23 ipv6 ping packets 5 were received with a ~78% loss. So, yes it appears T-Mobile has jacked up the use of ICMP as a trouble shooting tool. 

Based upon the two tests I ran it appears pings with IPv4 fail much worse than IPv6 pings but the use of pings now is pretty much useless.

I fail to see why they feel this would be positive for users. Make it more difficult for users to identify potential issues so they are totally blind. It just makes calls to TMO support less productive when users with such basic knowledge cannot tell support what they do not see. 

Reply