Release Asuswrt-Merlin 3004.388.8_2 is now available

[Qwinn]

thanks for the suggestion. I triple checked and confirmed I downloaded correct firmware (for GT-AXE16000).
I tried to re-install my current firmware (3004.388.7_rog) with the file I downloaded a few months earlier, but still got same error message.

Finally made the plunge myself with my AXE16000 and installed merlin. Installed the ROG version of 388.8_2 over the stock firmware. Went beautifully - amazingly it didn't even reset my public IP, which would reset if I sneezed too hard near it on the stock firmware. And as I was promised in another thread, I can now update the DHCP assignments without causing a public IP reset, which is fantastic. Turned on the NTP server and told it to redirect too, which seems to be working fine. So far it's all positive stuff, wish I'd done it earlier.

Anyways, I replied to you because I'm using the same router and not having your problems. Granted, I've got a fairly simple set up with no VPN previously configured and only a Netgear extender as far as access points. Good luck.

 

[anotherengineer]

Is this typical for log to jump times like this?

Jul 28 20:02:58 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
May 5 01:05:07 kernel: klogd started: BusyBox v1.25.1 (2024-04-26 14:22:45 EDT)
.
.
.
May 5 01:05:07 kernel: Detecting PHYs...
Aug 4 11:56:08 Mastiff: Got SIGTERM
May 5 01:05:07 kernel: brcmboard registered
.
.
.
May 5 01:05:14 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link Up at 100 mbps full duplex
Aug 4 11:57:38 crond[1602]: time disparity of 3288172 minutes detected
.
.
.

 

[Unetwork]

I don't have these items in the logs, but I had this problem after the second day of running version 388.8_2 :

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

I restarted the router and for the last five days I've had nothing abnormal.
That's strange too.

 

[bennor]

@anotherengineer, the May 5th date typically means your router was booted or rebooted and that's the default date (May 5) the firmware uses before it obtains the current network time from the NTP server.

 

[anotherengineer]

@anotherengineer, the May 5th date typically means your router was booted or rebooted and that's the default date (May 5) the firmware uses before it obtains the current network time from the NTP server.

Ya familiar with that, however, if I rebooted it on July 28th, then it stayed May 5th, then jumped to Aug 4th to May5th then back to Aug 4th? But if that's the norm, fine by me. Just curious where July 29th to Aug 3rd went?

 

[Deleted member 48162]

Yes. As indicated in the changelog, the killswitch will activate even if the user manually stops/disable the client. You have to disable the killswitch if you don't want it active.

And how exactly that is done in web interface? I just can't see any "killswitch" over VPN-client. Neither VPN-server contain any adjustment for killswitch. Should I perform Factory Reset? From "network tools" I'm able to 'ping', 'traceroute' and 'nslookup' everything. But no internet access for all my desktops and mobile...

 

[lgkahn]

Kill switch is in client not server

 

[Deleted member 48162]

Kill switch is in client not server

I just can't observe it in web-interface. Could you give me a clue how to switch it OFF, please? And by the way it is called "killswitch" so why it doesn't 'kill' any network tools?

 

[RMerlin]

I just can't observe it in web-interface. Could you give me a clue how to switch it OFF, please? And by the way it is called "killswitch" so why it doesn't 'kill' any network tools?

Traffic redirection needs to be set to either Yes or VPN Director. There's no killswitch if set to "No" because you aren't redirecting anything through it.

 

[Deleted member 48162]

View attachment 60901
Traffic redirection needs to be set to either Yes or VPN Director. There's no killswitch if set to "No" because you aren't redirecting anything through it.

My VPN application has been set manually and all settings are done according to their support page. I've found where to put killswitch OFF. Still the question remains: how to bring internet connection from router to remaining devices? Just to remind: all "Network tools" operate normal. Router gets internet, but doesn't share it with remaining clients as it should. Exactly this happened after my first "dirty" update from 3004.388.7_0 to 3004.388.8_beta1

 

[RMerlin]

My VPN application has been set manually and all settings are done according to their support page. I've found where to put killswitch OFF. Still the question remains: how to bring internet connection from router to remaining devices? Just to remind: all "Network tools" operate normal. Router gets internet, but doesn't share it with remaining clients as it should. Exactly this happened after my first "dirty" update from 3004.388.7_0 to 3004.388.8_beta1

Start a new thread with your question. This thread is specifically for discussing the new release, and does not cover support requests.

 

[Igor]

disconnect the USB before doing a FW upgrade might help avoid the prolem

Do I need to be physically near the router to do this? Or can I do it remotely? The router is 60 kilometers away.

 

[Igor]

Does CVE-2024-7589 affect the current firmware?

 

[ColinTaylor]

Does CVE-2024-7589 affect the current firmware?

The router doesn't run sshd it runs dropbear.

 

[Igor]

