Will it be released for E750v2? I need camouflage mode critically. Especially for travel (!) router
Logs provided in DM as requested.
Note: the 5ghz Wifi network I am repeating is a hidden network, if that makes a difference.
regarding the 5GHz WiFi issue, is there no disconnection?
GL firmware support connects to NordVPN through WireGuard, and what function is not implemented?
With WiFi 5GHZ you no longer have to forego other connection settings. Slower 2.4GHZ and Slower USB.
Due to the connection drops, I spoke to Nordvpn and they told me that they don't offer any wireguard for routers at all.
This is still under development and is not yet available for routers.
If you look at the German servers on the router, for example, there are different servers there that pay for Berlin, but the config files are all the same.
These are two different things: NordLynx is an obfuscation that NordVPN build on top of wireguard. NordLynx is not open-source and at the moment only available within NordVPN apps. The "standard" wireguard is open-source and implemented in glinet devices (and many more).
1 Like
Hello,
Update:
After reproducing this issue, it is submitted to R&D.
R&D checks the MTK closed-source driver, he said when the WiFi of the MT3000 is turned off, the ra interface will be disabled, resulting in the repeater being unable to scan/connect to the hidden SSID after the router is restarted (or not restarted and the wireless driver is reinitialized).
The reason is that to scan the hidden SSID, it must start the ra interface (i.e., MT3000 WiFi) to receive the reply messages from hidden SSID.
This issue is related MTK closed-source driver, and we have feedback to MTK to see if it can be improved.
I have tested op24-4.7.0 (open-source driver) and this issue does not exist.
In your usage scenario, please install op24-4.7.0 firmware.
3 Likes
Will there be an update to the op24 Version anytime soon?
5 Likes
It is clear to me that Nordlynx and Wireguard 2 are different things. I didn't ask about Nordlynx either, but specifically about Wireguard and was told several times that it wasn't currently for routers.
It's also funny that, for example, in Germany on the Flint 2 / 20 Berlin, different servers are displayed but they are all identical in the config file.
You could have just shown 1
I encounter problems with dnscrypt, when I set it up it goes for sometimes but then suddendly usually after a restart of the router this happen:
Sat Mar 1 21:53:52 2025 daemon.notice procd: /etc/rc.d/S18dnscrypt-proxy-vpn: mkdir: can't create directory '/etc/dnscrypt-proxy2-vpn/': File exists
Sat Mar 1 21:53:54 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:53:54] [NOTICE] dnscrypt-proxy 2.1.5
Sat Mar 1 21:53:54 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:53:54] [NOTICE] dnscrypt-proxy 2.1.5
Sat Mar 1 21:53:54 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:53:54] [NOTICE] Network not available yet -- waiting...
Sat Mar 1 21:53:54 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:53:54] [NOTICE] Network not available yet -- waiting...
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:02] [NOTICE] Network connectivity detected
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:02] [NOTICE] Now listening to 127.0.0.1:5453 [UDP]
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:02] [NOTICE] Now listening to 127.0.0.1:5453 [TCP]
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:02] [NOTICE] Network connectivity detected
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:02] [NOTICE] Now listening to 127.0.0.1:5454 [UDP]
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:02] [NOTICE] Now listening to 127.0.0.1:5454 [TCP]
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:02] [NOTICE] Service is not usable yet
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:02] [NOTICE] Resolving server host [download.dnscrypt.info] using bootstrap resolvers over udp
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:02] [NOTICE] Source [odoh-servers] loaded
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:02] [NOTICE] Source [public-resolvers] loaded
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:02] [NOTICE] Source [relays] loaded
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:02] [NOTICE] Firefox workaround initialized
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:02] [NOTICE] Loading the set of blocking rules from [blocked-names.txt]
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:02] [NOTICE] Source [public-resolvers] loaded
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:02] [NOTICE] Service is not usable yet
Sat Mar 1 21:54:02 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:02] [NOTICE] Resolving server host [ipv6.download.dnscrypt.info] using bootstrap resolvers over udp
Sat Mar 1 21:54:03 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:03] [NOTICE] Source [relays] loaded
Sat Mar 1 21:54:03 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:03] [NOTICE] Service is not usable yet
Sat Mar 1 21:54:03 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:03] [NOTICE] Resolving server host [raw.githubusercontent.com] using bootstrap resolvers over udp
Sat Mar 1 21:54:03 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:03] [NOTICE] Source [odoh-servers] loaded
Sat Mar 1 21:54:03 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:03] [NOTICE] Firefox workaround initialized
Sat Mar 1 21:54:03 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:03] [NOTICE] Loading the set of blocking rules from [blocked-names.txt]
Sat Mar 1 21:54:08 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:08] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:54:08 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:08] [ERROR] No useable certificate found
Sat Mar 1 21:54:08 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:08] [NOTICE] dnscrypt-proxy is waiting for at least one server to be reachable
Sat Mar 1 21:54:09 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:09] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:54:09 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:09] [ERROR] No useable certificate found
Sat Mar 1 21:54:09 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:09] [NOTICE] dnscrypt-proxy is waiting for at least one server to be reachable
Sat Mar 1 21:54:24 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:24] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:54:25 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:25] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:54:39 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:39] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:54:40 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:40] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:54:55 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:54:55] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:54:56 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:54:56] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:55:11 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:55:11] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:55:12 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:55:12] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:55:27 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:55:27] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:55:28 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:55:28] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:55:42 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:55:42] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:55:43 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:55:43] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:55:58 2025 daemon.err dnscrypt-proxy[2620]: [2025-03-01 21:55:58] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
Sat Mar 1 21:55:58 2025 daemon.err dnscrypt-proxy[2636]: [2025-03-01 21:55:58] [NOTICE] [dnscry.pt-milan-ipv4] TIMEOUT
No dns is then available anymore of the 8 I selected, it seems it is losing something....like the certificates of the servers!
This is a AXT1800 slate ax, 4.7.0 RC1
selected dns are:
server_names = ["dnscry.pt-london-ipv4","dnscry.pt-madrid-ipv4","dnscry.pt-paris-ipv4","dnscry.pt-frankfurt-ipv4","dnscry.pt-geneva-ipv4","dnscry.pt-lisbon-ipv4","dnscry.pt-munich-ipv4","dnscry.pt-milan-ipv4"]
Hi Bruce,
I have seen multiple scenarios where MTK falls short in terms of compatibility, and the common response from support or beta managers is to use the OP24 image instead. Given this, I would like to understand the tangible, real-world advantages of the MTK channel right now compared to OP24.
Specifically, what measurable performance gains does MTK provide over OP24? Additionally, aside from increased support focus that MTK seems to have, what are the key benefits of MTK that justify its use despite its apparent compatibility issues?
Your insights would be greatly appreciated.
5 Likes
Please refer to:
Good point.
Maybe it should be better to change the prioritization from closed source as primary to Op24?
5 Likes
This is deeply concerning. While the final decision rests with GL.iNet, I feel they are failing to uphold their own commitment:
[GL.INET] will provide a synchronized Native OpenWrt version labeled 4.x.x-opxx, based on the OpenWrt main branch with kernel version 6.6.x.
If beta, RC, and release versions are not synchronized, then what is? As a customer, it is incredibly frustrating and confusing to determine what is actually supported. Worse yet, I have been explicitly told that to use features that were advertised for the product, I must use the op24 build. This raises serious questions.
3 Likes
Just to understand, to avoid wasting my time installing an wrong firmware:
-
Which version is the priority for GL-iNet? MTK Closed source or Open source (based on OpenWRT 24.10)?
-
Is there any plan to move to OpenWRT 24.10 (Stable, instead of 24.10-rc2)?
1 Like
It would make sense to go from OP 24.10 rc2 to OP 24.10 final or even 24.10.1 (end of March is my hunch).
Please GL-iNet, can you work on OP24 soon. I'd like to test this out as I'm using an older +6 months, but stable version of your FW at the moment.
3 Likes
What a mess..... and it gets only messier... What makes it so difficult to manage these firmwares "things" ?
1 Like
It's just a router! Use the version which works for you 
Traffic statistics are based on the card slot.
If you change different cards to access the Internet, it unable to accurately count the traffic usage of specified card.
Please clear the traffic usage before changing the card.
Hi,
do I have access to luci's advanced mode with 4.7.4 where I can activate fast transition?
That would be true if I had more than 1 SIM card to swap around 
I only use 1 SIM card in 1 slot ever so your explanation doesn't quite make sense to my situation.
Is there anything you'd like me to test?