GL.iNET Flint 2 (GL-MT6000) discussions

phinn · January 31, 2024, 2:43pm

Added an AP section with topics for those configuring this as a dumb AP:

[https://openwrt.org/toh/gl.inet/gl-mt6000#access_point_mode]

Kinfolk3106 · February 1, 2024, 3:33pm

Could you send me the link to any issues on Github that report this problem so I can send it to the router developers?

thedude · February 1, 2024, 5:13pm

Nobody has reported the issue yet, so if 2.4GHz is a lot faster then you'd need to report the issue here. But the report needs to be as detailed as possible, since it's not enough to say that 2.4GHz is a lot faster when using the proprietary MediaTek driver.

Use the same WiFi settings on both firmwares
Disable 5GHz and limit the 2.4GHz mode to N on both firmwares
Share the contents of /etc/config/wireless from both firmwares
Share the log file from both firmwares
Input iw phy0 info and share the output from both firmwares
Perform online speed tests with both firmwares
Perform local iPerf3 speed tests with both firmwares

The title should be something like "MT7986: Slow 2.4GHz WiFi compared to proprietary driver".

dr-dolomite · February 1, 2024, 11:59pm

I can testify to this also. 2.4Ghz is indeed working "normally" on proprietary driver. Will do these tests if Ive got time.

fakemanhk · February 2, 2024, 2:11am

Hi, can you tell me more information about this bug? I am using IPv6 at home as well, and does this affect all kind of devices or just Mediatek based?

SiXX · February 2, 2024, 2:25am

I was referring to bugs in the Dynalink, which is Qualcomm based. I have not had to do this with the MT6000 (mediatek).

xize · February 3, 2024, 3:42pm

for me the latest snapshot breaks 2.4ghz too much (OpenWrt SNAPSHOT r24993-32b4498c15).

both my Poco X6 Pro and one homewizard meter are unable to connect this first started when I changed the mode from WPA2 (CCMP) to WPA3/WPA2 mixed and then back.

then I rebooted these misbehaving devices because it kept disconnecting, I got greeted with multiple messages like: psk mismatch, to "tries to authenticate before asociating", it made no sense

then the errors for the not authenticated/psk mismatch error are gone.

but as by product it did something awfully strange to dnsmasq:

full log

Sat Feb  3 15:15:05 2024 daemon.err dnsmasq[1]: failed to send packet: Resource temporarily unavailable
Sat Feb  3 15:15:05 2024 daemon.err dnsmasq[1]: failed to send packet: Resource temporarily unavailable
Sat Feb  3 15:15:05 2024 daemon.err dnsmasq[1]: failed to send packet: Resource temporarily unavailable
Sat Feb  3 15:15:05 2024 daemon.err dnsmasq[1]: failed to send packet: Resource temporarily unavailable
Sat Feb  3 15:15:05 2024 daemon.err dnsmasq[1]: failed to send packet: Resource temporarily unavailable
Sat Feb  3 15:15:05 2024 daemon.err dnsmasq[1]: failed to send packet: Resource temporarily unavailable
Sat Feb  3 15:15:05 2024 daemon.err dnsmasq[1]: failed to send packet: Resource temporarily unavailable
Sat Feb  3 15:15:06 2024 daemon.err dnsmasq[1]: failed to send packet: Resource temporarily unavailable
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: Remove interface 'phy0'
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: interface state ENABLED->DISABLED
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 54:ef:44:35:94:4c
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 5c:2f:af:12:10:ae
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 8c:de:f9:87:fd:f8
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 6a:e0:92:a3:a6:35
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 5c:2f:af:16:8d:9e
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 5c:2f:af:14:22:28
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 5c:2f:af:01:d0:98
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 5c:2f:af:01:cb:88
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 5c:2f:af:01:fa:22
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
Sat Feb  3 15:15:06 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0
Sat Feb  3 15:15:06 2024 kern.info kernel: [  545.194514] device phy0-ap0 left promiscuous mode
Sat Feb  3 15:15:06 2024 kern.info kernel: [  545.199322] br-zigbee: port 2(phy0-ap0) entered disabled state
Sat Feb  3 15:15:06 2024 daemon.notice netifd: Network device 'phy0-ap0' link is down
Sat Feb  3 15:15:06 2024 daemon.notice ttyd[3977]: [2024/02/03 15:15:06:5981] N: rops_handle_POLLIN_netlink: DELADDR
Sat Feb  3 15:15:06 2024 daemon.notice wpa_supplicant[1758]: Set new config for phy phy0
Sat Feb  3 15:15:06 2024 daemon.notice netifd: Wireless device 'radio0' is now down
Sat Feb  3 15:15:06 2024 daemon.notice netifd: radio0 (14752): WARNING: Variable 'data' does not exist or is not an array/object
Sat Feb  3 15:15:06 2024 daemon.notice hostapd: Set new config for phy phy0:
Sat Feb  3 15:15:06 2024 daemon.notice wpa_supplicant[1758]: Set new config for phy phy0
Sat Feb  3 15:15:07 2024 daemon.notice wpa_supplicant[1758]: Set new config for phy phy0
Sat Feb  3 15:15:07 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat Feb  3 15:15:07 2024 daemon.notice hostapd: Restart interface for phy phy0
Sat Feb  3 15:15:07 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=NL ieee80211d=1 hw_mode=g supported_rates=60 90 120 180 240 360 480 540 basic_rates=60 120 240 beacon_int=100 chanlist=8 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935] ieee80211ax=1 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=128 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca_qos_info_txop_request=0 he_mu_edca_ac_be_aifsn=8 he_mu_edca_ac_be_aci=0 he_mu_edca_ac_be_ecwmin=9 he_mu_edca_ac_be_ecwmax=10 he_mu_edca_ac_be_timer=255 he_mu_edca_ac_bk_aifsn=15 he_mu_edca_ac_bk_aci=1 he_mu_edca_ac_bk_ecwmin=9 he_mu_edca_ac_bk_ecwmax=10 he_mu_edca_ac_bk_timer=255 he_mu_edca_ac_vi_ecwmin=5 he_mu_edca_ac_vi_ecwmax=7 he_mu_edca_ac_vi_aif
Sat Feb  3 15:15:07 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Sat Feb  3 15:15:07 2024 kern.info kernel: [  545.917172] br-zigbee: port 2(phy0-ap0) entered blocking state
Sat Feb  3 15:15:07 2024 kern.info kernel: [  545.923013] br-zigbee: port 2(phy0-ap0) entered disabled state
Sat Feb  3 15:15:07 2024 kern.info kernel: [  545.929085] device phy0-ap0 entered promiscuous mode
Sat Feb  3 15:15:07 2024 kern.info kernel: [  545.934244] br-zigbee: port 2(phy0-ap0) entered blocking state
Sat Feb  3 15:15:07 2024 kern.info kernel: [  545.940075] br-zigbee: port 2(phy0-ap0) entered forwarding state
Sat Feb  3 15:15:07 2024 daemon.notice hostapd: phy0-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat Feb  3 15:15:07 2024 daemon.notice netifd: Network device 'phy0-ap0' link is up
Sat Feb  3 15:15:07 2024 kern.info kernel: [  546.179354] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
Sat Feb  3 15:15:07 2024 daemon.notice hostapd: phy0-ap0: interface state COUNTRY_UPDATE->ENABLED
Sat Feb  3 15:15:07 2024 daemon.notice hostapd: phy0-ap0: AP-ENABLED
Sat Feb  3 15:15:09 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:d0:98 IEEE 802.11: authenticated
Sat Feb  3 15:15:09 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:fa:22 IEEE 802.11: authenticated
Sat Feb  3 15:15:09 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:14:22:28 IEEE 802.11: authenticated
Sat Feb  3 15:15:09 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:cb:88 IEEE 802.11: authenticated
Sat Feb  3 15:15:12 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:14:22:28 IEEE 802.11: associated (aid 3)
Sat Feb  3 15:15:12 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:cb:88 IEEE 802.11: associated (aid 4)
Sat Feb  3 15:15:13 2024 daemon.notice hostapd: phy0-ap0: STA 5c:2f:af:12:10:ae IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:14 2024 daemon.notice hostapd: phy0-ap0: STA 5c:2f:af:16:8d:9e IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:14 2024 daemon.info hostapd: phy0-ap0: STA 8c:de:f9:87:fd:f8 IEEE 802.11: authenticated
Sat Feb  3 15:15:14 2024 daemon.info hostapd: phy0-ap0: STA 8c:de:f9:87:fd:f8 IEEE 802.11: authenticated
Sat Feb  3 15:15:15 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:d0:98 IEEE 802.11: authenticated
Sat Feb  3 15:15:15 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:fa:22 IEEE 802.11: authenticated
Sat Feb  3 15:15:15 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:14:22:28 IEEE 802.11: authenticated
Sat Feb  3 15:15:15 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:cb:88 IEEE 802.11: authenticated
Sat Feb  3 15:15:16 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:14:22:28 IEEE 802.11: associated (aid 3)
Sat Feb  3 15:15:16 2024 daemon.err hostapd: nl80211: NL80211_ATTR_STA_VLAN (addr=5c:2f:af:14:22:28 ifname=phy0-ap0 vlan_id=0) failed: -2 (No such file or directory)
Sat Feb  3 15:15:16 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:cb:88 IEEE 802.11: associated (aid 4)
Sat Feb  3 15:15:16 2024 daemon.err hostapd: nl80211: NL80211_ATTR_STA_VLAN (addr=5c:2f:af:01:cb:88 ifname=phy0-ap0 vlan_id=0) failed: -2 (No such file or directory)
Sat Feb  3 15:15:18 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:d0:98 IEEE 802.11: associated (aid 1)
Sat Feb  3 15:15:18 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:fa:22 IEEE 802.11: associated (aid 2)
Sat Feb  3 15:15:20 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:14:22:28 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Feb  3 15:15:20 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:cb:88 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Feb  3 15:15:21 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:fa:22 IEEE 802.11: authenticated
Sat Feb  3 15:15:21 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:d0:98 IEEE 802.11: authenticated
Sat Feb  3 15:15:21 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:14:22:28 IEEE 802.11: authenticated
Sat Feb  3 15:15:21 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:cb:88 IEEE 802.11: authenticated
Sat Feb  3 15:15:22 2024 daemon.notice hostapd: phy0-ap0: STA 8c:de:f9:87:fd:f8 IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:23 2024 daemon.notice hostapd: phy0-ap0: STA 8c:de:f9:87:fd:f8 IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:24 2024 daemon.notice hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:25 2024 daemon.notice hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:26 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:d0:98 IEEE 802.11: deauthenticated due to local deauth request
Sat Feb  3 15:15:26 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:fa:22 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Feb  3 15:15:26 2024 daemon.notice hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:27 2024 daemon.notice hostapd: phy0-ap0: STA 5c:2f:af:12:10:ae IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:27 2024 daemon.notice hostapd: phy0-ap0: STA 5c:2f:af:16:8d:9e IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:28 2024 daemon.notice hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:28 2024 daemon.notice hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:30 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:cb:88 IEEE 802.11: authenticated
Sat Feb  3 15:15:30 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:14:22:28 IEEE 802.11: authenticated
Sat Feb  3 15:15:31 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:d0:98 IEEE 802.11: authenticated
Sat Feb  3 15:15:32 2024 daemon.notice hostapd: phy0-ap0: STA 5c:2f:af:01:fa:22 IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:33 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:fa:22 IEEE 802.11: associated (aid 0)
Sat Feb  3 15:15:33 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:cb:88 IEEE 802.11: associated (aid 1)
Sat Feb  3 15:15:33 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:14:22:28 IEEE 802.11: associated (aid 2)
Sat Feb  3 15:15:34 2024 daemon.info hostapd: phy0-ap0: STA 5c:2f:af:01:d0:98 IEEE 802.11: associated (aid 3)
Sat Feb  3 15:15:34 2024 daemon.notice hostapd: phy0-ap0: STA 8c:de:f9:87:fd:f8 IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:35 2024 daemon.notice hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:36 2024 daemon.notice hostapd: phy0-ap0: STA 8c:de:f9:87:fd:f8 IEEE 802.11: did not acknowledge authentication response
Sat Feb  3 15:15:37 2024 daemon.info hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: authenticated
Sat Feb  3 15:15:37 2024 daemon.info hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: authenticated
Sat Feb  3 15:15:38 2024 daemon.info hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: associated (aid 4)
Sat Feb  3 15:15:38 2024 daemon.info hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: associated (aid 4)
Sat Feb  3 15:15:38 2024 daemon.info hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: associated (aid 4)
Sat Feb  3 15:15:38 2024 daemon.notice hostapd: WPA: Multiple EAP reauth attempts without 4-way handshake completion, disconnect 54:ef:44:35:94:4c
Sat Feb  3 15:15:38 2024 daemon.info hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: associated (aid 4)
Sat Feb  3 15:15:38 2024 daemon.err hostapd: nl80211: NL80211_ATTR_STA_VLAN (addr=54:ef:44:35:94:4c ifname=phy0-ap0 vlan_id=0) failed: -2 (No such file or directory)
Sat Feb  3 15:15:38 2024 daemon.info hostapd: phy0-ap0: STA 54:ef:44:35:94:4c IEEE 802.11: authenticated

