[Release] Asuswrt-Merlin 384.10 is now available

[rromeroa]

#!/bin/sh
rm /etc/zebra.conf
service restart_quagga

this workaround does not work.

 

[maxbraketorque]

No. It will only remove the unused variables from nvram, all key and certs are now stored in the JFFS partition.

Awesome and thanks. I'll try upgrading to 384.10 this evening.

 

[talon_262]

Can't upgrade my AC86U to 384.10 from 384.9, it keeps through "firmware flashing unsuccessful"; I tried Chrome and IE, I tried (re)downloading through multiple SF mirrors, I even tried unzipping it through Windows 10's built-in ZIP utility and through 7-Zip.

All failed; what could be happening here?

Edit: And, before anyone else asks it, I have been downloading the correct file for the AC86U, not for the AC68U...several times.

 

[octopus]

Can't upgrade my AC86U to 384.10 from 384.9, it keeps through "firmware flashing unsuccessful"; I tried Chrome and IE, I tried (re)downloading through multiple SF mirrors, I even tried unzipping it through Windows 10's built-in ZIP utility and through 7-Zip.

All failed; what could be happening here?

make sure you have downloaded right file, not fore-ac68u.

 

[talon_262]

make sure you have downloaded right file, not fore-ac68u.

It's been the correct file every time I tried; still, no dice.

 

[octopus]

It's been the correct file every time I tried; still, no dice.

Remove ev usb and reboot and try again and you load this file?
===>>> RT-AC86U_384.10_0_cferom_ubi.w

 

[Seamaster]

Dirty upgrade from 384.9 with no issues, thank you @RMerlin for your great job.

 

[RMerlin]

this workaround does not work.

Make sure you enable User Script under Administration -> System. Then check the content of /etc/zebra.conf after the router has booted.

 

[RMerlin]

If you have issues connecting your OpenVPN client, make sure you have up-to-date certificates. Older SHA1-signed certificates are no longer accepted by OpenSSl 1.1.1.

 

[talon_262]

Remove ev usb and reboot and try again and you load this file?
===>>> RT-AC86U_384.10_0_cferom_ubi.w

Yes... I was using the *.w file.

However, removing my Diversion/Skynet USB drive did the trick; I was able to upgrade after that.

 

[visortgw]

Yes... I was using the *.w file.

However, removing my Diversion/Skynet USB drive did the trick; I was able to upgrade after that.

Depending on what is running in the background and what USB device(s) are mounted, sometimes it is necessary to remove the drive in order to free up enough RAM to complete the upgrade.

 

[RMerlin]

Especially as the RT-AC86U can get tight on free RAM.

 

[baronet]

Updated.
Seem ok, except this problem: https://www.snbforums.com/threads/issue-with-vpn-and-merlin-384-9.55690/

 

[tallytr]

