What's new

Release Asuswrt-Merlin 386.1 is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Hello again everybody.

First of all, thanks to @RMerlin for the great work done.

I dirty flashed 386.1 final on RT-AC86U.
By now I've exactly the same issues as in Beta 5:

CPU Temp jumped from 78°C to 89°C. CPU Wait is enabled. However, as it seems, high temp issue is still present.
I don't understand why for some people the problem is solved, for others not. Is it just a software, or hardware + software issue?

This kind of error message in the system log:
Code:
[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc0074472e8  dir=1 old_key=0xfffffffe new_key=0x20001584[0m

The following error in the system log with Guest WiFi 1 enabled (known issue)
Code:
kernel: protocol 0800 is buggy, dev eth6

Thanks again

very odd, mine was dirty upgrade to, i had no issues with web gui becoming unresponsive or temp issues.
 
All good wit 386.1 on AX86U, just quite few info messages

Jan 31 19:22:18 kernel: 64:89:F1:34:36:95 not mesh client, can't update it's ip

In relation to XBOX and Samsung TV... Dont think I saw these with beta3 or 4, starting seen these with beta5 and final release
 
@RMerlin, don't think I can use Asus stock firmware again, there are so many features missing. Thanks for the AWESOME job.
About Guest Networks and SSID Broadcasts, hiding SSID in the main router doesn't work because second router stills broadcasts. Managed to resolve trhough nvram command via SSH on the second router, but need to redo every time I apply settings on the main router.
AC86U as main router and AC68U as AiMesh node, 386.1 clean install.
Is this something that can be resolved on futures releases or is it a part of the AiMesh code where you have nothing to do?
 
Last edited:
I know that the time scheduler should block all access, but on my RT-AX86U only web access is blocked. Devices that should be blocked with time scheduler, cannot access web pages from the browser, but Netflix, Spotify, etc. still have access to the internet.
Hmm.....maybe something different with that unit possibly? I have the AC86u unit and for my children they aren't able to get on anything internet related. XboxLive, netflix, amazon, etc....
 
Dirty upgrade from 384.19 to 386.1 on AX58 (no scripts, no VPNs). Everything seems fine, 22 clients in the last 6 hours without problems.

Only 1 glitch found: several registry entries "kernel: nf_conntrack: expectation table full" not a lot but maybe 20 o 30 in 6 hours.
 
upgrade from beta 5 on my RT 5300 all running well , no problems showing up in the logs yet , will update in a day if things show up .
Thanks again for al the work you put in to bring all of us a great firmware option . Merlin is one of the reasons I have stuck with Asus for the past 12 years . the other being Asus supporting models for years after they are released , unlike other brands that drop support 6 months after release or new model replacing it
 
Last edited:
Further exploration of 386.1 on my RT-AC86U; the Wifi Radar tools only shows the RT-86U's SSID in the graphs for both 2.4 & 5 GHz.
 
I don't know if that's a bug or not but RAM usage in the dashboard an in htop are pretty different. Dashboard always shows around ~480MB even when there are no scripts installed.

dashboard.png


htop.png


I'm not obsessed with RAM, especially under Linux since I know that unused RAM is wasted RAM, but the difference between makes me wonder.
 
Dirty upgrade from 384.19. No apparent issues. Skynet, YazFi, FlexQoS, Entware, VPNs, everything appears to be working as expected.
 
Installed 386.1 on a new X86U a couple of days ago and configured it from scratch. Yesterday around 11:30pm, it restarted on its own. Today around 2:37pm, it restarted on its own again.

Anything to look for in the System Log? Nothing seems to stick out to me, I guess it may have cleared anything just prior to the restart as part of the issue.
 
Upgraded to 386.1 after a full reset on both units. The only issue is roam assist is “dumber” in this version than in 384.19. The clients seem real sticky even running the same roam assist settings I was using in 384.19. I will let it run for a few days and see what heppens.
 
Dirty upgrade from B5 on AX86U, and only thing i can see is after the upgrade the Addons tab is missing so i can consult the GUI version of spdMerlin and ConnMon... beside that (which might be plugin related) everything seems fine.
 
Dirty update from 384.19 to 386.1 RT-AC5300 Main router + 3 AIMesh nodes RC-AC68U. All seems well so far. Thanks for all the work on this @RMerlin!
 
-- Migration from 314.18 to 316.1 - settings - AiProtection / Parental Controls / Time Scheduling --

Thank you very much for this release and so many years of continued work.

I upgraded my AC-86U from 384.18 to 386.1, without reset. All good.

Nothing special with temperature. Details below.
Regarding AiProtection / Parental Controls / Time Scheduling, it might be a good idea to delete rules and disable the feature before the upgrade. Alternatively, I would recommend to delete rules, disable the feature and recreate all rules after the upgrade. Indeed, after the upgrade, my router still had "Time Scheduling" active for 4 devices, but the Web UI only showed 1 device. I was aware of the updated UI, but the internals seems to also have changed. Details below. And of course, I was "prepared to do a factory default reset if something does not work as expected", as per
https://www.snbforums.com/threads/asuswrt-merlin-386-1-is-now-available.69783/#post-657229 ;-)

Finally, fyi, in Network Map, I noticed that some client IP addresses appear as being DHCP (and not "manual") even though the value is definitely manual (and outside the DHCP IP pool). (NB: The lease time is 24h00 and I only upgraded a few hours ago.) I know that "network map" is a closed source part.

Thank you very much again
Take care
Greetings from Belgium



So, the Web UI in 384.18, prior to upgrade, showed 4 "scheduled" devices.
After upgrade:
Android app (1.0.0.6.14) showed zero "scheduled" devices;
the Web UI in 386.1 showed 1 "scheduled" device;
iptables still had 4 referenced MAC adresses. Note that the device listed in the WebUI was the first one appearing in iptables, and in the 384.18 webUI.

**************************************************
***** Right after the migration from 384.18 to 386.1. Notice how the iptables targets 4 devices, even though the Web UI only showed one client.
Code:
Anonymised@RT-AC86U-4020:/tmp/home/root# iptables -t nat   -n --list PREROUTING
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination        
GAME_VSERVER  all  --  0.0.0.0/0            109.89.224.131    
VSERVER    all  --  0.0.0.0/0            109.89.224.131    
DNSFILTER  udp  --  192.168.17.0/24      0.0.0.0/0            udp dpt:53
DNSFILTER  tcp  --  192.168.17.0/24      0.0.0.0/0            tcp dpt:53
PCREDIRECT  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 22:00:00 to 23:59:59 MAC XX:10:81:0F:FB:38
PCREDIRECT  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 00:00:00 to 08:00:00 MAC XX:10:81:0F:FB:38
PCREDIRECT  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 00:00:00 to 08:00:00 on Mon,Tue,Wed,Thu,Sat,Sun MAC YY:DE:90:5D:43:51
PCREDIRECT  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 01:00:00 to 08:00:00 on Fri MAC YY:DE:90:5D:43:51
PCREDIRECT  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 21:00:00 to 23:59:59 on Wed,Fri,Sun MAC YY:DE:90:5D:43:51
PCREDIRECT  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 20:00:00 to 23:59:59 on Mon,Tue,Thu,Sat MAC YY:DE:90:5D:43:51


...


Anonymised@RT-AC86U-4020:/tmp/home/root# iptables -t filter   -n --list FORWARD
Chain FORWARD (policy DROP)
target     prot opt source               destination        
PControls  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 22:00:00 to 23:59:59 MAC XX:10:81:0F:FB:38
PControls  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 00:00:00 to 08:00:00 MAC XX:10:81:0F:FB:38
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            MAC XX:10:81:0F:FB:38
PControls  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 00:00:00 to 08:00:00 on Mon,Tue,Wed,Thu,Sat,Sun MAC YY:DE:90:5D:43:51
PControls  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 01:00:00 to 08:00:00 on Fri MAC YY:DE:90:5D:43:51
PControls  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 21:00:00 to 23:59:59 on Wed,Fri,Sun MAC YY:DE:90:5D:43:51
PControls  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 20:00:00 to 23:59:59 on Mon,Tue,Thu,Sat MAC YY:DE:90:5D:43:51
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            MAC YY:DE:90:5D:43:51


...

ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED
other2wan  all  --  0.0.0.0/0            0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0          
DROP       all  --  0.0.0.0/0            0.0.0.0/0            state INVALID
NSFW       all  --  0.0.0.0/0            0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            ctstate DNAT
OVPN       all  --  0.0.0.0/0            0.0.0.0/0            state NEW
DNSFILTER_DOT  tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:853
DROP       all  --  0.0.0.0/0            0.0.0.0/0          
Anonymised@RT-AC86U-4020:/tmp/home/root#



***** After deleting all visible rules and disabling "Time Schedule" in 386.1.

Code:
Anonymised@RT-AC86U-4020:/tmp/home/root# iptables -t nat   -n --list PREROUTING
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination        
GAME_VSERVER  all  --  0.0.0.0/0            109.89.224.131    
VSERVER    all  --  0.0.0.0/0            109.89.224.131    
DNSFILTER  udp  --  192.168.17.0/24      0.0.0.0/0            udp dpt:53
DNSFILTER  tcp  --  192.168.17.0/24      0.0.0.0/0            tcp dpt:53
Anonymised@RT-AC86U-4020:/tmp/home/root# iptables -t filter   -n --list FORWARD
Chain FORWARD (policy DROP)
target     prot opt source               destination        
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED
other2wan  all  --  0.0.0.0/0            0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0          
DROP       all  --  0.0.0.0/0            0.0.0.0/0            state INVALID
NSFW       all  --  0.0.0.0/0            0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            ctstate DNAT
OVPN       all  --  0.0.0.0/0            0.0.0.0/0            state NEW
DNSFILTER_DOT  tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:853
DROP       all  --  0.0.0.0/0            0.0.0.0/0          
Anonymised@RT-AC86U-4020:/tmp/home/root#


****** After redefining the Time Schedule rules in 386.1:

Code:
Anonymised@RT-AC86U-4020:/tmp/home/root# iptables -t nat   -n --list PREROUTING
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination        
GAME_VSERVER  all  --  0.0.0.0/0            109.89.224.131    
VSERVER    all  --  0.0.0.0/0            109.89.224.131    
DNSFILTER  udp  --  192.168.17.0/24      0.0.0.0/0            udp dpt:53
DNSFILTER  tcp  --  192.168.17.0/24      0.0.0.0/0            tcp dpt:53
PCREDIRECT  all  --  192.168.17.116       0.0.0.0/0            TIME from 22:45:00 to 23:59:59
PCREDIRECT  all  --  192.168.17.116       0.0.0.0/0            TIME from 00:00:00 to 07:00:00
PCREDIRECT  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 22:45:00 to 23:59:59 MAC ZZ:5F:67:21:04:9E
PCREDIRECT  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 00:00:00 to 07:00:00 MAC ZZ:5F:67:21:04:9E
PCREDIRECT  all  --  192.168.17.115       0.0.0.0/0            TIME from 20:30:00 to 23:59:59
PCREDIRECT  all  --  192.168.17.115       0.0.0.0/0            TIME from 00:00:00 to 07:00:00
Anonymised@RT-AC86U-4020:/tmp/home/root# iptables -t filter   -n --list FORWARD
Chain FORWARD (policy DROP)
target     prot opt source               destination        
PControls  all  --  192.168.17.116       0.0.0.0/0            TIME from 22:45:00 to 23:59:59
PControls  all  --  192.168.17.116       0.0.0.0/0            TIME from 00:00:00 to 07:00:00
ACCEPT     all  --  192.168.17.116       0.0.0.0/0          
PControls  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 22:45:00 to 23:59:59 MAC ZZ:5F:67:21:04:9E
PControls  all  --  0.0.0.0/0            0.0.0.0/0            TIME from 00:00:00 to 07:00:00 MAC ZZ:5F:67:21:04:9E
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            MAC ZZ:5F:67:21:04:9E
PControls  all  --  192.168.17.115       0.0.0.0/0            TIME from 20:30:00 to 23:59:59
PControls  all  --  192.168.17.115       0.0.0.0/0            TIME from 00:00:00 to 07:00:00
ACCEPT     all  --  192.168.17.115       0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED
other2wan  all  --  0.0.0.0/0            0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0          
DROP       all  --  0.0.0.0/0            0.0.0.0/0            state INVALID
NSFW       all  --  0.0.0.0/0            0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0          
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            ctstate DNAT
OVPN       all  --  0.0.0.0/0            0.0.0.0/0            state NEW
DNSFILTER_DOT  tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:853
DROP       all  --  0.0.0.0/0            0.0.0.0/0          
Anonymised@RT-AC86U-4020:/tmp/home/root#



Temp before upgrade, with 384.16 (without cake-qos):
46 °C - 53 °C - 76 °C
Temp after upgrade, with 386.1 (with cake-qos diffserv8):
46 °C - 53 °C - 78 °C
 
Dirty upgrade from 384.19 on RT-AC3100 - things came right back up but still awaiting usable WebGUI. I get the login prompt but after that just a blank screen forever loading. I assume this is what was mentioned in the changelog. So far about 20 minutes in. Will wait patiently.
Same here on ac5300. Now an hour in, scared to reboot it.
 
Dirty upgrade AC86U from 384.19 to 386.1. Upgrade went smooth, but I got one blocking issue with the guest network.
This was my working setup on 384.19: I don't use the Merlin embedded DHCP server, but an external DHCP server on my Synology. My guest network has no Intranet access, so I had to add some ebtables rules to allow guest clients to get an IP address from the DHCP server on my Intranet. I added these rules:
ebtables -I FORWARD -i wl0.2 -p ipv4 --ip-proto udp --ip-destination-port 67:68 -j ACCEPT
ebtables -I FORWARD -o wl0.2 -p ipv4 --ip-proto udp --ip-source-port 67:68 -j ACCEPT
ebtables -I FORWARD -i wl1.2 -p ipv4 --ip-proto udp --ip-destination-port 67:68 -j ACCEPT
ebtables -I FORWARD -o wl1.2 -p ipv4 --ip-proto udp --ip-source-port 67:68 -j ACCEPT


After the upgrade to 386.1 this doesn't work anymore. It looks like ebtables isn't used anymore. Previously when setting Intranet access disabled for guest network, I noticed these ebtables rules were added:
-i wl0.2 -j DROP
-o wl0.2 -j DROP
-i wl1.2 -j DROP
-o wl1.2 -j DROP

In 386.1, no ebtables rules are added or removed when setting Intranet access disabled or enabled.

How can I permit guest network clients to access DHCP server on the Intranet?
 
Dirty upgrade of RT-AX88U from 384.19 to 386.1 and it went very smooth. I just want to note that the router speed test was much lower on the download then the same test using Firefox. The upload was fine. I am connected by ethernet cable. Two tests from the router were 377.55 & 496.63 (two different servers) and from Firefox to speedtest.net it was 899. It has been less than an hour since I upgraded but everything seems to be running fine so far. Thanks to Merlin and all that have worked on this!
 
failed.PNG


trying to upgrade from 384.19 and it says unsuccessful. I did a manual reset and that did not help either. Any suggestions?
 
Dirty upgrade of RT-AX88U from 384.19 to 386.1 and it went very smooth. I just want to note that the router speed test was much lower on the download then the same test using Firefox. The upload was fine. I am connected by ethernet cable. Two tests from the router were 377.55 & 496.63 (two different servers) and from Firefox to speedtest.net it was 899. It has been less than an hour since I upgraded but everything seems to be running fine so far. Thanks to Merlin and all that have worked on this!

I also notice a difference from internal test compared to the same servers on the speedtest app.
 
Status
Not open for further replies.

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top