if I need to post a config please let me know the issue is its beyond the text limit and i cannot upload a zip file or txt files. my network is very advanced but that might make it more interesting to test certain use cases

foggygray · February 4, 2024, 1:50pm

Looks like there’s driver updates in the snapshot for MT76 and associated chips. Has anyone been able test them yet? Firmware selector and attended sysupgrade aren’t working right now so I haven’t been able to install them.

vw-owrt · February 4, 2024, 3:26pm

Have not been able to update either due to the build environments not working.

UPDATE: I was able update to SNAPSHOT r25002-6e8df06fc1 by downloading the default sysupgrade image from the firmware builder page then use vi to copy / paste the network config entries I needed from an archive. I was then able to add back my packages then my backup configuration. Then I did the same for my mesh node but since it's a basic setup, I was able to keep settings and only had to bring it near to the main router and tether with Ethernet in order to remove wad-basic-mbedtls and install wpad-mbedtls so mesh would work again.

Luckily this router has an easy uboot recovery so if I had gotten stuck I could have always flashed back to a previous version.

Anyway, thought I'd share for anyone who has a bit of free time, does not have the knowledge to create their own imagebuilder environment and wants to be up-to-date. Hopefully the online build environments will be working again, soon.

Kinfolk3106 · February 4, 2024, 6:04pm

