Issues With GL-iNet Flint 2 WiFi Not Providing Proper Bandwidth On WiFi Connections 25.05.4

[Oliumen]

I have the following setup...

The Router PC's specs are as follows...

Dell Optiplex 9020
Intel Core i5-4750 CPU @ 3.2 GHz x4
Mesa Intel HD Graphics 4600 (HSW GT2)
Samsung SSD 120 GB
32 GB of DDR3@1600 CL 11
PCIe Ethernet Card(I forget which one, some Intel card) with 2 interfaces.

I am using OpenWRT 23.05.5 ( Main router) and OpenWRT 23.05.4(Gl-inet Flint 2 acting as a Dumb AP) with a generic-squashfs-combined-efi.img.gz on the main router and whatever the community package is for the Flint2.

My AP is one of these devices...

Gl-inet Flint2
https://openwrt.org/toh/gl.inet/gl-mt6000

===

Network setup is as follows...

ISP Fiber Line to Home.
ISP Fiber Line to home to ISP Fiber Modem.
ISP Fiber Modem to Ethernet to Router (eth2 Wan).
Router Ethernet card(eth0,eth1) to Dumb AP(Flint2) with OpenWRT 23.05.4 via Ethernet cable from (eth1 - Main router) to (eth2-Flint2).
Flint2 acts as a dumb AP for Wifi Access.
Client Machines showing the issue are on Wifi connecting to the Flint2 AP.

===

I have confirmed the main router is not the problem, nor is my ISP the issue, and all Ethernet interfaces are working as intended. My issue is entirely caused by the Wireless Systems on the Flint2 not operating properly. If I connect a device via a wire direct, everything works at 1000BAST-T speeds. When I try to use Wi-Fi, instead of the Wi-Fi working as intended, I am limited to 10BAST-T speeds on Wi-Fi for some unexplained reason when just days ago I will getting 700-800 Mbps off WiFi in the 5 GHz range.

The issue I am having is with the Flint2's Wifi Systems and I have no idea what is going on or why I am all of a sudden limited to the 10 BASE-T speeds even after several reboots of the device.

[krazeh]

Have you checked the ethernet cable?

[moeller0]

Install ethtool (probably something like opkg update , opkg install ethtool) and then query both wan and lan ethernet interfaces:
ethtool eth2
ethtool eth1
post the results here...

[Oliumen]

@krazeh

Have you checked the ethernet cable?

It's fine. Just checked it. I also connected an ethernet connection from the router directly to one of the client machines and ran some tests to find they are in fact operating at 1000BASE-T so there is something wrong with the wifi connections that is causing the extremely slow speeds and I wouldn't know how to fix it.

[moeller0]

@Oliumen

so there is something wrong with the wifi connections that is causing the extremely slow speeds and I wouldn't know how to fix it.

Maybe change the title to reflect that you see issues with MT6000/flint WiFi on OpenWrt 23? I seem to recall there are already some MT6000 threads on this forum that discuss WiFi and WiFi regressions where you are more likely to find help...

[Oliumen]

@moeller0

ethtool

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 23.05.5, r24106-10cc5fcd00
 -----------------------------------------------------
root@OpenWRT:~# ethtool eth2
Settings for eth2:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        MDI-X: on (auto)
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes
root@RiseBroadband:~# ethtool eth1
Settings for eth1:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        MDI-X: on (auto)
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes
root@OpenWRT:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        MDI-X: off (auto)
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes
root@OpenWRT:~#

[Oliumen]

@moeller0

Maybe change the title to reflect that you see issues with MT6000/flint WiFi on OpenWrt 23?

Will do. Now that I know it's not the main router and is in fact the Flint2's wireless systems.

[moeller0]

Maybe re-post your question over here:

GL.iNET Flint 2 (GL-MT6000) discussions

There is an interesting article about the new upcoming GL.iNet Flint2 (also known as GL-MT6000) - a new AX6000 router based on MediaTek MT7986 (Filogic 830) Arm SoC and the vendor claims that it's supporting VPN speeds of up to 900 Mbps using WireGuard and 190 Mbps with OpenVPN. As MT7986 support is already in for devices like bpi-r3 there is just a question of time now before it gets official support in Openwrt mainline. More details here GL.iNet Flint2 AX6000 router supports up to 900 Mbps …

