Release Asuswrt-Merlin 388.1 is now available for all supported Wifi 6 models

[karateca]

hello, me again, i haved this last week many lose connection with internet, first time i think was a problem with ISP, cuz change 600mb to 1gb of speed. But 2 days ago i change the firmware to the stock firmware and i dont have more disconnection. Today i go back to merlin firmware and even dont pass 2 hours and lose the connection again. Hope can help me with this plz.

Feb 9 18:31:13 pppd[1440]: Connection terminated.
Feb 9 18:31:13 pppd[1440]: Modem hangup
Feb 9 18:31:13 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 40:2F:86:05:43:2C, status: 0, reason: Previous authentication no longer valid (2), rssi:0
Feb 9 18:31:13 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 68:72:C3:81:A3:C8, status: 0, reason: Previous authentication no longer valid (2), rssi:0
Feb 9 18:31:13 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 8C:85:80:C9:FD6, status: 0, reason: Previous authentication no longer valid (2), rssi:0
Feb 9 18:31:13 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 8C:85:80:E7:F5:C4, status: 0, reason: Previous authentication no longer valid (2), rssi:0
Feb 9 18:31:13 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 54:48:E6:71:4B:B3, status: 0, reason: Previous authentication no longer valid (2), rssi:0
Feb 9 18:31:14 wlceventd: wlceventd_proc_event(508): eth7: Disassoc 40:2F:86:05:43:2C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 9 18:31:15 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 8C:85:803:C9F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 9 18:31:16 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 8C:85:80:E7:F5:C4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 9 18:31:16 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 8C:85:80:C9:FD6, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 9 18:31:17 acsd: acs_candidate_score_busy(951): eth6: busy check failed for chanspec: 0x180a (8l)
Feb 9 18:31:17 acsd: acs_candidate_score_intf(1003): eth6: intf check failed for chanspec: 0x180a (8l)
Feb 9 18:31:17 acsd: acs_candidate_score_bgnoise(1320): eth6: bgnoise check failed for chanspec: 0x180a (8l)
Feb 9 18:31:17 acsd: acs_candidate_score_txop(1575): eth6: txop check failed for chanspec: 0x180a
Feb 9 18:31:17 acsd: acs_candidate_score_busy(951): eth6: busy check failed for chanspec: 0x180b (9l)
Feb 9 18:31:17 acsd: acs_candidate_score_intf(1003): eth6: intf check failed for chanspec: 0x180b (9l)
Feb 9 18:31:17 acsd: acs_candidate_score_bgnoise(1320): eth6: bgnoise check failed for chanspec: 0x180b (9l)
Feb 9 18:31:17 acsd: acs_candidate_score_txop(1575): eth6: txop check failed for chanspec: 0x180b
Feb 9 18:31:17 acsd: acs_set_chspec: 0x180a (8l) for reason APCS_CSTIMER
Feb 9 18:31:18 acsd: eth6: selected_chspec is 0x180a (8l)
Feb 9 18:31:18 acsd: eth6: Adjusted channel spec: 0x180a (8l)
Feb 9 18:31:18 acsd: eth6: selected channel spec: 0x180a (8l)
Feb 9 18:31:18 acsd: eth6: txop channel select: Performing CSA on chspec 0x180a
Feb 9 18:31:58 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:33:13 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:34:28 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:35:43 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:36:58 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:38:13 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:39:28 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:40:43 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:41:58 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:43:13 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:44:28 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:45:43 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:46:59 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:48:14 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:49:29 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:49:46 acsd: acs_candidate_score_busy(951): eth6: busy check failed for chanspec: 0x180a (8l)
Feb 9 18:49:46 acsd: acs_candidate_score_intf(1003): eth6: intf check failed for chanspec: 0x180a (8l)
Feb 9 18:49:46 acsd: acs_candidate_score_bgnoise(1320): eth6: bgnoise check failed for chanspec: 0x180a (8l)
Feb 9 18:49:46 acsd: acs_candidate_score_txop(1575): eth6: txop check failed for chanspec: 0x180a
Feb 9 18:49:46 acsd: acs_candidate_score_busy(951): eth6: busy check failed for chanspec: 0x180b (9l)
Feb 9 18:49:46 acsd: acs_candidate_score_intf(1003): eth6: intf check failed for chanspec: 0x180b (9l)
Feb 9 18:49:46 acsd: acs_candidate_score_bgnoise(1320): eth6: bgnoise check failed for chanspec: 0x180b (9l)
Feb 9 18:49:46 acsd: acs_candidate_score_txop(1575): eth6: txop check failed for chanspec: 0x180b
Feb 9 18:50:44 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:51:59 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:53:14 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:54:29 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:55:44 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:56:59 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:58:14 pppd[1440]: Timeout waiting for PADO packets
Feb 9 18:59:29 pppd[1440]: Timeout waiting for PADO packets
Feb 9 19:00:44 pppd[1440]: Timeout waiting for PADO packets
Feb 9 19:02:00 pppd[1440]: Timeout waiting for PADO packets
Feb 9 19:03:15 pppd[1440]: Timeout waiting for PADO packets
Feb 9 19:04:30 pppd[1440]: Timeout waiting for PADO packets
0:47 services: apply rules error(18891)
Feb 9 20:10:49 rc_service: httpds 1221:notify_rc restart_wan_if 0;restart_stubby
Feb 9 20:10:49 pppd[31707]: Unable to complete PPPoE Discovery
Feb 9 20:10:49 wsdd2[1849]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Feb 9 20:10:51 pppd[32125]: pppd 2.4.7 started by stolker, uid 0
Feb 9 20:11:02 services: apply rules error(18857)
Feb 9 20:11:02 zcip_client: configured 169.254.95.63
Feb 9 20:11:07 services: apply rules error(18891)
Feb 9 20:11:12 services: apply rules error(18891)
Feb 9 20:11:17 services: apply rules error(18891)
Feb 9 20:11:22 services: apply rules error(18891)
Feb 9 20:11:26 pppd[32125]: Timeout waiting for PADO packets
Feb 9 20:11:27 services: apply rules error(18891)
Feb 9 20:11:32 services: apply rules error(18891)
Feb 9 20:11:37 services: apply rules error(18891)
Feb 9 20:11:42 services: apply rules error(18891)
Feb 9 20:11:47 services: apply rules error(18891)
Feb 9 20:11:52 services: apply rules error(18891)
Feb 9 20:11:57 services: apply rules error(18891)
Feb 9 20:12:02 services: apply rules error(18891)
Feb 9 20:12:07 services: apply rules error(18891)
Feb 9 20:12:12 services: apply rules error(18891)
Feb 9 20:28:22 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Feb 9 20:28:22 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 194 for peer 58:bf:25:2d:f2:38 prio 5 ifindex 0
Feb 9 20:28:22 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Feb 9 20:28:22 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 58:BF:25:2D:F2:38, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 9 20:28:22 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Feb 9 20:28:22 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 58:BF:25:2D:F2:38, status: 0, reason: Previous authentication no longer valid (2), rssi:0
Feb 9 20:28:22 kernel: CONSOLE: 108279.167 iov:SCB_DEAUTH
Feb 9 20:28:22 kernel: CONSOLE: 108279.167 wl0.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 58:bf:25:2d:f2:38 AID 22 tid 5
Feb 9 20:28:22 kernel: CONSOLE: 108279.169 iov:SCB_DEAUTH
Feb 9 20:28:22 kernel: CONSOLE: 108279.169 iov:SCB_DEAUTH
Feb 9 20:28:22 kernel: CONSOLE: 108279.191 iov:SCB_DEAUTH
Feb 9 20:28:22 kernel: CONSOLE: 108279.191 iov:SCB_DEAUTH
Feb 9 20:28:23 wlceventd: wlceventd_proc_event(527): eth6: Auth 58:BF:25:2D:F2:38, status: Successful (0), rssi:0
Feb 9 20:28:23 wlceventd: wlceventd_proc_event(556): eth6: Assoc 58:BF:25:2D:F2:38, status: Successful (0), rssi:0
Feb 9 20:28:23 kernel: CONSOLE: 108279.831 wlc_ap_authresp: status 0
Feb 9 20:28:23 kernel: CONSOLE: 108279.834 wlc_ap_process_assocreq_done status 0
Feb 9 20:28:23 kernel: CONSOLE: 108279.836 iov:SCB_DEAUTH
Feb 9 20:28:23 kernel: CONSOLE: 108279.837 txrep:802.1x
Feb 9 20:28:23 kernel: CONSOLE: 108279.839 wl0.0: wlc_send_bar: for 58:bf:25:2d:f2:38 seq 0x1 tid 5
Feb 9 20:28:24 services: apply rules error(18891)
Feb 9 20:28:24 kernel: CONSOLE: 108280.833 txrep:802.1x
Feb 9 20:28:25 kernel: CONSOLE: 108281.828 txrep:802.1x

 