The developers released a beta version with Mediatek's proprietary drivers to try to solve the problem of slow Wifi and recurring disconnections. It's worth testing to see if the performance was superior to open source drivers: https://dl.gl-inet.com/?model=mt6000&type=beta

di_Niko · February 4, 2024, 7:15pm

Nothing worth the use of discontinued openwrt version.

Reznale · February 5, 2024, 1:02pm

I just did a little test on r25004, reading/writing to a usb hdd on the router was 125-130MB/s both ways for 5ghz 160mhz, and 18-20MB/s both ways for 2.4ghz 20mhz, on an Intel AX200 card right beside the router. I haven't had any wifi issues personally but almost every device connects to 5ghz.

phinn · February 6, 2024, 1:49pm

Looking closely at the m76 driver update there isn't anything for our mt7976 wifi, it should be about the same. I plan on running a new build off in the next few days to test though. Performance has been great for me lately, 1 month uptime zero issues.

If there is any excitement to be had from that driver update is all the wifi 7 device additions. Seems like wifi 7 mediatek devices should work great in OpenWrt once they start shipping.

abceleung · February 7, 2024, 4:16am

Hi, I want to buy this device for my small homelab. Any caveat I need to look out for (Beside bad 2.4GHz performance and only snapshot build available)?

I also noticed that this model uses Realtek switch chip for the dual 2.5G ports. Is it supported by OpenWrt?

