TL-MR6400 disconnected many times per day
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Introduction:
LTE internet connection dies frequently. Typically happens when the WiFi has been idle for a couple of minutes. When there are no other devices connected at the wee hours, just me and my laptop, it's often disconnected by the time I've read a long page. However, if I have e.g. a download running on the background, it doesn't happen.
Sometimes the router manages to reconnect to the internet by itself. However, I often have to log in to the router and try to get it moving. "Basic" mode Internet icon clicking often does the trick, suppose it reminds the router to check status and try again. Sometimes a reboot is required. (Typically after enough minutes of attempting to fix it by poking around places with no success.) It's rather irritating when it happens after every couple of minutes of idle. I'd rather not have to craft up a keep-alive bot that generates dummy background traffic to tackle this nuisance.
When the LTE disconnects, it's dead in the water. Local network functions, but DNS server pings, etc. all fail. Sometimes it still shows an IP address, anyone's guess as to if that's just the last known IP still lingering.
In recommended steps from earlier in this thread, I've re-created the ISP profile, makes no difference. I've also browsed through the syslogs, please see at the end. The LTE band doesn't correlate with disconnects. Signal strength from ISP is typically 50-75%, and there are no such issues when using the SIM with a phone.
I've had the device for a couple of months now, and it's been consistently doing this. I haven't ran out of patience yet, but I assure you that day is in the horizon. I specifically chose TP-Link to have a stable product!?.
Router Specs:
- Model: TL-MR6400(EU)
- Country: Indonesia (Purchase & Use Location)
- Firmware Version:1.10.0 0.9.1 v0001.0 Build 190521 Rel.38696n
- Hardware Version:TL-MR6400 v4 00000001
This being the latest publicly available firmware. If there's a beta firmware available, I wouldn't mind giving it a shot. However, could you please let me know what exact issues the beta firmware actually addresses? I'd rather not flash the device and risk introducing glitches in unrelated areas, if there's nothing in the beta that obviously correlates with this particular issue.
Errors & System Log:
When disconnects happen, the Basic/Advanced page sometimes shows: "Unknown failure reason. Please make sure your configuration is correct." (It is.) Sometimes it just says "Disconnected". Attached screenshots from the Basic/Advanced pages. (After clicking back from "Advanced" to "Basic", the router remembered to try and reconnect, and now I can post this.)
Then, as far as syslog contents. I have exactly 24 instances of these entries in the syslog from the last 24 hours. Level is set to "Debug". The disconnect is always associated with "QMI_ERR_CALL_FAILED", followed by "reason = 2001, type = 3". (Edit: I've also come across "reason = 210, type = 2", the rest being the same.)
2020-07-20 00:24:51 [6] 4G: USER: Get ISP's profile now.
2020-07-20 00:24:51 [6] 4G: USER: GetCurrProf result is:ipver:0 staticApn:0 authType:2 pkgName:TELKOMSEL profname:TELKOMSEL apn:internet usr: psw:
2020-07-20 00:24:51 [6] 4G: ERROR: 0x0000000E QMI_ERR_CALL_FAILED
2020-07-20 00:24:51 [6] 4G: ERROR: Call end reason = 3.
2020-07-20 00:24:51 [6] 4G: ERROR: Verbose Call end reason = 2001, type = 3.
2020-07-20 00:24:51 [6] 4G: USER: Fail to connect to the network, start autoconnect!
2020-07-20 00:28:02 [6] 4G: USER: The network disconnected, start autoconnect!
2020-07-20 00:28:02 [6] 4G: USER: Get ISP's profile now.
2020-07-20 00:28:02 [6] 4G: USER: GetCurrProf result is:ipver:0 staticApn:0 authType:2 pkgName:TELKOMSEL profname:TELKOMSEL apn:internet usr: psw:
2020-07-20 00:28:02 [6] 4G: ERROR: 0x0000000E QMI_ERR_CALL_FAILED
2020-07-20 00:28:02 [6] 4G: ERROR: Call end reason = 3.
2020-07-20 00:28:02 [6] 4G: ERROR: Verbose Call end reason = 2001, type = 3.
2020-07-20 00:28:02 [6] 4G: USER: Fail to connect to the network, start autoconnect!
Other relevant notes:
My ISP, Telkomsel (the largest telecom in Indonesia and majority infrastructure holder) runs a Double NAT setup for internet subscribers. That's why you see a 10.x.x.x private-block IP allocated on the router status page; while the actual post-NAT public IP would be different (and often in rapid rotation). I have no doubt that other telecoms here are doing the same, given the massive subscriber base in a developing country of now 170+M internet users, and the scarcity of the available IPv4 address pool. I don't know if this is consequential to the issue at hand, but thought it worth mentioning, for the tech staff troubleshooting the ubiquitous disconnect issues with MR-series router users.
Hello all forum users!
User MarkusAO is right. Unfortunately, I have had the same equipment for four months and I run into the same problem, which seems to be quite common. I use the router in a holiday home, on a video surveillance system. When I live there, an online radio station runs all day in the background and there is no disconnection from the network. When there is no more random network traffic, the router starts to disconnect.
--- Sometimes the router manages to reconnect to the internet by itself. However, I often have to log in to the router and try to get it moving. "Basic" mode Internet icon clicking often does the trick, suppose it reminds the router to check status and try again. Sometimes a reboot is required. (Typically after enough minutes of attempting to fix it by poking around places with no success.) It's rather irritating when it happens after every couple of minutes of idle. I'd rather not have to craft up a keep-alive bot that generates dummy background traffic to tackle this nuisance .--- quoted from user MarkusAO.
Engineers at tp-link, what are you doing? Sleep? There are over a hundred identical issues here on the forum and probably hundreds more unreported! I bought this router to benefit from the brand's reputation. I think I was wrong. I will return it to the warranty and I will justify my action including through the posts in this forum.
I am attaching a photo with a router type in which it can be seen that it has the latest software update.
