Flint (GL.iNet) sketchy/deceiving behaviour

[Deleted member 115599]

U

 

[vlord]

This is almost a word for word copy of this post on Reddit and I responded there, so I’ll respond the same here as well:

Due to the embargo, many of us have had to stay silent but there is a lot of factually incorrect information in this thread.

1. This is a highly capable 64bit processor that supports hardware acceleration for encryption. Unfortunately the kernel, as of now, does not include NEON support that is compatible with the Wireguard version installed but engineering is aware and hope to have it enabled in a future release. This should double Wireguard speeds from 680Mbit/460Mbit. Good news is that kernel support for AES/SHA1/SHA2 is already enabled and OpenVPN speeds are astronomical. In my testing I was able to consistently get around 1448Mbit/609Mbit.
2. 10G Aggregated "Lie" -- This is a fair point but it's marketed similar to how every other manufacturer markets their routers
3. 2x2 vs 4x4 streams that Flint 2 supports. Another fair point but this is really only valid when there are 8+ clients simultaneously transmitting high amounts of data on 5 & 6GHz.
4. "Wifi 7 Pitfalls" - This argument is ridiculous. It's a Wifi 7 router. It's like saying 2.4GHz is better because of the better distance it has over 5GHz. 6GHz has a specific use case of 10m or less and is definitely less crowded than 5GHz - 160MHz. If you need max speed, 6GHz -160/320MHz is the future.
5. "FAN Noise!" - Another ridiculous argument. I've stressed this router to the limit (100% CPU utilization for 30+ mins with a load average of 5.25 and a surface temp of 113* F and there is barely a whisper of the fan.

 

[Tech9]

this CPU can't handle the actual throughput

No home router CPU can handle the advertised port speed throughput. NAT acceleration only, eventually.

It's looking like a step back to 2x2

Tri-band 2-stream radios are quite common for Wi-Fi 7 low/mid level products. At this price point - expected.

 

[sfx2000]

flint3 is complicated - not in a position at the moment as I'm just getting a first look at it as a qualcommbe target for openwrt...

currently, the gl-inet build is running on QSDK, which is a good place to start...