New firmware version 4.8 being released for beta testing

[Nomax2000]

There is a new and first 4.8.1 for the Slate 7

[azleatherneck]

Ever tried getting mwan and pbr working together…. THIS is why I wait for their firmware. Nobody else has a multiwan setup that works well with PBR Split tunnels and if you have ever attempted it yourself. I promise you never got it right or you would be makeing money

[buntspext]

@Renato

I just upgraded my GL-MT3000 (Beryl AX) to 4.8.0-op24 (25/07/2025) and this firmware is completely broken.

Same here on my Beryl MT3000

[aranmor]

Is 4.8 coming out for Mudi?

[lama]

Hi? I want to give feedback on current latest 4.8 build for Flint Ax1800

1. I don’t Like that after Manually entering Client devices to LAN’s reserved IP, New client names, IP etc are Not showed up under Clients page (offline or online).

2. On Clients page, there is No toggle switch to TurnOn or TurnOff WAN, LAN, Changing IP by simply clicking parts of IP address (after Reserve is On)

3. I hate that you guys are Not coding Pop-up option on MouseOver for desktop browsers

[mainufer]

@teleney Hi, I could now replicate the problem. When I upgrade from a previous version, in my case 4.6.6 and open then open my router IP 192.168.5.1, it goes straight to OpenWRT GUI:
config uhttpd 'main'
option redirect_https '0'
option home '/www'
option rfc1918_filter '0'
option max_requests '3'
option max_connections '100'
option cert '/etc/uhttpd.crt'
option key '/etc/uhttpd.key'
option cgi_prefix '/cgi-bin'
list lua_prefix '/cgi-bin/luci=/usr/lib/lua/luci/sgi/uhttpd.lua'
option script_timeout '60'
option network_timeout '30'
option http_keepalive '20'
option tcp_keepalive '1'
option ubus_prefix '/ubus'
list ucode_prefix '/cgi-bin/luci=/usr/share/ucode/luci/uhttpd.uc'
option inited '1'
list listen_http '0.0.0.0:80 ['
list listen_https '0.0.0.0:443 ['

config cert 'defaults'
option days '397'
option key_type 'ec'
option bits '2048'
option ec_curve 'P-256'
option country 'ZZ'
option state 'Somewhere'
option location 'Unknown'
option commonname 'OpenWrt'

root@GL-MT6000:~# cat /tmp/log/nginx/error.log
2025/08/01 15:14:21 [emerg] 9164#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:14:21 [emerg] 9164#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:14:21 [emerg] 9164#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:14:21 [emerg] 9164#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:14:21 [emerg] 9164#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:14:21 [emerg] 9164#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:14:21 [emerg] 9164#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:14:21 [emerg] 9164#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:14:21 [emerg] 9164#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:14:21 [emerg] 9164#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:14:21 [emerg] 9164#0: still could not bind()
2025/08/01 15:15:13 [emerg] 12626#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:13 [emerg] 12626#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:13 [emerg] 12626#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:13 [emerg] 12626#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:13 [emerg] 12626#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:13 [emerg] 12626#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:13 [emerg] 12626#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:13 [emerg] 12626#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:13 [emerg] 12626#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:13 [emerg] 12626#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:13 [emerg] 12626#0: still could not bind()
2025/08/01 15:15:21 [emerg] 13071#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:21 [emerg] 13071#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:21 [emerg] 13071#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:21 [emerg] 13071#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:21 [emerg] 13071#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:21 [emerg] 13071#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:21 [emerg] 13071#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:21 [emerg] 13071#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:21 [emerg] 13071#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:21 [emerg] 13071#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:21 [emerg] 13071#0: still could not bind()
2025/08/01 15:15:29 [emerg] 13485#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:29 [emerg] 13485#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:29 [emerg] 13485#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:29 [emerg] 13485#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:29 [emerg] 13485#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:29 [emerg] 13485#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:29 [emerg] 13485#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:29 [emerg] 13485#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:29 [emerg] 13485#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:29 [emerg] 13485#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:29 [emerg] 13485#0: still could not bind()
2025/08/01 15:15:36 [emerg] 13634#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:36 [emerg] 13634#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:36 [emerg] 13634#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:36 [emerg] 13634#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:36 [emerg] 13634#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:36 [emerg] 13634#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:36 [emerg] 13634#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:36 [emerg] 13634#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:36 [emerg] 13634#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:36 [emerg] 13634#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:36 [emerg] 13634#0: still could not bind()
2025/08/01 15:15:44 [emerg] 13703#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:44 [emerg] 13703#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:44 [emerg] 13703#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:44 [emerg] 13703#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:44 [emerg] 13703#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:44 [emerg] 13703#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:44 [emerg] 13703#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:44 [emerg] 13703#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:44 [emerg] 13703#0: bind() to 0.0.0.0:80 failed (98: Address in use)
2025/08/01 15:15:44 [emerg] 13703#0: bind() to 0.0.0.0:443 failed (98: Address in use)
2025/08/01 15:15:44 [emerg] 13703#0: still could not bind()

