@RMerlin, thank you for 384.19_0 release final. Great upgrade as usual.
@CaptnDanLKW,
@Jack Yaz, and others, after upgrading
every single RT-AC86U from 384.18 to 384.19_0 release final (almost 50 so far), the JFFS partition truncated to 47MB from 48MB caused issues either immediately or after a few minutes in the amtm scripts (showing minimal updates available when they're not, etc.), or, in the OpenVPN Servers and/or Clients. Waiting, rebooting, or full power off for a minute or two didn't solve these issues.
Upgrading from 384.18_0 or earlier and flashing 384.19_0 or later
requires the steps outlined in the link below for stable operation.
I have no doubt that there will be some combination of options/features and scripts that don't seem to need the suggested steps below, but for 100% peace of mind, the minimal commitment to save the JFFS and then restore it
after flashing 384.19_0 or later is worth it.
Dirty flashed from 384.19_alpha4 to 384.19_beta1 and lost my internet connection. Dirty flashed back to 384.19_alpha4 and my internet connection was available again. Bit short on time now to look at the logs. Router model RT-AC86U. Hi, to correct my issue. First of all I noticed no code...
www.snbforums.com
Note that I
cannot edit the original post stating "... restore the JFFS partition 'if necessary' with 'required'..."
Restore the JFFS you saved after flashing to 384.19_0 to prevent unneeded wild goose chases on ghost issues that don't really exist.