Release Asuswrt-Merlin 3004.388.4 is now available

[BobbyFlobby]

Dirty Flash to 3004_388.4_0 on AX88U Pro & AX3000 V1. Up for over 24 hours with no issues.
TNX, RMerlin

Same but on 2x AX86U, web UI seems super snappy too

 

[mmalyska]

Hi, I was using `Tools` for checking ports status.
I'm missing this on `Network Map` page.

Also I've checked and I've enough `NVRAM` 74169 / 131072 bytes

 

[karateca]

Hi, 3 days with out restart or lose internet. But today in the morning lose connection. I left the log if can help me, thx for everything!. Sorry this happen in to the ax11000 with aimesh ax82u.

Aug 24 01:06:22 wlceventd: wlceventd_proc_event(662): eth7: Disassoc E0:92:5C:E4:0A:57, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 24 01:06:22 roamast: [EXAP]Deauth old sta in 1 0: E0:92:5C:E4:0A:57
Aug 24 01:06:22 roamast: eth7: disconnect weak signal strength station [e0:92:5c:e4:0a:57]
Aug 24 01:06:22 roamast: eth7: remove client [e0:92:5c:e4:0a:57] from monitor list
Aug 24 02:30:28 miniupnpd[1726]: removed 18 unused rules
Aug 24 02:49:35 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link UP at 1000 mbps full duplex
Aug 24 02:52:27 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Aug 24 02:52:41 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link UP at 1000 mbps full duplex
Aug 24 02:52:42 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Aug 24 02:52:44 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link UP at 1000 mbps full duplex
Aug 24 02:52:45 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Aug 24 02:52:52 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link UP at 1000 mbps full duplex
Aug 24 03:14:16 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Aug 24 04:00:28 miniupnpd[1726]: removed 18 unused rules
Aug 24 07:08:50 wlceventd: wlceventd_proc_event(685): eth7: Auth E0:92:5C:E4:0A:57, status: Successful (0), rssi:0
Aug 24 07:08:50 kernel: br0: received packet on eth7 with own address as source address
Aug 24 07:08:50 wlceventd: wlceventd_proc_event(695): eth7: ReAssoc E0:92:5C:E4:0A:57, status: Successful (0), rssi:-66
May 5 07:05:06 kernel: klogd started: BusyBox v1.25.1 (2023-08-21 15:35:27 EDT)
May 5 07:05:06 kernel: Linux version 4.1.51 (merlin@ubuntu-dev) (gcc version 5.5.0 (Buildroot 2017.11.1) ) #4 SMP PREEMPT Mon Aug 21 16:27:45 EDT 2023
May 5 07:05:06 kernel: CPU: AArch64 Processor [420f1000] revision 0
May 5 07:05:06 kernel: Kernel command line: coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe rootwait

 

[morden]

Just updated my AX86U to this version with no issues during the process. Thank you Merlin for doing a wonderful job with the custom firmware for Asus routers!!

 

[Mogsy]

Thank you @RMerlin !

 

[L&LD]

@karateca, it may help to put the actual model number in your signature of the routers you're using. And to indicate which router you're providing the log for.

 

[Lee MacMillan]

Dirty flash over 388.2_2 and reboot after 24 hours. Working as expected.

 

[Paliv]

@Tech9 network services filter is working again in this GPL release. Still doesn’t work for IPV6, though.

 

[RMerlin]

@Tech9 network services filter is working again in this GPL release. Still doesn’t work for IPV6, though.

I remember seeing something in newer GPL code that might be related to that (I saw some changes to the firewall related to IPv6, but I didn`t analyze the changes in depth).

 

[Tech9]

@Tech9 network services filter is working again in this GPL release. Still doesn’t work for IPV6, though.

Thank you, but I don't do firmware testing anymore.

 

[Paliv]

Thank you, but I don't do firmware testing anymore.

Enjoy retirement

 

[Tech9]

Enjoy retirement

I travel and race cars summer time. Still have RT-AX86U somewhere, but don't remember what firmware it has on it.

 

[Paliv]

I remember seeing something in newer GPL code that might be related to that (I saw some changes to the firewall related to IPv6, but I didn`t analyze the changes in depth).