root@GL-MT6000:~# ps | grep nginx
16504 root 1340 S grep nginx

[bruce]

Hello,

Thanks for your feedback.

We have reproduced this issue, and the R&D team is being fix.
I think it will be improved in the next version release.

[bruce]

Hi,

Thanks for your feedback.

1. New client names have taken effect, BUT IP will take effect in the next connection of this client, like say that is DHCP renew.
   

   
   
   
   
   
   
   

2. I think this is a good suggestion, will collect it to the PM team for evaluation.

3. Are there any specific suggestions for the operation logic of the UI part?
   Considering that the desktop should have a mouse, the mouse click is equivalent to confirming the action, avoiding misoperation.
   

[bruce]

I think the performance of Mudi v2 may not be able to support SDK v4.8

[DaWeav]

@bruce

Hi,

The v4.8 firmware will remain in beta version for testing in a while.

At present, there may be some changes in the GUI. We may release multiple beta version firmware during these months.

I assume (not sure) in the end of Q3 may be the v4.8 converted to stable.

@bruce Since the non-OPT24 4.8 version firmware has been released for the Beryl AX already, would it be safe to say that the non-OPT24 4.8 Beta firmware version for the Flint 2 is stable to use now too while we wait for some potential GUI changes pending?

[darkdevil]

Hello, how can i download again this firmware as its removed, this beta was perfect for my router not hicups no lags no reboots in 90 days, however yesterday i updated to stable and now on every command router breaks and i need to factory reset him. Anyone can give me download for this beta firmware to re-flash my router (Beryl AX) i would be grateful. Thank you

[mainufer]

Which version number?

[ikun]

@darkdevil

every command router breaks

Could you tell me what you mean by "on every command router breaks"? What issues are you observing?Thanks!

[darkdevil]

@ikun

on every command router breaks

I mean if i wanted to change lan from 192.168.* to lets say 10.0* it would break and wont come back till factory reset, also for guest networks.. Turning on VPN was blocking the router and needed to factory reset, the 1st time I installed stable it broke on setting cloudflare as encrypted dns.. I reflashed now to OpenWrt 21.02-SNAPSHOT and so far in this 2 days i don't have any problem, its working similar like before update to stable.

[darkdevil]

@mainufer

Which version number?

I don't remember for sure, but i know it was in late April and you could set less than 10 chars for pass also.. with latest firmwares that is not option now it asks for 10 chars... i Think it was beta3 when you go in System Overview..

[bruce]

Flint2's v4.8.0 stable version is probably expected to be released in Q3 2025.

If it is a formal/business environment, it is recommended to wait for a while to upgrade the table v4.8.x firmware.

If using for personal, you can upgrade to v4.8.x beta early for experience.
I think the current version (even beta) is definitely more perfect than the earlier.

[azleatherneck]

@bruce Do you have a target release on the opo version? Quarterly/Bi-Annual? It’s been running GREAT but I am seeing a lot of polish you guys are doing in the 4.8 code and I am hoping the opo doesn’t get left behind

[bruce]

Do you refer to op24 firmware?

@azleatherneck

opo version

If yes, it is generally updated with GL SDK large versions, such as 4.8.0/4.9.0(or 4.8.5/4.9.5), which is usually updated every six months.

[mlorda]

Any news , no date for 4.8 Beta MT2500 available?

[danielg]

I think I found a bug concerning same server setups as multiple tunnels. I set up a VPN server for use by specific devices with priority 1 and kill switch enabled and the same VPN server as priority 2 for use for "all devices" (meaning all other devices without specifying them, in my understanding) with specific domain exclusions. The effect is that the devices affected by the priority 1 tunnel cannot access the internet while for the devices affected by the priority 2 tunnel everything works as expected. When I assign two different servers to each tunnel, both tunnels work as expected. So I guess I could just solve the issue that way, but isn't performance reduced by connecting to more than one VPN at the same time?