John Adler
Regular Contributor
beta version dirty flash over 384.19
everything fine so far
thxs Merlin
everything fine so far
thxs Merlin
It looks like RMerlin has included a fix since Beta 1 was built. Once Beta 2 is available we can test again
rc: always copy LE certs to /etc on httpd start · RMerl/asuswrt-merlin.ng@a800293 · GitHub
I haven't upgraded my RT-AC68U to v386.1Beta (yet), but on the RT-AX86U/RT-AX56U PPTP works - neither of my VPN ISPs (HMA, VPNBook) support L2TPHI,
VPN PPTP/L2TP Clients does not work
OpenVPN Clients are working normally
?! I cannot understad why...
yes exactly the same...I haven't upgraded my RT-AC68U to v386.1Beta (yet), but on the RT-AX86U/RT-AX56U PPTP works - neither of my VPN ISPs (HMA, VPNBook) support L2TP
e.g.
View attachment 28413
Do you get any errors in Syslog?
Don't have any into depth knowledge on security. I only know it offers 128 bit end to end tunnelling.
Whenever I see posts about 5GHz radio delays, DFS always comes to mind. Check to make sure you are not using DFS channels. Even if you have not used them in the past, when you reset, make sure you didn't leave something enabled. Also, a 160MHZ width on AX devices will always cross into DFS space, so expect the delay.I've noticed that 5G takes several minutes longer than 2.4 to come up after a reboot, but not random radios turning off after that.
It looks like RMerlin has included a fix since Beta 1 was built. Once Beta 2 is available we can test again
rc: always copy LE certs to /etc on httpd start · RMerl/asuswrt-merlin.ng@a800293 · GitHub
AX86U, can confirm what some others are saying on the Lets Encrypt "Authorizing" issue.
Wiped configuration completely, formatted JFFS, sitting at authorizing. Not much in logs. Happy to look deeper if needed.
Thank you
Just want to throw this out there one more time. A factory reset is necessary with this release!
A lot of problems posted here are a direct result of not doing a factory reset or doing a factory rest improperly. When you do a factory reset make sure you don't restore your settings from a saved backup. It's also recommended to format the JFFS partition after you updated to the new release. And be sure to give your router plenty of time to complete its bootup process after each restart, especially if you do a JFFS partition format. This is not something you can rush in 5 minutes; this needs time to do it properly.
If you're not happy to reset when requested, it's probably worth avoiding the Alpha and Beta code sticking with released versions instead.annoying when I did this on alpha4 anyway as brand new router (and not using a backup of settings to initialise it). PITA always resetting between firmwares. Never have this with other manufacturer devices I have. Good job Merlin's firmware overall is so good to put up with it
If you're not happy to reset when requested, it's probably worth avoiding the Alpha and Beta code sticking with released versions instead.
#ThisIsTheWayI always reset when a new branche is launched. It helps eliminate at least 75 to 90 procent of the issues i usually read on here.
#ThisIsTheOtherWayIf you're not happy to reset when requested, it's probably worth avoiding the Alpha and Beta code sticking with released versions instead.
There are now 3 of us so far that can confirm that rapidly clicking through the menu system (for example to check your settings) on 386 Beta 1 causes the RT-AX58U to crash and reboot.
Same here. Went from 384 release to 386 beta 1. Clicking around in WebUI crashes router. Also, connecting from the Asus Router app and opening the Devices list, then clicking any device will instantly crash the router.
When it's ready!
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!