Release Asuswrt-Merlin 3004.388.8_2 is now available

[Kees17760]

I've set them both to "notice", which keeps the log pretty clean for days on a row.
But it's your party

 

[Makaveli]

Those are the right speeds - 2Gbps down, 200Mbps up. It's still the old coax/cable system here - still got the old XB7 modem. No fibre in our area at all for either Rogers or Bell. This must be DOCSIS 4.0 then I'd guess? They've been promoting "higher" upload speeds in our area recently.

There was an offer on my Rogers account for a bundle of Rogers Pro 2G Internet, Rogers Ultimate TV and Rogers Home Phone for $185/month, which was like $10/month less than I was already paying for the 1.5G service and all the same stuff so I "upgraded" to it, save $10/month and get the better upload speeds.

you are on docsis 3.1 with rogers going mid split for the increase in uploads. That is not docsis 4.0 the only north american providers that have it are comcast and I think that is still in a testing phase.

It’s DOCSIS 3.1
Companies started upgrading equipment last year in the US and I presume Canada.
Standard has been available for many years with modems available 5+ years ago… but internet companies are slooow.

Rogers has been on Docsis 3.1 since I think 2016 or 2018 but only on the download site upload was 3.0 and yes they are slow because they are trying to squeeze as much as they can out of the old systems.

Nice. Was not sure if DOCSIS 3.1 supported those speeds but a quick google says it does. Support for up to 10Gbps downstream and 1Gbps upstream. Let's GO! I know Rogers has been testing DOCSIS 4.0... but that would likely need a new modem on my end as well.

And yes, these companies move at a glacier pace when it comes to upgrades.

That 10Gbps down and 1 Gbps up is to the node.

 

[M75]

I'm happy to use 388.8_2 without the ROG. Started with 388.8 without ROG and never look back to ROG.

 

[Igor]

Release - Asuswrt-Merlin 3004.388.8_2 is now available

Asuswrt-Merlin 3004.388.8 is now available for supported Wifi 6 models. This release implements a new VPN killswitch method, and fixes a number of issues. July 31st: 3004.388.8_2 is now available. Changes since 3004.388.8: 3004.388.8_2 (31-July-2024) - UPDATED: OpenVPN to 2.6.12. -...

www.snbforums.com

fixed. Thanks!

 

[Unetwork]

Hello everyone,

After the second day with version 388.8_2 (clean installation on an AX88U) I get a ton of messages in the logs like below. I've never had this type of message before.

PS : After rebooting the router, these strange lines disappeared... Strange.

I don't know if @RMerlin can look at this problem or another forum member :

Aug 5 09:25:22 wlceventd: wlceventd_validate_message(249): subtype: event
Aug 5 09:25:22 wlceventd: wlceventd_proc_event(752): eth6: Probe-req from 50:XX:XX:XX:XX
Aug 5 09:25:22 wlceventd: dump_data(277): dump data (86) 40 00 00 00 FF FF FF FF FF FF 50 XX XX XX XX D6 FF FF FF FF FF FF...
Aug 5 09:25:22 wlceventd: wlceventd_proc_socket(997): Done Local Event
Aug 5 09:25:22 wlceventd: wlceventd_proc_socket(993): Recv Local event: 176
Aug 5 09:25:22 wlceventd: wlceventd_proc_event(616): recved 176 bytes from eventfd, ifname: eth6
Aug 5 09:25:22 wlceventd: wlceventd_validate_message(249): subtype: event
Aug 5 09:25:22 wlceventd: wlceventd_proc_event(752): eth6: Probe-req from 50:XX:XX:XX:XX
Aug 5 09:25:22 wlceventd: dump_data(277): dump data (86) 40 00 00 00 FF FF FF FF FF FF 50 XX XX XX XX D6 FF FF FF FF FF FF...
Aug 5 09:25:22 wlceventd: wlceventd_proc_socket(997): Done Local Event
Aug 5 09:25:22 wlceventd: wlceventd_proc_socket(978): No event
Aug 5 09:25:22 wlceventd: main(1246): ticks: 234286
Aug 5 09:25:23 wlceventd: wlceventd_proc_socket(993): Recv Local event: 226
Aug 5 09:25:23 wlceventd: wlceventd_proc_event(616): recved 226 bytes from eventfd, ifname: eth6

 

[marcd5123]

Hi guys question please...I've just updated my RT-AX86U Pro with a complete "clean" install non-dirty upgrade and have possibly some very interesting results to report back but later in the week giving it a bit of time to settle in...

