Could you explain the VPN issue you mentioned? What exactly doesn't work with custom SSIDs?
Thanks @Miles
I'll send an email 
Like @MucFlyer, I can get my full 500/500 connection wirelessly through Flint 3 on either 5 GHz or 6 GHz. I am selecting channels and not using auto mode. Flint 2 and Flint 3 are set up the same way on the same channels. My connection at 12 meters on 6GHz is like 5.7 Gbps. Really fast. I am not using MLO as it is buggy.
1 Like
Agree. And some compiler errors.
Hi Bruce, which AdGuard version is running on the Flint3? Is this the right ARM64 version?
Please refer to [Script] Update AdGuard Home
@bruce, I am not using the script and transfer the binary myself. The question is: Which version is the correct one? @admon, can you answer this question?
Sorry, I only support my own script - not direct transfer of the binaries.
The related dependencies have been uploaded to the repo, available to v4.7.11, please try to install ddns one more time.
It is working now fine.
ChatGPT says: The file AdGuardHome is an ELF 32-bit LSB executable for the ARM architecture (specifically: ARM EABI5). This means it is intended for devices with a 32-bit ARM processor, such as:
- Older Raspberry Pi models (e.g., Pi 2 or Pi 3 running a 32-bit OS),
- ARM-based routers or NAS devices,
- Embedded Linux systems with 32-bit ARM CPUs.
Yes, that's correct — this binary is intended for the following ARM platforms:
- ARMv5: generally compatible, since it uses EABI5, though many modern tools expect at least ARMv6.
- ARMv6: fully compatible (e.g., Raspberry Pi 1).
- ARMv7: also compatible (e.g., Raspberry Pi 2 and 3 running a 32-bit OS).
@bruce, this means the Flint 3, who has a 64Bit CPU, uses a 32Bit AdGuardHome application?
You should have asked to Chat GPT how to identify the architecture of the system.
Type "uname -m"
Well, I've uploaded the binary, and this was the result:
import subprocess
# Check the file type of the uploaded binary
file_path = "/mnt/data/AdGuardHome"
file_info = subprocess.run(["file", file_path], capture_output=True, text=True)
file_info.stdout.strip()
Result:'/mnt/data/AdGuardHome: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked,
What happened to the MAC Clone option? It was under Network > MAC Clone and was very handy specially when travelling and staying at hotels. I just received the Flint 3 and I can't find it anywhere.
Since v4.6 firmware, this page has been removed, and the MAC address settings for Ethernet and repeater interfaces have been migrated to the corresponding sections on the INTERNET page.
Ethernet - GL.iNet Router Docs 4
Repeater - GL.iNet Router Docs 4
I received my Flint 3 a few days ago, and been playing a bit with it, but noticed some strange behaviour with mine, hopefully im not the only one, and maybe someone knows how to fix it.
So enabling the MLO band, download / upload speeds are slower, much slower than just simply using WiFi 6 instead and its only a couple of things that use it like my Pixel 9 Pro and my Mrs Iphone 15 Pro max, so its not like its maxed out or anything, so I disabled MLO and use WiFi 6 instead, I wonder if the beta testers actually picked up on any of this ?, seems like rather than combining the 3 networks, its using only either the 2.4, 5 or 6ghz bands of its own choice.
Now onto the WiFi 6ghz settings, it was running fine at 320mhz, but as soon as I plugged in my external hard drive which I kind of use as a NAS, the 6ghz channel dropped off, I tried everything to get it back and nothing worked, tried changing channels, didn't work, the only thing that works for the 6ghz channel now is 160mhz and channel 5, if I choose any other channel it doesnt appear in available networks, if I unplug my external hard drive, everything is back to normal how it was in the beginning.
When I was testing MLO (not on the Flint 3, Slate 7), this is exactly what I noticed, the client picks on one ghz and stays on it, this is what I noticed on a non wifi 7 device (so I don't know if MLO also does something if the client actually supports it), it looks more like a box in where the box advertises with: I have AC,N,AX, BE choose your pick, and where the client picks one and likely works on clients decisions in where it can change which mean some devices won't.
I don't think it is supposed to work similar like mtcp with multiple flows and then on different bands what I initially thought to be, although the tech looks advertising this for wifi7.
in my case I wasn't much fan of MLO, I saw it as a downgrade against 5ghz, but I yet have to understand if clients also can have MLO features as wifi 7 device.
MLO is a mess, the historical reason is device manufacturers started shipping WIFI7 devices before IEEE finalized the standard, as a result routers have to support every single slightly different MLO protocol each brand implemented.
No router has fully solved this issue yet, IEEE mitigated this issue in WIFI8, but WIFI7 MLO might never be fully functional.
2 Likes
Agree. MLO does not work well on any brand router I have either.
1 Like