that seems to be the flint 2 most active thread...

[Oliumen]

Will do. Thank you.

[Pico]

Your opening post and you heading is highly confusing, as you mix up details of 2 devices and do not make it clear, which of the 2 is affected.

You should first try to narrow down your issues to 1 of the 2 devices. Then only post the description and config details of the affected device.

It feels like you want to tell, that the WAN port is affected.
If you are already sure that it is WAN port of the Dell x86, remove the details of the Flint completely, as the Flint does not influence the WAN port of your Dell x86 main router.

[Oliumen]

@Pico

Your opening post and you heading is highly confusing, as you mix up details of 2 devices and do not make it clear, which of the 2 is affected.

Apologies, I have made adjustments. Let me know if that is better and more sufficient.

[slh]

As your haswell based x86_64 router is fast enough for this (which is usually not the case with 'plastic routers'), you can install iperf3 on the router and use that (iperf3 -s) to test your wireless clients against that (removing the ISP side variances out of the picture).

[Oliumen]

I will definitely install the package for future problems that might come up.

[Oliumen]

@slh

iperf3 -s

I tried to run this on the AP and it did nothing. I have no idea how to properly use this to get any sort of proper data from it. I will have to look into it and how to properly use it.

I am at the point now where I think I am just going to reflash the AP and start from scratch. I can't get it to operate at proper bandwidth limits no matter how hard I try or what settings I swap. I have a feeling something went wrong with an SQM package or something and it's totally messed things up but the problem is I have no idea how to fix it so reflashing the AP it is. bummer

[slh]

iperf3 -s starts the 'server' instance, for your clients to connect to (and test against) via iperf3 -c <ip of server>. But again, doing this (either client- or server) on an OpenWrt device is only sensible, if the hardware is considerably faster than necessary (e.g. x86_64 or similar). In all other cases, test through the devices, with fast enough systems on either side. iperf3 is available for all major platforms, linux, xBSD, MacOS, Windows, often part of network oriented smartphone apps (among others, as part of "he.net - Network Tools"),

[Oliumen]

Thank you for that explanation. That clears things up. I will try to run an iperf3 test today before I reflash the AP.

[Oliumen]

These were the results of my iperf3 test.

[x@x ~]$ iperf3 -c 192.168.1.2
Connecting to host 192.168.1.2, port 5201
[  5] local 192.168.1.228 port 53636 connected to 192.168.1.2 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  3.50 MBytes  29.3 Mbits/sec    0    202 KBytes       
[  5]   1.00-2.00   sec  4.12 MBytes  34.6 Mbits/sec    0    358 KBytes       
[  5]   2.00-3.00   sec  3.50 MBytes  29.4 Mbits/sec    0    512 KBytes       
[  5]   3.00-4.00   sec  3.50 MBytes  29.3 Mbits/sec    0    667 KBytes       
[  5]   4.00-5.00   sec  2.75 MBytes  23.1 Mbits/sec    0    789 KBytes       
[  5]   5.00-6.00   sec  2.75 MBytes  23.1 Mbits/sec    0    902 KBytes       
[  5]   6.00-7.00   sec  2.62 MBytes  22.0 Mbits/sec    0   1.02 MBytes       
[  5]   7.00-8.00   sec  2.75 MBytes  23.1 Mbits/sec    0   1.18 MBytes       
[  5]   8.00-9.00   sec  2.75 MBytes  23.1 Mbits/sec    0   1.34 MBytes       
[  5]   9.00-10.00  sec  4.12 MBytes  34.6 Mbits/sec    0   1.49 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  32.4 MBytes  27.2 Mbits/sec    0             sender
[  5]   0.00-10.01  sec  30.1 MBytes  25.2 Mbits/sec                  receiver

iperf Done.
[x@x ~]$ 

As you can see the Flint2's Wifi speeds just aren't where they should be. I should be in the 500Mbps range at least and the device is only operating at 25Mbps at it's best. I can't for the life of me figure out what happened or why I went from the proper bandwidth figures to just 25 Mbps from one day to the next with no changes being done to the Flint2.