With this 2nd firmware update rolled out now 8_2 do we have a rough idea time table wise to when we are likely to see MerlinWRT move over to MerlinWRT ART 5.0 (ASUS WRT 5) will this be end of 2024 Xmas Time or perhaps January 2025 looking ahead.

Lastly will this very likely be the very last major firmware update we see for 2024 based on AsusWRT 4 ??

Many Thanks as always .

@RMerlin

 

[Analog-1]

With this 2nd firmware update rolled out now 8_2 do we have a rough idea time table wise to when we are likely to see MerlinWRT move over to MerlinWRT ART 5.0 (ASUS WRT 5) will this be end of 2024 Xmas Time or perhaps January 2025 looking ahead.

Merlin has already moved over to Asus 5.0 but only for 2 BE models no other models are supported at this time. Good luck getting a answer on time lines, it's frowned upon here to even ask and often leads to being flamed.

 

[marcd5123]

Merlin has already moved over to Asus 5.0 but only for 2 BE models no other models are supported at this time. Good luck getting a answer on time lines, it's frowned upon here to even ask and often leads to being flamed.

Hi Thanks for the reply it's Very much appreciated.

Well that is definitely not my intention to cause so called "flamed" or to be frowned upon ..

It was more just an enquiry that's all .

I did see their was a mention several weeks back on one of the threads were he did briefly state what was likely to be happening moving forwards kinda timetable as such. Yes I understand their are a few of the newer models that being the "BE" WiFi 7 models that already have the newer AsusWRT 5 aka MerlinWRT 5 installed.

I like everyone else here are incredibly grateful to and very happy with everything that he has done so far so thank you very much Mr.Merlin indeed for all the hard work @RMerlin .

Much appreciated.

 

[Damit1]

LET'S GO!

 

[thatdoodle]

Both @thatdoodle and you need to be more precise about how you've configured NGINX, and where it's running. Don't assume we should just know. It could be on the router, or internally on the LAN. It could be a proxy, or reverse proxy. It could be bound to the WAN, the LAN, or BOTH. Without such details, it's difficult to provide accurate answers or address your concerns.

My assumption w/ @thatdoodle was that he was running NGINX on the router and wanted it bound to the LAN (port 80), which is in conflict w/ the GUI. So he changed the GUI's LAN port to something else (e.g., 8080). And while that solved the problem, it came at the unexpected expense of having the GUI now running on the new port w/ HTTP, when he had specifically requested only HTTPS for the LAN authentication!

That's why I consider it a bug. Had he never needed port 80 for NGINX and simply wanted to limit LAN authentication to HTTPS, the router would NOT have bound the GUI to HTTP/80.

Now when it comes to the WAN side, the GUI is never bound to the WAN. If you enable remote access, then HTTPS is required and a port is opened (8443 by default, although you can change it), where the inbound traffic is redirected (via DNAT) to the GUI on the LAN side (port 80 by default, for http, or 8443, for https, unless you changed these for some reason).

In short, unless you're replicating @thatdoodle's configuration, there shouldn't be any issues w/ port forwarding or opening ports 80/443 on the WAN. At least NOT as far as the GUI is concerned (I can't speak to other services that might also find those same ports appealing, e.g., AiCloud).

For the clarity of other users, @eibgrad was correct in his assumptions. I run NGINX directly on my router as a reverse proxy, binding 80 specifically to redirect requests to 443 and force https.

@Jeffrey Young

For my use case, yes I have (and soon plan on again) run NGINX on the router as a reverse proxy to two web services (family Nextoud server and a website for our local Catholic church group) inside my LAN. As such, my interest is to ensure I can bind NGINX to port 80 and 443 on the WAN.

From the description above, it sounded like the issue was on the LAN side. I was just wanting to confirm my suspicions.

While the gui is unavailable over WAN, httpd does bind to all interfaces and so unless you change the port you'll be unable to start NGINX unless you bind to 443 only or move the http webgui port. I am currently unaware of a way to persistently configure httpd binds on these routers, but then again I also haven't spent any time looking into it... your options are rebinding the webgui http port, ignoring http requests on nginx and using something like cloudflare tunnels to force https, or (if possible) binding httpd to specific interfaces instead of 0.0.0.0:* and :::*

On the one hand, the OP has requested only HTTPS on the LAN side, yet HTTP has been made available over the new port. Then again, the LAN side is usually a trusted network. Then again, if the OP is trying to force the LAN clients through the NGINX proxy, it undermines his efforts.

So technically, I suppose it's a failure of security, but just how much of a failure it represents depends on the OP's intentions and security requirements.

