My setup was working before, but it stopped working sometime in the last month or so while we were away from home. The only error I see in the interface is this:
"The interface is connected, but the Internet can't be accessed."
I had to clone the IMEI from my T-Mobile router (which is still working fine) to set up the GL-X3000. That IMEI is still there, and on my side nothing changed. I did update to the latest firmware manually, but no change.
Any advice?
Thanks.
Hello,
ping [Modem Gateway] or ping www.google.comHi, Bruce.
The SIM comes from a T-Mobile router. It works fine in that router now, and was working fine in the GL.iNet router until very recently.
From a PC on the network, I can ping the modem gateway (of course) as well as connect to the web interface, but I cannot ping google.com. Name resolution does appear to work, however. Very strange.
Cellular antennas are fine. I've tried fast.t-mobile.com and fbb.home as APNs. No luck with either.
Hi,
May I know ping 8.8.8.8 and ping www.google.com in router SSH are available?
Please try change the MTU, like 1420, 1380, or lower.
Neither ping succeeds. I've tried changing the MTU (e.g. to 1300). No change.
Hello, can we have a remote check? Could you bind your device to Goodcloud and share to GL.iNet for troubleshooting?
Unfortunately T-Mobile Home Internet is my only ISP, so that would be very complicated. I havea T-Mobile-native router that works for now (which I'd replaced with the X3000). So we'd have to arrange a specific time to avoid work calls, and I'd have to figure out how to connect the router to a mobile hotspot for internet access since the TMHI SIM no longer connects on the X3000.
Understood. Can you provide the following information with us to check first:
And could you share with me a screenshot showing the cellular configuration of the T-mobile router? Just want to see if there is any special config. Thanks
Not sure you would have had to clone the IMEI. I've used TMO sims in various gizmos for decades without doing that.
There are tons of info in the gui for x3000 and might be some online via your phone Tlife app that can help.
There should be * Access Point Name (APN): fast.t-mobile.com
You should be able to search for points.
Look at IP addresses, I'd disable IPv6 and force only IPv4.
For TMHI, you need to clone the IMEI of the TMo device to the X3000 and set the APN to fbb.home. At least that was the way it was when I was doing this. No other messing with TTL or anything was needed.
@Cathy: I've attached the files you requested. One system log is with the default APN (fast.t-mobile.com) and another is with the APN manually set to fbb.home. Needless to say, neither works. I've also attached config screenshots of SIM1 and SIM2. On SIM1 I've made some changes based on people's suggestions online. With SIM2 I just have the defaults + the APN change I mentioned above. And again, nothing works.
system-fast.tar (172.5 KB)
system-fbb.tar (174 KB)
modem-debug.zip (1.4 KB)
Cloning the IMEI is required with TMHI SIMs, AFAIK. It was definitely required for me, back when this configuration was working.
I've tried with and without IPv6. No change in behavior. Same with setting fbb.home as the APN.
change the APN to fast.metropcs.com, to give a try, some user has issue for fbb.home (perhaps local infrastructure or tower specific) .
Yes I am talking about tmobile home internet.
Hi @IMarshal
You can follow meerkat's suggestion and set the APN as fast.metropcs.com.
Or update X3000 to this beta version and try it again.
If it still doesn't work, we need to obtain the modem log for further analysis.
@Cathy: setting the APN to fast.metropcs.com doesn't change anything. Same results as the other two T-Mobile APNs: interface connected, internet can't be accessed.
I also tried the 4.8 beta firmware. No change in behavior. Here are system and modem logs. Please advise.
Thanks.
logread.tar (195 KB)
modem-debug.zip (1.6 KB)
What’s the APN used by your T-mobile router? This sim card can work properly with the T-mobile router, right?
We need to get some modem logs to check. I will provide with you the required tools later.
@Cathy: I have a Nokia 5G21 gateway from T-Mobile and it works fine with this SIM card. That's my internet provider at the moment, and it was working great with the GL-X3000 until it suddenly stopped working. I was able to run the dashboard_device_status_web_app.cgi script on the Nokia and that says it's using the fbb.home APN.
"apn_cfg":[{"oid":1
,"Enable":1,
"APN":"fbb.home",
"X_ALU_COM_ServiceType":"TR069,INTERNET",
"X_ALU_COM_ConnectionState":1,
"X_ALU_COM_IPAddressV4":"",
"X_ALU_COM_IPAddressV6":"2607:fb90:etc"
},{"oid":2
,"Enable":1,
"APN":"ims",
"X_ALU_COM_ServiceType":"VOICE",
"X_ALU_COM_ConnectionState":0,
"X_ALU_COM_IPAddressV4":"",
"X_ALU_COM_IPAddressV6":""
}]
And I thought I'd uploaded modem logs above?
I signed up for an account just for this issue. About 2-3 weeks ago, I woke up with my internet really slow and broken. Restarted my GL-XE3000 (GL-X3000 with backup battery), and it says no internet and I couldn't not ping 8.8.8.8 on the network. Updated with the latest beta firmware and still doesn't work. I also used the fbb.home APN. It was working perfectly fine before. Now I have to revert back to using the default T-Mobile G4SE gateway. At this point, it is a $370 deadweight. Will try to do some troubelshooting when I have time, but just want to report the issue is also happening elsewhere.
@Blah1234: maybe you can check and see if you're seeing what I'm seeing. At this point it looks like IPv4 doesn't work, but IPv6 works. Here's a way to replicate that from a command prompt on a PC behind the GL.iNet router:
C:>nslookup google.com
Server: GL-X3000.lan
Address: fd04:f1fd:a6a4::1
Non-authoritative answer:
Name: google.com
Addresses: 2607:f8b0:4006:820::200e
172.217.164.110
C:>ping 172.217.164.110
Pinging 172.217.164.110 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 172.217.164.110:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:>ping 2607:f8b0:4006:820::200e
Pinging 2607:f8b0:4006:820::200e with 32 bytes of data:
Reply from 2607:f8b0:4006:820::200e: time=90ms
Reply from 2607:f8b0:4006:820::200e: time=100ms
Reply from 2607:f8b0:4006:820::200e: time=95ms
Reply from 2607:f8b0:4006:820::200e: time=100ms
Ping statistics for 2607:f8b0:4006:820::200e:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 100ms, Average = 96ms
Maybe TMo is enforcing hardware changes and is detecting these SIMs are not in TMo equipment somehow. Could be using GPS as an indicator I guess. Not for location, for a response that may not be provided by X3000 but is by the TMo hardware.