Newbie to TMHI...so what are we supposed to do with IPV4 devices?
I just set up my TMHI "router" (yes, in airquotes), and am very happy with the speed, but I'm not happy that a couple of my devices won't connect to it at all. Neither my 2021 wired Ring Doorbell, nor my Sense Labs home entergy monitor will connect to the router. I switched the mode from Automatic to 2.4GHz, but no luck. I'm guessing it is related to the router only handling IPV6. As soon as I switched the devices back to use my old router (an actual real router...Linksys EA7500), both devices reconnected with no issues. I'm thinking of connecting my EA7500 to the TMHI router, and just continue to use it as I did when it wasconnected to my Spectrum cable modem. Any thoughts on how this will work for me, and what the disadvantages may be to doing so? Does anyone have an alternate solution to accomplish getting these devices to connect to the TMHI "router"? Thanks, Bill
Unstable Hotspot and MMS Issue
Hi All. I am having a strange and annoying issue. I have an unlocked Samsung S21. When I use the APN provided by T-Mobile, I have a very unstable phone hotspot. I turn on the hotspot; sometimes it connects, sometimes it doesn't. If it connects, it disconnects quickly. I have to turn on and off airplane mode multiple times to get it to work. I found a work around by creating a new APN for the phone. I changed the APN Protocol to IPv4/IPv6 and the APN roaming protocal: to IPv4/IPv6. With those settings, the phone hotspot works. Great right? Almost. Unfortunately, with those settings, I can no longer send group MMS. And to make matters stranger, my wife has an identical phone without hotspot issues. Can you help please? -Thanks! Name: T-Mobile APN: Fast.t-mobile.com Proxy: <Not set> Port: <Not set> Username: <Not set> Password: <Not set> Server: <Not set> MMSC:http://mms.msg.eng.t-mobile.com/mms/wapenc MMS proxy: <Not set> MMS port: <Not set> MCC: 310 MNC: 260 Authentication Type: <Not set> APN Type: default,supl,mms APN Protocol: IPv4/IPv6 APN roaming protocol: IPv4/IPv6 Turn APN on/off: Grayed out Bearer: Unspecified Mobile virtual network operator type:GID Mobile virtual network operator value:544D
With happiness, why has FTP started to work with T-Mobile home internet?
I've had T-Mobile home internet several months now. Having made it through severalissues I'm glad I stayed with T-Mobile. Because T-Mobile maps IPV4 over IPV6, FTP did not work. To use FTP I had to subscribe to a VPN, turn it on when FTP was needed then turn off again. I've been using NordVPN for that. However, just now I attempted some file transfers and they worked! All my FTP logins work without using the VPN. This is wonderful. So I'mwondering if anyone knows what changed. Was it T-Mobile? Was it something else? It isn't the FTP servers or protocols or the internet in general. I use multiple FTP servers. So it has to be T-Mobile.Solving CGNAT problems?
AFAICT my T-Mobile Internet router connects to a CGNAT DMZ, and every time I connect to a networkservice I do so from what appears to that service to be a different IP4 address. There seem to be exceptions, however, for some known protocols - I've had an SSH session up for several consecutive days. So one CAN obtain a static IP address for things like VPNs and SSH, but the protocol has to be well-known. Therefore, questions: Is there an IPV4 packet flag that says "this session needs a static IP address" to routers along the way? Routers are already reading the port assignments in order to determine "oh, that's SSH, better make this static." Is there a packet flag one can set? If I turned off IPV4 and just used IPV6 would the CGNAT DMZ provide a static address, since I wouldn't need to be sharing IPV4 addresses any more?
T-Mobile Home Internet Slow IPv4
Hi all, I'm having a terrible experience lately using the T-MobileTM-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. Thanks, Jason