I agree this is a very small security risk and I wasn't particularly concerned, it's just strange behaviour that I thought was worth reporting. As @eibgrad alluded to, any potential attack would need the LAN to be compromised, at which point I'm not too concerned about httpd having two ports bound instead of one.... I still think it is worth fixing if possible. There are a significant number of Merlin users who aren't system/network admins and would be unable to appropriately judge the risks involved, if they were even aware of where and what to look for in the first place.

 

[octopus]

Just a thought if it is possible a simple request:
Is it possible to have same status as vpn client have in wireguard client.

Se pictures:

@RMerlin

 

[welim]

When authentication set to BOTH instead of default http on a aimesh AP main node , one cannot access remote aimesh node. You have to set authentification to http before you can access Aimesh node.

Also, when Aimesh node led set to off, if there is a power cycle, the led will light up again despite the GUI indicating it’s set to off. This happen on the Aimesh node but not the Aimesh main router though.

 

[welim]

When authentication set to BOTH instead of default http on a aimesh AP main node , one cannot access remote aimesh node. You have to set authentification to http before you can access Aimesh node.

Also, when Aimesh node led set to off, if there is a power cycle, the led will light up again despite the GUI indicating it’s set to off. This happen on the Aimesh node but not the Aimesh main router though.

Can see the details reported here:-

AX86U Pro AIMESH router in AUTHENTIFICATION METHOD set to http & https will not able to access remote AIMESH node

Dear All, My AIMESH router is AX86U-PRO and my AIMESH node is AX11000. Recently after the merlin firmware update to the 388.8.0 , I found something weird. My authentication method is setup to be both http/https (Administration->System->Authentication Method -> BOTH) 1. When I click upload...

www.snbforums.com

 

[cptnoblivious]

No issues on AX58 upgrading from 388.8 to 388.8_2. Running now to check stability before upgrading the AX68.

 

[webjunk78230]

Greetings - I have been using the Merlin RT-AX58U firmware on my RT-AX3000 v1 non-ROG for years without any problem. However, when I upgraded to 388.8 (from 388.7) I lost internet WAN connection. I can reach the router just fine and the manual fw upgrade completed successfully, but I had no WAN connection. I flashed back to 388.7 and everything worked fine again. I'm using the web UI on Windows 11 and am not using any VPN configuration and my provider is Google Fiber. I waited a few days and just tried 388.8_2, but am having the same issues.

I looked at the change log and noted the VPN changes, but I'm not using ANY VPN configuration. Given the documention, do i need to make any configuration changes with fw version 388.8_x to get it to work like it was working with 388.7?

I noticed that the ASUS support websites latest firmware release for the RT-AX3000 is April 2024 which coincides with the Merlin 388.7 release, so maybe my router is no longer supported with the Merlin 388.8 release?

Thanks in advance for any help.

 

[Moshe1010]

I’m trying to upgrade GT-AX11000

From 3004.388.8 to 3004.388.8_2

But it doesn’t seem to change the version number/upgrade. I definitely use the right firmware file:
GT-AX11000_3004_388.8_2_ubi.w

Thanks

 

[Jeffrey Young]

I lost internet WAN connection. I can reach the router just fine and the manual fw upgrade completed successfully, but I had no WAN connection.

Did you look at the syslog for clues as to what the router was having issues with?

 

[M75]

@GNUton thanks for the FW and good job to @RMerlin too

 

[monakh]

reboot the router then tried updating to 388.8_2 again, still got same error. After this message I reboot the router firmware stays as old version (388.7)

View attachment 60699

Anyone got GT-AXE16000 updated to 388.8_2 ROG successfully?

Yes. Working OK here with a dirty upgrade over 8_0.

 

[webjunk78230]

@GNUton thanks for the FW and good job to @RMerlin tooView attachment 60792

Did you look at the syslog for clues as to what the router was having issues with?

Did you look at the syslog for clues as to what the router was having issues with?

Thanks for the reply - yes I did look at the log, but I'm not sure what I'm looking for. Attached is the syslog when I applied 388.8_2 and when the router rebooted. I have no idea why my log has random May 5 entries, but it has done that for many years and I've never been able to determine why. I may be overthinking this, but doesn't a Merlin firmware release usually follow an Asus firmware release? Asus's last fw release for the AX3000 was April 2024 which coincides with Merlin 388.7 (which works fine on my AX3000). There has been no firmware release for the AX3000 from Asus since April 2024, so perhaps 388.8 no longer supports the AX3000?