Second time I've upgraded from 384.9 to 384.10 it worked perfectly fine. Everything the way it should be.
(Gave me a headache yesterday. Initially the upgrade didn't register, said it was still on 384.9 after uploading new firmware so did it again, afterwards no Wifi and constant connection drop-outs...)
Today on the other hand everything was perfect right away, did the "dirty" upgrade.
Power-cycled RT-AC86U after upgrade.
Thanks.

 

[Zork]

Upgraded today and setting all from zero, going great!

 

[dragon31337]

I updated on beta 3 few days ago and today updated to release it it is so unstable for me once I connect to the VPN and start doing noticable transfers.

Spoiler

Mar 25 18:42:27 rc_service: ntp 531:notify_rc restart_diskmon
Mar 25 18:42:27 rc_service: waitting "start_firewall" via udhcpc ...
Mar 25 18:42:27 kernel: nf_conntrack_rtsp v0.6.21 loading
Mar 25 18:42:27 kernel: nf_nat_rtsp v0.6.21 loading
Mar 25 18:42:28 rc_service: udhcpc 510:notify_rc start_upnp
Mar 25 18:42:28 rc_service: waitting "stop_upnp" via udhcpc ...
Mar 25 18:42:28 disk_monitor: Finish
Mar 25 18:42:29 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Mar 25 18:42:30 miniupnpd[685]: HTTP listening on port 40590
Mar 25 18:42:30 miniupnpd[685]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 25 18:42:30 disk_monitor: be idle
Mar 25 18:42:30 dhcp_client: bound 73.231.231.189 via 73.231.230.1 during 180113 seconds.
Mar 25 18:42:31 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 25 18:42:39 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 25 18:42:45 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 25 18:42:50 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 25 18:42:53 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 25 18:43:05 crond[306]: time disparity of 467377 minutes detected
Mar 25 19:30:57 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 25 21:36:14 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 25 21:36:35 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 26 02:40:06 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 26 02:44:12 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 02:57:16 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 02:59:37 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 26 03:42:01 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 26 06:13:37 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 26 06:28:33 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 06:28:33 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 06:28:43 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 06:28:43 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 06:29:51 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 06:29:51 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 06:42:27 ntp: start NTP update
Mar 26 06:42:39 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 07:01:21 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 07:01:21 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 07:28:15 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 07:28:15 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 07:28:18 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 07:28:32 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 07:30:03 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 07:30:03 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 09:41:36 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 26 09:47:19 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 09:56:17 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 09:56:17 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 09:56:30 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 26 10:00:06 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:00:09 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:00:10 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:00:12 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:02:26 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:07:45 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:08:25 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:13:08 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:13:11 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:16:05 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:16:16 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:18:00 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:18:04 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:29:14 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:32:17 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:33:16 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:33:40 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:35:04 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:35:30 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:39:06 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:39:06 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:39:18 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:39:21 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:39:40 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:39:40 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:40:12 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:40:13 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 10:41:19 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 10:41:23 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 11:23:23 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 11:28:37 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 26 11:29:14 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 11:31:19 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 11:45:11 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 11:45:16 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 16:57:29 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 26 16:58:40 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 16:59:04 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 17:01:52 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 17:01:53 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 18:33:34 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 18:42:24 ntp: start NTP update
Mar 26 19:03:24 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 26 19:03:24 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 26 21:05:38 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 26 21:29:58 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 26 22:29:56 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 26 22:30:04 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 26 22:34:50 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 02:40:15 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 04:32:41 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 04:40:07 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 27 04:40:43 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 27 04:43:45 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 27 04:43:47 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 27 04:43:48 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 04:44:03 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 04:44:10 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 04:45:15 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 27 04:45:17 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 04:46:17 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 04:47:24 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 04:48:24 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 04:49:32 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 04:49:53 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 27 04:50:32 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 04:51:53 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 04:51:55 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 04:57:36 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 04:57:36 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 04:57:56 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 04:58:04 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 04:59:10 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:00:10 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:08:51 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:08:55 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 27 05:14:13 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:14:13 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:14:33 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:14:41 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:15:58 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:16:14 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:16:14 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 27 05:16:58 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:18:19 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:19:19 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:20:26 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:21:27 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:21:30 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:21:31 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:21:40 WLCEVENTD: eth1: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:22:03 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 27 05:24:56 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:24:56 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:25:16 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:25:24 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:26:30 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:27:30 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:29:17 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:30:17 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:30:27 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:30:35 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:31:52 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:32:52 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:36:05 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:36:21 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:37:05 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:37:22 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:37:30 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:38:36 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:39:36 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:43:28 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:43:28 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
Mar 27 05:43:49 WLCEVENTD: eth2: Disassoc SO:ME:MA:C_:__:__
Mar 27 05:43:56 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__

 

[Xentrk]

I updated on beta 3 few days ago and today updated to release it it is so unstable for me once I connect to the VPN and start doing noticable transfers.

Spoiler

Mar 25 18:42:27 rc_service: ntp 531:notify_rc restart_diskmon
Mar 25 18:42:27 rc_service: waitting "start_firewall" via udhcpc ...
Mar 25 18:42:27 kernel: nf_conntrack_rtsp v0.6.21 loading
Mar 25 18:42:27 kernel: nf_nat_rtsp v0.6.21 loading
Mar 25 18:42:28 rc_service: udhcpc 510:notify_rc start_upnp
Mar 25 18:42:28 rc_service: waitting "stop_upnp" via udhcpc ...
Mar 25 18:42:28 disk_monitor: Finish
Mar 25 18:42:29 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Mar 25 18:42:30 miniupnpd[685]: HTTP listening on port 40590
Mar 25 18:42:30 miniupnpd[685]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 25 18:42:30 disk_monitor: be idle
Mar 25 18:42:30 dhcp_client: bound 73.231.231.189 via 73.231.230.1 during 180113 seconds.
Mar 25 18:42:31 WLCEVENTD: eth1: Assoc SO:ME:MA:C_:__:__
Mar 25 18:42:39 WLCEVENTD: eth2: Assoc SO:ME:MA:C_:__:__
<snip>

See if the tips on this post help.
https://www.snbforums.com/threads/asus-rt-ac88u-drops-homekit-devices-wlceventd.54482/

Further discussion starts here: https://www.snbforums.com/threads/r...-9-is-now-available.54843/page-13#post-464527

RMerlin said: ↑
In newer routers, if you experience wireless stability issues then it's recommended that you disable the following options:

• MU-MIMO (some hardware revisions have non-functional/unreliable implementations)
• Airtime Fairness (causes connectivity issues for various devices, including wireless printers)
• Universal Beamforming (non-standard, might cause compatibility issues with some clients)

 

[SMS786]

If you have issues connecting your OpenVPN client, make sure you have up-to-date certificates. Older SHA1-signed certificates are no longer accepted by OpenSSl 1.1.1.

Can anyone point me in the right direction regarding updating said certificates? I exported the updated ovpn file from the admin GUI and on my windows client 2.4.7 (which includes OpenSSL 1.1.1) my connection still shows that it's utilizing OpenSSL 1.1.0.

 

[Xentrk]

Can anyone point me in the right direction regarding updating said certificates? I exported the updated ovpn file from the admin GUI and on my windows client 2.4.7 (which includes OpenSSL 1.1.1) my connection still shows that it's utilizing OpenSSL 1.1.0.

I think he is referring to the CA-Certificate from the VPN provider.

 

[pusb87]

Notes:

• This release resolved the issue where OpenVPN key/certs might sometimes end up stored in nvram (in addition to their proper jffs location), which would result in a lot of wasted nvram. I have also removed the nvram instances of these nvram values, to save even more nvram. To clean up your router, you can run the following script:
  
  

  #!/bin/sh
  
  echo "Removing unused cert/key from nvram..."
  
  for i in 1 2 3 4 5
  do
     nvram unset vpn_crt_client$i\_ca
     nvram unset vpn_crt_client$i\_extra
     nvram unset vpn_crt_client$i\_crt
     nvram unset vpn_crt_client$i\_key
     nvram unset vpn_crt_client$i\_crl
     nvram unset vpn_crt_client$i\_static
  done
  
  for i in 1 2
  do
     nvram unset vpn_crt_server$i\_ca
     nvram unset vpn_crt_server$i\_dh
     nvram unset vpn_crt_server$i\_ca_key
     nvram unset vpn_crt_server$i\_extra
     nvram unset vpn_crt_server$i\_client_crt
     nvram unset vpn_crt_server$i\_crl
     nvram unset vpn_crt_server$i\_crt
     nvram unset vpn_crt_server$i\_key
     nvram unset vpn_crt_server$i\_static
     nvram unset vpn_crt_server$i\_client_key
  done
  
  nvram commit
  
  echo "done."

Hi,

Thanks once again to @RMerlin for an excellent firmware upgrade.

I have an RTAC86U and have succesfully upgraded to 384.10 but noted your comments about the cert keys so though i would try to clear out using your script. I have never used scriots before so i am in unknown terrortory bit thought i would give it a go.

However, although i have read up on the wiki and other forum posts i am still struggling !

This is what i have done:-
Copy and pasted the script into Notepad ++ and called it nvramclean
Enabled JFFS custom scripts + configs in router
Enabled SSH on LAN in router.
applied and rebooted router
transferred nvramclean into jffs/scripts using winscp
used terminal to chmod a+r x jffs/scripts/nvramclean
rebooted router
used winscp - terminal to run the script ( i am unsure whether i really know how to do this !) but what i have tried fails !!

I have attached screenshots so hopefully someone can tell me where i am going wrong.

many thanks in advance of any replys.