[128bit]

hello, me again, i haved this last week many lose connection with internet, first time i think was a problem with ISP, cuz change 600mb to 1gb of speed. But 2 days ago i change the firmware to the stock firmware and i dont have more disconnection. Today i go back to merlin firmware and even dont pass 2 hours and lose the connection again. Hope can help me with this plz.

i've been doing merlinware for years now. 388 by far was unusable - a first for me. stockware also sucked. asked for help and was totally ignored - twice even! yet another first. i've not jumped on the latest 2/7/23 release.

while i do applaud the fine work eric does, sw is tough. it seems like he's the single developer for a worldwide product. that in itself is insane. i've done global software as a profession and it's intense. how he manages to do all that he does astonishes me.

i will likely pass on the next couple releases until things settle. i reverted to 386.72 which was always stable and runs like a thoroughbred. i don't run mesh but use a vpn and some static ip's at home with about 30 clients. it's solid as a rock.

 

[domic]

Is it safe to downgrade to 386.7_2 from 388.1 for now and keep existing configs?

 

[128bit]

Is it safe to downgrade to 386.7_2 from 388.1 for now and keep existing configs?

i did it BUT since i tried 388 at least 3 times then the previous stockware (prior to 2/7) i did hard resets. i was being extra cautious due to all the problems. you may not have to but if you use vpn director, there may be a change, can't recall as it's been awhile. still, reverting was quite worthwhile for me as 386.72 remains solid.

 

