Forum Discussion
T-Mobile Home Internet Slow IPv4
Hola all,
I’m having a terrible experience lately using the T-Mobile TM-RTL0102. More with IPv4 than IPv6
For example, when pinging bing.com on Windows
>ping bing.com -4
Pinging bing.com [204.79.197.200] with 32 bytes of data:
Reply from 204.79.197.200: bytes=32 time=333ms TTL=117
Reply from 204.79.197.200: bytes=32 time=222ms TTL=117
Reply from 204.79.197.200: bytes=32 time=227ms TTL=117
Reply from 204.79.197.200: bytes=32 time=509ms TTL=117
Ping statistics for 204.79.197.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 222ms, Maximum = 509ms, Average = 322ms
and with IPv6, not as bad:
>ping bing.com -6
Pinging bing.com [2620:1ec:c11::200] with 32 bytes of data:
Reply from 2620:1ec:c11::200: time=50ms
Reply from 2620:1ec:c11::200: time=85ms
Reply from 2620:1ec:c11::200: time=93ms
Reply from 2620:1ec:c11::200: time=72ms
Ping statistics for 2620:1ec:c11::200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 93ms, Average = 75ms
When I use my iPhone as hotspot, I get reasonable ping and have reasonable experience.
It is not just ping, it's IPv4 site. If I can't access the site with IPv6, it will use IPv4 and the experience is horrible.
This oddly started when I began to use alternate DNS 8.8.4.4, 1.1.1.1, 9.9.9.9 with my internal Asus router and/or the T-Mobile router and DNS over TLS (DoT). I’m not quite sure when but it was within the last few days and that has been my only major configuration changes.
I’m not using the 5G router as the one wasn’t able to work in my area due to it trying to use multiple towers that were further away than closes causing worse experience than closest one.
I did contact T-Mobile twice today and after a power off and back on, it improved a bit but was not as good as a week ago.
Any advice appreciated to get this working like a good ISP should be.
Gracias,
Jason
Let everything ultimately use their DNS as primary... it is served via their v6 network to the Askey, which will forward the results over it's local v4 LAN or V6 segment (you can do v6 passthrough via a personal router if you are using one... not the greatest, but it kinda sorta works). If you poke around the GUI you will see it reference the v6 gateway and DNS in play upstream from the Askey. May have to be in Expert view to see it... forget the details.
Queries to an external v4 DNS will have to go through their funky 464xlat/CGN tunnel crud to get there and back. Think of it like using a firewalled VPN for the queries, versus a more direct query.
Depending on your local setup, it could get a bit funky.
Note that with the Askey, you can change the private address space if you want, so if you are doing a double-nat set up (personal router in NAT mode not as an access point), you can set them up with more unique IP ranges.
The Askey forwards it over it's v4 private LAN subnet, and if you are using your own router in native mode, that will have to forward again to it's private LAN subnet. This will inject a little extra lag, but should be considerably less than what you are getting trying to force google/cloudflare/others as the primary DNS. For the clients you configure manually, would want to point to the router(s) first, then any external provider you want to hit. Por ejemplo:
10.10.x.x (personal router in NAT mode)
192.168.x.x (TMO Askey)
(Put the local gateway with better response time first, then you can list external providers as you see fit)
8.8.8.8
1.1.1.1
Forget where I got referred to it, may have been speedguide.net. But there is a DNS Benchmark tool you can download for free that you can use to test responsiveness of your DNS setup. May want to Google for it, just make sure it is coming coming from reputable source and all.
EDIT: found it…
https://www.grc.com/dns/benchmark.htm
Hoping they start shipping the new 5g hardware soon so we can get a feel for how they hold up. The bands have been available in our market for quite a while now... but we are all still on the Askey LTE boxes.
