Flint 2 (GL-MT6000 ) - bug reports - collective thread

Routers
63

@admon Sure thing Flint 2 (GL-MT6000) unable to create Wireguard profiles

64

sorry
i just noticed the plug to the powered usb hub was lose
once the hub got power all usb hdds show as connected now!

2 Likes
65

I really wish Gl-Inet had a public bug tracking system for reporting new bugs, for example like the “issues” in github or bugzilla.

66

Yes and no. Public bug trackers are great for people who know how to use them. Unfortunately, you also see time and again that GitHub projects no longer accept issues because the reporters of the problem do not adhere to the policy or cannot provide basic information.

Bug trackers are great if you work with highly technical people - or your staff will manage the issues.

1 Like
67

MT6000 BUG REPORT - multiple reboots during the first day of operation

I received yesterday morning my two MT6000 routers, and one of them has now been running for about 24 hours. I was hoping for a flawless experience, but I had in that period at least 6 unexpected reboots, whereas one of these left the device in a status in which the WAN connection did not get back by itself until I had performed a manual reboot. So already after one day it is now time for a bug report…

Some details about the conditions in which the router has been working, and how the reboots occurred:

  • at the start of the installation I upgraded the router from v4.5.2 to v4.5.3

  • the router replaced a previous router to take care of 30-40 devices: a few connected through LAN, a few through 5G WIfi, and the majority via 2.4G Wifi (3 tablets, one PC used for browsing and communication, some security cameras, and a number of swtiches and light bulbs - no gaming or any other heavy internet / LAN usage)

  • I added a static address for each of these devices by adding them in the /etc/config/dhcp file

  • the router has been all the time connected to the original power supply

  • both the 2.4G Wifi and 5G Wifi have been working with the maximum power setting

  • the ambient temperature has been around 23 degrees and a fan beside of the router has been running continously to create an airflow, in order to avoid any overheating effects

  • after the 30-40 devices were connected I added a USB key with multimedia files and I switched on the DLNA server, which I tested succesfully

  • after a few hours I added another 20 Wifi devices to the router by transferring them from a different router in my network using the 2.4G guest account of the MT6000 (I used the SSID of the original router for the guest account after that router had been disabled) and I checked the CPU and memory behaviour several times but there was no visible increase compared to before

  • after some time there was a first unexpected reboot, which did not really surprise me because with my Flint 1 I already have expierenced that same situation: using the guest account strongly increases the risk of random reboots…

  • after that I disabled the guest account and disconnected the 20 additional devices, hoping that it would stop further issues, and the router passed a quiet night without any reboots while still taking care of 30-40 devices

  • today I started using the Wireguard server, with the 30-40 devices still connected, and unfortunately this resulted in 4 more more unexpected reboots, of which one that kept the router in a disconnected WAN state with the LED blue blinking: whereas the WAN port was connected to the LAN output of another router which was working fine without any internet problems, only the Wifi of the MT6000 got back after the reboot so I could connect and check that the WAN was not recognized with all lines in the Ethernet 1 section of the Admin Panel remaining empty (this is quite worrying to me because the router will need to be working remotely often and when the WAN connection blocks there is no way to get the router back on track from distance without the access to GoodCloud or DDNS)

  • before starting to make this report I removed the USB key, I disabled the DLNA server and I switched both the 2.4 G and 5G Wifi from Max to High, hoping that this would reduce the reboot risk, but just now while writing there was another reboot so this did not help

  • I have saved the crash reports after each reboot, so I can send them to the support team if they give me an e-mail address for that (I will not post them here for confidentiality reasons)

  • in my network I have one router which checks continously the health of all other routers, and I get automatic notifications for every reboot - therefore other MT6000 owners might also have these kind of reboots but without being aware of it

I will install during the coming weekend my second MT6000, which is supposed to run in similar conditions: 40-50 devices, with DNLA server and USB Key, and also with enabled Wireguard server, so it will be interesting to see if similar reboots will happen as well for the second router.
Meanwhile I hope that the support team can find out where these reboots are coming from and that the issue can be solved soon.

68

After the 4.5.4 update, my wifi no longer presents problems with a bad connection or incorrect password error, it took me a while to get back to you because I was evaluating day after day to see if I had the errors and there were no more problems, so this version is being better.

69

What is the cause of the crashes according to the crash logs?

Try the beta firmware 4.5.4.

70

I see every time this type of line in the Crash log:

Unable to handle kernel paging request at virtual address ffffffffc0000000

71

Please show the full crash log.

72

Can you give me an e-mail address to send the Crash log to?

73

[email protected]

74

Thanks, I have sent you 5 Crash and Kernel reports that were saved after the reboots

75

https://dl.gl-inet.com/?model=mt6000&type=beta

Please try this firmware.

76

Thanks for your fast reaction, I have installed the 4.5.4 beta firmware and I will report later on whether the reboot issue is still present

77

@JerryZhao I’m still having the same crashes with Version 4.5.4. Was 4.5.4 supposed to fix them?

Crashlog: https://pastebin.com/JrDjV6ib

78

At my side, there have been no new reboots after having changed to version 4.5.4 this morning, even after enabling the guest account with 20 additional devices and keeping Wireguard and DNLA switched on again…

1 Like
79

I noticed a bug now, connected to 2.4ghz on the PC the speed goes to maximum, now connected to Android it doesn’t exceed 100mb, and the same test with the same conditions on the mt3000 reaches 200 almost 300, as my internet is 300mb, Could you check if the same thing happens on your MT6000?

2 Likes
80

Slow 2.4 GHz AX speeds happen to me as well on iPhone 14. Further away also latency increases a lot like above 100 ms from 20-30 ms when close by.

81

I bought into the hype, purchased a Flint 2, and recommended it to many others, but now I’m regretting my decision due to basic configuration issues and bugs. This is like the Linksys WRT3200/WRT32X debut years ago and the fiasco of their Wi-Fi issues, amongst other problems.

Here are some problems that I immediately noticed.

  1. Wi-Fi issues - Slow 2.4 GHz performance. Unstable Wi-Fi 5 (ac) for devices like my Apple TV 4K 1st Gen. Apps on it exhibit A//V streaming buffering. In this case, the device is 15 feet away. Interestingly, newer devices, such as MacBooks and iPhones that are Wi-Fi 6 capable perform optimally. Additionally, there are no buffering issues on 2.4 GHz. I’m toggling between them; both aren’t on at the same time.
  2. Software version mismatch - DDNS in Luci reports a version of 2.8.2-37, but when you install a new service instance and read the log, it reports ddns version : 2.7.7-6. Due to this, the Cloudflare DDNS scripts fail when creating a new service instance.
  3. U-Boot Environment Corruption - When issuing a fw_printenv command, it results in a CRC warning and incomplete listing.
    Warning: Bad CRC, using default environment
    bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
    bootdelay=5
    baudrate=115200

I’m coming from a WRT32X running OpenWrt 23.05.0 and have yet to get to the complex configurations on my Flint 2. Hopefully, that will go better.

3 Likes
82

I have the same experience especially with Wifi 2.4GHz where the performance is very poor with Android devices, even my old Slate AR750s is better

1 Like