[TimmyL]

Can't connect to NORDvpn, after fallback from ASUS the latest firmware version 3.0.0.4.388.22238, back to Merlin 388.2 Alpha, but get the system Log:
ovpn-client1[8907]: --cipher is not set. Previous OpenVPN version defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers.
Feb 10 13:19:11 ovpn-client1[8907]: Options error: You must define CA file (--ca) or CA path (--capath)
Feb 10 13:19:11 ovpn-client1[8907]: Use --help for more information.
Feb 10 13:19:11 openvpn: Starting OpenVPN client 1 failed!
Since there is no such setting in Merlin firmware , such as Cipher Negotation and Legacy/fallback cipher,
will there be any one here can help me to solve this problem.
or can I fill in something in the attached fields ?

Thanks
Asus GT-AXE11000 @388.2 Alpha

 

[Dedel66]

It would be nice if everyone posting here had a signature with their router model so anyone reading along can see what the postimg refers to.
Thanks...
Greetings to all!

 

[AntonK]

It would be nice if everyone posting here had a signature with their router model so anyone reading along can see what the postimg refers to.
Thanks...
Greetings to all!

Agree. Signatures are great, and take a second to create.

 

[RMerlin]

Can't connect to NORDvpn, after fallback from ASUS the latest firmware version 3.0.0.4.388.22238, back to Merlin 388.2 Alpha, but get the system Log:
ovpn-client1[8907]: --cipher is not set. Previous OpenVPN version defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers.
Feb 10 13:19:11 ovpn-client1[8907]: Options error: You must define CA file (--ca) or CA path (--capath)
Feb 10 13:19:11 ovpn-client1[8907]: Use --help for more information.
Feb 10 13:19:11 openvpn: Starting OpenVPN client 1 failed!
Since there is no such setting in Merlin firmware , such as Cipher Negotation and Legacy/fallback cipher,
will there be any one here can help me to solve this problem.
or can I fill in something in the attached fields ?

