Flint 3 (GL-BE9300) Discussion Thread

The issue is that 5 GHz / 6 GHz is not suitable for our houses in Germany since they are pretty old with massive walls. So when I move in my house, my device might switch to 2.4 GHz sometimes - which is fine, since some network is better than no network at all. :smiling_face:

OpenWrt isn't very good at pushing a device from one band to another when the connection starts to worsen - I am not even sure if real band steering exists or if it's just a bunch of scripts... MLO makes it even worse in that case, at least in my experience.

I would love to get the Flint3 working as great as the Flint2 :frowning:
But right Wi-Fi is always a big problem with my devices and environment.

I went for few days trip. After returning home, my phone connected to MLO network - no Internet. My wife's oneplus 11,to regular 2.4/5ghz - no Internet. Until I switched off hardware acceleration. BTW when switched to software was also no Internet. But with no acceleration it seems I lose around 150mbps from ISP on download…not good…

1 Like

Is it likely that new firmware will improve the WiFi reception?

The dropout are getting frustrating!

Thanks

I have the same issue with firmware 4.8.1. My wifi died completely today and wasn’t solved until I made a restart. I hope that they release a fix for this soon.

WIFI side seems very unstable on Flint3. MLO is not working properly or at all (my support case already ongoing, but no results so far). Or dies completely, or slows down. I have feeling moving away from known and good chips to QC was a mistake.

1 Like

Seems that this move from Mediatek to QC is causing more issues than solutions. Currently my Flint 2 gives me less issues.

I hope that they release FW 4.8.3 because these issues are becoming annoying (and affecting my work daily activities to be honest). If they released a Flint 4 with Mediatek and Wifi 7 I would purchase it immediately, because these QC based routers seem without solution in the short term.

1 Like

I get good speed with Flint 3 as long as I have good signal strength (direct line of sight). The problem is that the signal strength seems to drop off very quickly as I move away, or add any obstructions. Signal strength in the next room is noticeably worse than both my AT&T router and my old TP-Link router. I wonder if it is the 2x2 MIMO that makes it worse? (TP-Link was 3×3 WiFi-5, AT&T was 4x4 WiFi-6). Come to think of it, I suspect that is the case. I never thought of this until typing out this message. I really regret buying the Flint 3 now.

1 Like

@bruce the problem was the Flint 2 :laughing: A very good and strong product (great coverage, 4x4 on every band, etc). Flint 3 sadly was a step down, even with the 6ghz. Why Flint 3e is only 4x4 on 5ghz? We hope in a Flint 4 with powerful specs like Flint 2, GL.INET can do this! :flexed_biceps::wink:

2 Likes

Here are my observation after installing a Flint 3 in place of my “old” Flint 2.

Like the Flint 2, upload rate is limited to about 600mbit if Network Acceleration is disabled, and you lose a lot of features if you enable it, like Parental Control. I don’t understand why this was acceptable to launch.

Luci is broken in many ways. There is no wireless client list. All wifi interfaces show as “disabled.” And some other bugs.

Wireguard performance is *horrible. *About 60mbit tops to my VPN server which I own. I got about 200mbit with the Flint 2.

Wifi coverage is worse than the Flint 2, not by a whole lot, but from my bedroom I see about half the speed from my phone as I did with the Flint 2.

Network File Sharing shows ERR FS even for freshly-formatted external drives, both USB sicks and USB SATA SSDs. It only works after re-partitioning and reformatting the drive for ext4 (and only ext4) from the cli in the Flint 3.

Constant PPPoE disconnects - once every hour or two, the PPPoE disconnects and has to reconnect, which takes 60-90 seconds.

All clients in the client list shown as using the VPN even when the wireguard client only has the VPN subnet allowed (manual client setup)

It’s kinda disappointing that having all of your network speed hobbles the router in so many ways, and that there are so many f/w issues still 3 months after launch.

2 Likes

I am just curious why switching to QC. Isn’t Mediatek cheaper in production cost?

I think personally they look only to supply and demand, which chips where more available present at that time.

To be honest Mediatek doesn't have alot of wifi 7 at that period.

And there is little marketing decision too, qualcomm where one of the first rolling out of the wifi 7 even when wifi 7 wasn't officially specificated yet by the wifi alliance, I think 1-2 years before it was official.

And personally I think this is exactly where alot of problems stem from with the designs of these chips and the QSDK, they may be out of spec now and have been rushing hacking it to spec.... things like MLO could have been completely wrong implemented, or on hardware level, this depend also how early a chip is, it could be worse it looks GL-iNet has choosen the middle path (they are middle adopters after wifi standard release) :slight_smile:

this is also the reason there is way more less on Mediatek chips for wifi 7, they are there but they are slowly making it through little by little, I did not see Mediatek chips around when wifi 7 was not official specified by wifi alliance.

Personally if I was in GL position I would take my time not rush a new product to keep up with the newest wifi standard, OpenWrt itself is still adding early support for wifi 7, and what I learned from it is that often something becomes stable when nearly a new version of wifi standard has been released the older becomes stable, qualcomm however is even more difficult to be official supported by OpenWrt since they dont release the firmware blobs.

But they also have consumers which want the next level experience and want to satisfy, personally I would not sacrifice it over this and rather sell stable devices and fully OpenWrt supported devices but that is my own opinion :slight_smile:

3 Likes

GL should keep their hardware OpenWRT supported and move the Dev to the GL GUI Only as a package/wrapper for Luci. Just stay up with the main branch and only have hardware that is supported by OpenWRT IMO

1 Like

@bruce There’s a new beta version for the Flint 3, and the firmware size has increased significantly — 130 MB instead of 83 MB. Do you know the reason for that?
https://fw.gl-inet.com/firmware/be9300/testing/be9300-4.8.99_beta1-808-1108-1762604729.bin

I just tested this newest beta firmware, its WireGuard VPN server doesnt work, i just reset back to v4.8.1

Disabled HW acceleration also cant get WireGuard VPN server to work.

  • Router’s GUI not showing any connected devices, even when devices shown connected to it.
  • Device connected to VPN have no internet access.

@mainufer I guess all the new features take more space :slight_smile:

3 Likes

Your complaint of constant PPPoE disconnections is a known issue from day 1.
You can avoid that with going to the Multiwan settings and at the right top go to Sensitivity Options then set Sensitivity to Customized and move the slider completely to the right.
That fixes for now the constantly disconnecting off the PPPoE connection.
Bruce from Gl.i wrote to me that they needed to fix that in the firmware.

Hello,

May I know what router model and firmware version did you use?

I did not reproduce this issue.

VPN Server, BE9300


VPN Client, SFT1200


Ping to VPN server's router LAN client from SFT1200, without issue:

Hello,

Sorry for the inconvenience!

Please email your questions to [email protected], and our technical specialist will check this. Thanks!

v4.8.99 install with keep existing configuration..

Might be useful to keep discussions about that firmware to the 4.8.99 firmware thread?

1 Like