GL.iNET Flint 2 (GL-MT6000) discussions

lol :rofl:
the things with 5g cellular sim slot are real costly

I was expecting some router with 5g cellular,
out of the oblivion here comes Flint 2 which has pretty good flagship configuration maybe I will do RNDIS for 5G

Wi-Fi 7 coming soon, is this router future proof for broadcasting 6ghz AP?

Hello,
just received my 99ā‚¬ flint2 to be setup as AP, so i flashed a 23.05.5 image and i have a question on switch/ports/vlan
I come from a R7800 that had a wonderful "switch" interface under network that the flint has not. Am i missin any luci packet?
Also, the R7800 in interfaces - devices had eth0-eth1 and basically i could assign ports (including WAN) to either one or the other CPU interface and assign one by one VLAN to ports.
Should with the FLINT2 i manage each port one by one?
Now i have 5 lanN ports, eth1 that i assume to be WAN and eth0 that.. i don't know what it is :slight_smile:

I also have today fear: using VLAN is not impacting on hardware offloading, right?
Thanks

when there is a switch button the switch is swconfig, flint 2 uses DSA (destributed switch architecture).

If you navigate to luci -> network -> interfaces click on the tab devices.

Then click on edit for br-lan, then click on the bridge vlan filtering tab.

Basicly its moved and works a little different than with swconfig :+1:

2 Likes

oh, nice, i was wondering if this was a matter of DSA :slight_smile:
can you help me understanding ETH0 and ETH1?

jup eth0 is the cpu switch, usually with dsa you don't want to touch this.

Wan is eth1, also the extra 2.5gb port turns into a lan1 or lan4. Im not sure but you don't have to worry about eth1 turning into a lan interface :slight_smile:

just found full answer here

let's see how badly i can break things :smiley:
thanks

1 Like

The MT6000 is WiFi 6. That means it can only access 5GHz frequencies, not the 6GHz frequencies available to 6E and 7 devices.

GL-iNet have stated plans or desires to release a WiFi 7 router by the end of 2024.

1 Like

I would reommend:
DSA mini Tutorial
https://openwrt.org/docs/guide-user/network/dsa/dsa-mini-tutorial#dsa_mini-tutorial

2 Likes

damn this thing is fast, compared to my old R7800..
is it correct while using it as AP that i have some tasks running like these?

  872     2 root     RW       0   0%  10% [napi/phy0-12]
  880     2 root     RW       0   0%  10% [mt76-tx phy0]

Yes. They handle network traffic going through phy0 which is WiFi 2.4 GHz.

very strange, since i was doing a speedtest over 5G
i mean, i see it's 2.4G but i was using 5G (i have only IOT devices on 2.4G)

I tested myself and I see the same result. I guess these process names have different phy-numbers than what hostapd uses for its purposes.

coherence and transparency are all :slight_smile:

Is it possible to run snort3 on this router? Would this be affected by Hardware Flow offloading?
Which performance could I expect?

Snort3 is fairly CPU/RAM heavy, the doc page recommends up to 1GB RAM so we are good there, there is an ARM build so good there, and Filogic 830 is fairly performant so good there too. You could also run it in a Docker container, but that gets fairly complex. Guide here is: https://openwrt.org/docs/guide-user/services/snort

edit: to answer your questions Yes, and Yes leave HFO off for that :slight_smile:

1 Like

I will give it a try

@pattagghiu yes DSA comes from upstream Linux and is nearly project-wide for OpenWrt now. There are a few exceptions of old holdovers of swconfig such as ipq806x like your former device. Regarding mt76-tx, yes you want that it's your wireless driver.

@nitinjs there is no 6GHz radio on this device that should be clear from the specs. Filogic 880 devices with WiFi 7 should start trickling out next year (or maybe Q4 as others said) but don't expect full OpenWrt support for a bit longer. MediaTek has a way to go with mt76 drivers supporting it too. BPi-R4 is the first so far.

thanks!
quite confused i have to basically create a bridge with ALL lan ports, like if it's the old switch... and then link bridge.vlan to interfaces.
at the end of the day, it's MORE OR LESS the same :slight_smile:
i assume i do not need to create bridges when i use vlan on single lan ports (e.g. WAN)