Thanks
Asus GT-AXE11000 @388.2 Alpha

The cipher line is just a warning indicating that you might have issues if your remote end is running a very old version (older than 2.4). Your actual problem lies with the missing Certificate Authority certificate.

 

[TimmyL]

actual problem lies with the missing Certificate Authority certificate

Sorry RMerlin, I am just a layman only, I just don't know how to insert back the missing Certificate Authority certificate, here is my VPN client input screen. Pls help me how to insert back the missing Certificate Authority certificate. I tried to contact Nordvpn but they just said only have a guide for Asus Rapture routers when they have VPN Fusion option.


Thanks.

 

[ColinTaylor]

Sorry RMerlin, I am just a layman only, I just don't know how to insert back the missing Certificate Authority certificate, here is my VPN client input screen. Pls help me how to insert back the missing Certificate Authority certificate

Thanks.

Upload the NordVPN ovpn file and configure the client again.

 

[TimmyL]

I tried to upload the related ovpn file and get the same result error-check configuration! and I had contacted NordVPN several times, they just said there is nothing wrong, but they just support Asus's VPN fusion only,

 

[128bit]

I tried to upload the related ovpn file and get the same result error-check configuration! and I had contacted NordVPN several times, they just said there is nothing wrong, but they just support Asus's VPN fusion only,

weird, cause i use nord/udp on my ax86u and it's fine. you may have to post your config for more help. oops, are you on 388.2? i missed that. shouldn't you be on a different thread?

 

[TimmyL]

weird, cause i use nord/udp on my ax86u and it's fine. you may have to post your config for more help.

I had already upload my VPN Client input screen above.

 

[128bit]

I had already upload my VPN Client input screen above.

perhaps it's my old eyes but unreadable.

 

[ColinTaylor]

I had already upload my VPN Client input screen above.

388.2 alpha is an unsupported alpha release for people that want to experiment with it. Go back to 388.1 and see if the same problem exists.

 

[TimmyL]

388.2 alpha is an unsupported alpha release for people that want to experiment with it. Go back to 388.1 and see if the same problem exists.

I tried fallback to 388.1, still get the same result

 

[ColinTaylor]

I tried fallback to 388.1, still get the same result

Check the VPN client "Keys and Certificates" (Static Key and Certificate Authority). They are part of the config file you downloaded from NordVPN but were missing in your post #825.

 

[TimmyL]

Check the VPN client "Keys and Certificates" (Static Key and Certificate Authority). They are part of the config file you downloaded from NordVPN but were missing in your post #825.

sorry, how to check ? I just a layman, I only know how to follow the instruction step by step only. As I had already contact NordVPN and they just said it seems normal in my VPN client setting

 

[domic]

It would be nice if everyone posting here had a signature with their router model so anyone reading along can see what the postimg refers to.
Thanks...
Greetings to all!

Good idea, I'll start doing that right away.

 

[Jaime Alvarez]

sorry, how to check ? I just a layman, I only know how to follow the instruction step by step only. As I had already contact NordVPN and they just said it seems normal in my VPN client setting

Don't forget to press tjhe "Apply" button after uploading the ovpn file you got from NordVPN. And do it againg after doing any changes, like entering your username and password.

It has happened to me before...