Thanks, that’s good to know. The only thing I’m interested in is blocking Quic. Not really right now, but for potential reasons down the road.

 

[Geo92]

Hi. I have a problem after updating.

I updated to 3004.388.2 on my RT-AX88U, however now my assigned DDNS is not connecting. It says; "Request error! Please try again". It was fine before I updated a few minutes ago (old version 388.2). DDNS Registration Result is stuck on processing.

Edit: Fixed it, for some reason I had to activate the: "IPv6 Update" for it to work again. Not sure if that option was there before, anyhow.

 

[MNoisy]

Just leave it disabled. I can't reproduce it, and it's within a closed source component that most people don`t need.,

Thank you!

 

[virusuf86]

Since 388.3 I've had an issue that after a reboot I sometimes (not always, 50/50 chance) get the message: "Your ISP's DHCP is not functioning properly" - so I don't have any internet connectivity at all after the reboot (WAN light is red).

Now after flashing to 388.4 & getting the necessary reboot, I got the same message.

Odd thing is that it can be fixed by just turning the Internet Connection slider to Off & back to On (in GUI: Network Map -> Internet Status). A reboot isn't even needed to fixed this. Because it can be fixed with just that I don't think it's an ISP issue but maybe something in the firmware that randomly causes a faulty DHCP request?

And yes, when I was on 388.3 I did a full reset & still had the issue when doing a reboot (again, not always, it occurs randomly).

Running smooth on my RT-AX88U-PRO besides this little issue.

Same thing is happening on my GT-AX6000. 388.1 is rock solid, but every release afterwards has the random ISP DHCP issue. DHCP query frequency is set to continuous mode. It eventually connects to my secondary WAN, but wont fallback back to the primary because the the DHCP issue. I have tried full resets on all the post-388.1 releases. Im going to try out the latest stock firmware to see if it happens there. Edit: The latest stock firmware is worse!

 

[kstamand]

Asuswrt-Merlin 388.4 is now available for Wifi 6 models.

3004.388.4 (21-Aug-2023)
  - NOTE: In preparation for the new 3.0.0.6 codebase, the version
          string will now start with 3004 or 3006 to match with
          upstream.

  - NOTE: The RT-AX56U is no longer supported, as Asus has put it
          on End-of-Life status, and the previous Asuswrt-Merlin
          388 releases for that model were all based on untested
          code.

  - NEW: Display channel utilisation for supported platforms on the
         Wireless Log page.
  - UPDATED: Merged GPL 388_23588.
  - UPDATED: curl to 8.1.2.
  - UPDATED: OpenVPN to 2.6.5.
  - UPDATED: openssl to 1.1.1u.
  - UPDATED: tor to 0.4.7.13.
  - CHANGED: FTP server will now only support strong ciphers
             in TLS mode.
  - FIXED: QOS Classification showing no Upload data on some
           WAN configurations.
  - FIXED: Radio temperature graphs weren't updating
  - FIXED: XT12 proximity pairing wasn't working (missing
           bluetooth firmware)
  - REMOVED: Ethernet port status from the Tools Sysinfo page
             (as this is redundant with Asus' own display
             now available on the networkmap page).

Downloads are here.
Changelog is here.

Factory reset and upgraded from 388.2_2 two days ago, all good and stable.

Thank you @RMerlin

 

[Aiadi]

I'm trying to follow along and got lost at why a discussion of base code 3006 is in the Release of 3004 base?
Did I make a mistake?

Serious question though. What's happened to 3005?

 

[marc093]

Same thing is happening on my GT-AX6000. 388.1 is rock solid, but every release afterwards has the random ISP DHCP issue. DHCP query frequency is set to continuous mode. It is connected to my secondary WAN, but wont fallback back to the primary because the the DHCP issue. I have tried full resets on all the post-388.1 releases. Im going to try out the latest stock firmware to see if it happens there.

Same thing is happening here as well on my AX88u. Also could not connect to my wifi because of wrong password. Everything is working again after a reboot.

Factory reset after update.

 

[Mchamps]

Question: Does anyone know why in the "network map" the usb recognizes me as 2.0, however in the "states" tab it recognizes it as 3.0 ??. It did not happen to me in the previous firmware version