Yes. But remember:mates, v38 L to v39 E via GUI is fine right?
A factory reset is recommended when changing between 'E' Builds and 'L' Builds of the fork, and any time as the first step in debugging wireless problems.
The CF test only tells you if you're using their servers, not other people's.Any experience here with DoT and the CF test? Does DoT work on other than CF and it's app? For me it always says no to DoT unless I use CF.
I see that now. Thought that it was universal. Thanks.The CF test only tells you if you're using their servers, not other people's.
(Default Build - All supported routers)
1da9783719ba049db983d951f2bf1d2e491eb54da536f6c37b91f83382570b41 RT-N16_374.43_39E3j9527.trx
7ff2550da6a757f989d0e826a65ad564882d9b964bc59be4ea70b85216705d21 RT-AC66U_374.43_39E3j9527.trx
79375da7d3f55626b9cd24aec5b13fb9871e86014f26959b70b32b16fae7fb64 RT-N66U_374.43_39E3j9527.trx
8e21b418e7df90d01b574e1fda08a6be5a8720ac9896a45cf1c8cba01c9dff0f RT-AC68U_374.43_39E3j9527.trx
0bb8364fda5740a1314115dbc1d9acc1f39f92498df55d1f2622ba7d6b0d48d3 RT-AC56U_374.43_39E3j9527.trx
(Legacy Only Builds)
fbba5033a87c5fbed9b3f83a2960838a5d53b717075d1aadc5c0d0ddfe54e4eb RT-AC68U_3.0.0.4_374.43_2-39L3j9527.trx
92faa3693ffc2cbef324fad7ff510d302628c57d977d5597e374e534fb04690b RT-AC56U_3.0.0.4_374.43_2-39L3j9527.trx
545927719c46e359a0db6bf9dcb348f99c0f3d8786725780cb182994c61b19be RT-N16_3.0.0.4_374.43_2-39L3j9527.trx
5e9c82a5b250097172fe3867667149dfa46ed792782cc9f7d11959c44957c2f5 RT-AC66U_3.0.0.4_374.43_2-39L3j9527.trx
9aa05ea06237b4ebec4619c43d9b7ad221c2565a4667971d172a6d857d1bac88 RT-N66U_3.0.0.4_374.43_2-39L3j9527.trx
Hi,
I have an RT-AC66U on 39E1. I just changed the log level from debug to notification, and after the usual waiting time I'm not able to login any more? Username and password just not accepted.
This has happened to me once before. That time I had to reset the router but don't feel like doing that again. Any ideas what's happening?
Edit: Router seems to work as usual, just not able to login to the admin interface.
Just tried flipping the log-level a couple of times and everything worked fine. Can't think of why loglevel would effect logging in.Hi,
I have an RT-AC66U on 39E1. I just changed the log level from debug to notification, and after the usual waiting time I'm not able to login any more? Username and password just not accepted.
This has happened to me once before. That time I had to reset the router but don't feel like doing that again. Any ideas what's happening?
Edit: Router seems to work as usual, just not able to login to the admin interface.
I saw a fork in the router so I took it!Next release has been posted to pick up a few new fixes...nothing critical. I'm going to be tied up for the next couple of weeks, so decided to post up my current working level.
LATEST RELEASE: Update-39E3/39L3
17-April-2019
Merlin fork 374.43_39E3j9527
Download http://bit.ly/1YdgUcP
============================
Key Changes:
- Backported fixes for two buffer overrun exposures from Merlin 384
- Custom scripts now post a log message if they are not marked as executable
- Fix a case where the JFFS syslog copy may not be updated
SHA256
Code:(Default Build - All supported routers) 1da9783719ba049db983d951f2bf1d2e491eb54da536f6c37b91f83382570b41 RT-N16_374.43_39E3j9527.trx 7ff2550da6a757f989d0e826a65ad564882d9b964bc59be4ea70b85216705d21 RT-AC66U_374.43_39E3j9527.trx 79375da7d3f55626b9cd24aec5b13fb9871e86014f26959b70b32b16fae7fb64 RT-N66U_374.43_39E3j9527.trx 8e21b418e7df90d01b574e1fda08a6be5a8720ac9896a45cf1c8cba01c9dff0f RT-AC68U_374.43_39E3j9527.trx 0bb8364fda5740a1314115dbc1d9acc1f39f92498df55d1f2622ba7d6b0d48d3 RT-AC56U_374.43_39E3j9527.trx (Legacy Only Builds) fbba5033a87c5fbed9b3f83a2960838a5d53b717075d1aadc5c0d0ddfe54e4eb RT-AC68U_3.0.0.4_374.43_2-39L3j9527.trx 92faa3693ffc2cbef324fad7ff510d302628c57d977d5597e374e534fb04690b RT-AC56U_3.0.0.4_374.43_2-39L3j9527.trx 545927719c46e359a0db6bf9dcb348f99c0f3d8786725780cb182994c61b19be RT-N16_3.0.0.4_374.43_2-39L3j9527.trx 5e9c82a5b250097172fe3867667149dfa46ed792782cc9f7d11959c44957c2f5 RT-AC66U_3.0.0.4_374.43_2-39L3j9527.trx 9aa05ea06237b4ebec4619c43d9b7ad221c2565a4667971d172a6d857d1bac88 RT-N66U_3.0.0.4_374.43_2-39L3j9527.trx
Agreed, this is not optimal. I'll take a look (have to remember if there was a reason I did it that way or if it's a just a byproduct of using a common subroutine )However, when I hit the DNSSEC radio button, the DoT server selection reverted to my previous entries. All this is done without yet hitting Apply.
I was confused when I saw 2 functions with the same update_resolverlist name, but one was for dnscrypt and one for stubby.Agreed, this is not optimal. I'll take a look (have to remember if there was a reason I did it that way or if it's a just a byproduct of using a common subroutine )
Yes....I left the dnscrypt code in just in case instead of deleting it. It's actually a conditional compile based on selected options as to which one is included. (the ability to do conditional compile within the gui code is something I ported over from Tomato).I was confused when I saw 2 functions with the same update_resolverlist name, but one was for dnscrypt and one for stubby.
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!