phinn · February 8, 2024, 4:02pm

Fantastic device I recommend it. Replaced my WRT32X/U6+ combo with only this. Stable too, had a 30-day uptime with a ton of added packages running before reflashing for the newer mt76 driver.

Yes 2.5G works, you can see them on the TOH page bootlog, e.g.:
[ 13.258001] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:01] driver [RTL8221B-VB-CG 2.5Gbps PHY] (irq=62)
[ 13.258286] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/2500base-x link mode

I haven't tested the max speed since I don't have a 2.5Gbit device on them (PC has 2.5Gbit but connected to a 1Gbit switch port) but the future proofing is there

Kinfolk3106 · February 8, 2024, 4:21pm

Were you able to perform tests with the m76 driver?

phinn · February 8, 2024, 5:45pm

Yes runs great but roughly identical from the older driver. I didn't do any long range tests past my usual ~15-ft point though. They were lots of bug fixes so it most likely wouldn't affect speed or range.

foggygray · February 8, 2024, 6:57pm

I have mine hooked up to the 2.5Gb port on my modem and I have a 2.5Gb switch and the ports register as 2.5. That’s just future proofing for me as I don’t have any 2.5Gb computers or other devices to test with.

di_Niko · February 8, 2024, 9:16pm

In my case its gigabit fiber with 2.5 gb ont, i can easily reach 1015/1015 using 160mhz

abceleung · February 9, 2024, 4:10am

Thanks for the answers everyone. Another (silly) question, since the 2.5G ports and 1G ports use separate switch chips, is there a bandwidth limit between them?
For example, I have 2 clients plugged to the 1G ports and one 2.5G port connected to a 2.5G port NAS. Both clients start downloading a large file from the NAS. Will the download speed of both clients stay close to 1G?