Mon Aug 12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C wlceventd: wlceventd_proc_event(831): eth6: Radar detected
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: cm_updateChanspec call wl_chanspec_changed_action
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: event: wl_chanspec_changed_action_a101 of eid(1) of cfgs(1102)
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: ! handling event in static chan case: (5g_1)wl1_chanspec:136u / (5g_2)wl2_chanspec:
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: current chansp(unit0) is 1001
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: current chansp(unit1) is d986
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: dump exclchans:
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: old wl0_acs_excl_chans:0x100c,0x190a,0x100d,0x190b,0x100e,0x190c
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: new wl0_acs_excl_chans:0x100c,0x190a,0x100d,0x190b,0x100e,0x190c
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: valid wl0_acs_excl_chans:
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: old wl1_acs_excl_chans:
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: new wl1_acs_excl_chans:0xd084,0xd088,0xd886,0xd986
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: valid wl1_acs_excl_chans:
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server:  wl_chanspec_changed_action: Need to restart acsd due current 5G chanspec is un-available, (cur_5g=d986), static5G=1
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C cfg_server: reset acs_ifnames as eth6
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C rc_service: cfg_server 1102:notify_rc restart_acsd
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C acsd: eth6: Selecting 5g band ACS policy
Mon Aug 12 20:03:12 2024;10.8.0.3; <13>Aug 12 20:03:12 RT-AX68U-92A0-522207D-C acsd: acs_init_run(1111): acs_start eth6 cannot select chanspec with the wrong info
Mon Aug 12 20:03:15 2024;10.8.0.3; <13>Aug 12 20:03:15 RT-AX68U-92A0-522207D-C acsd: eth6: Selecting 5g band ACS policy
Mon Aug 12 20:03:15 2024;10.8.0.3; <13>Aug 12 20:03:15 RT-AX68U-92A0-522207D-C acsd: acs_init_run(1111): acs_start eth6 cannot select chanspec with the wrong info
Mon Aug 12 20:03:18 2024;10.8.0.3; <13>Aug 12 20:03:18 RT-AX68U-92A0-522207D-C acsd: eth6: Selecting 5g band ACS policy
Mon Aug 12 20:03:18 2024;10.8.0.3; <13>Aug 12 20:03:18 RT-AX68U-92A0-522207D-C acsd: acs_init_run(1111): acs_start eth6 cannot select chanspec with the wrong info
Mon Aug 12 20:03:21 2024;10.8.0.3; <13>Aug 12 20:03:21 RT-AX68U-92A0-522207D-C acsd: eth6: Selecting 5g band ACS policy
...

Please tell me how to understand the reason for the appearance of 5G in the cycle?
It is fixed by rebooting the router.

 

[Thermaltake]

I am on 3004.388.8 didn't flash _2 yet. And today at 00:55 I got message from my NAS that connection has been lost. I check what was wrong and I couldn't connect with my phone on any 5Ghz or 2.4 Wifi, I lost NET completely. And then I turn off router and On again at everything was ok. Only message that I got was this

Aug 13 01:05:10 ntpd: Initial clock set
Aug 13 01:05:10 rc_service: ntpd_synced 1948:notify_rc restart_diskmon
Aug 13 01:05:10 disk_monitor: Finish
Aug 13 01:05:10 disk_monitor: be idle
Aug 13 01:05:11 kernel: random: nonblocking pool is initialized

I assume that's normal startup from router.

 

[jerry6]

I am on 3004.388.8 didn't flash _2 yet. And today at 00:55 I got message from my NAS that connection has been lost. I check what was wrong and I couldn't connect with my phone on any 5Ghz or 2.4 Wifi, I lost NET completely. And then I turn off router and On again at everything was ok. Only message that I got was this

Aug 13 01:05:10 ntpd: Initial clock set
Aug 13 01:05:10 rc_service: ntpd_synced 1948:notify_rc restart_diskmon
Aug 13 01:05:10 disk_monitor: Finish
Aug 13 01:05:10 disk_monitor: be idle
Aug 13 01:05:11 kernel: random: nonblocking pool is initialized

I assume that's normal startup from router.

it would help if you listed router and any add ons you are running

 

[pavlfz]

After following the VPN issues on here and worrying that I may mess things up in ways beyond my understanding, I've finally taken the plunge and dirty flashed 3004.388.8_2 from 388.7 on my ax86u pro. Both the wireguard and openvpn server vpns are working fine. The only client I have running on a wireguard client vpn was already routed with VPN director and that was working fine following a reboot. Turning the killswitch on has had no ill-effects. It's all working perfectly. Very pleased! I was definitely having second and third thoughts about going ahead. Thanks very much Merlin and everyone else who spent time ironing out the problems.

 

[aitor_mtb]

Does anyone know why the VLAN option that should be within LAN does not appear with Merlin?

 

[Dedel66]

VLAN is only available with 3006.xxxx versions of firmware.