Beta Asuswrt-Merlin 386.2 Beta is now available

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.
Status
Not open for further replies.

rlucho

Occasional Visitor
Hi! How are you? New here... I have 2 AX11000 in AiMesh 2.0 working at home, they are using the latest official Asus beta firmware (9.0.0.4.386_41994), so i want to know how to update to Merlin now... Just dirty flash the merlin firmware in both? Nothing else? First time Merlin's user, Thanks in advance!
 

Wistuplu

Regular Contributor
Hello,

Thank you for beta 3.
38 hours running on AC86U
All good.

W.

FYI
Dirty upgrade from 386.2 beta2+
Cake, diffserv4 for upstream
spdMerlin, connmon, cake-qos
No AiMesh
 

Jeffrey Young

Senior Member
Hi! How are you? New here... I have 2 AX11000 in AiMesh 2.0 working at home, they are using the latest official Asus beta firmware (9.0.0.4.386_41994), so i want to know how to update to Merlin now... Just dirty flash the merlin firmware in both? Nothing else? First time Merlin's user, Thanks in advance!

Personally, if you are moving from stock to Merlin, I would not dirty flash.

Flash the new software, then reset the router and setup from scratch. Do not load a previous saved config.
 

maxbraketorque

Very Senior Member
So anyone running beta 3 on AC86U as a main router? Any issues so far? Haven't seen much report here haha. Just some with random problems. But that's to be expected with different configurations...

beta 3 ok for me using AC86Us as a main router in a main/AP combo. But I'm using a pretty simple configuration, and didn't have any obvious issues with beta 2 or beta 1.
 

Matthew Patrick

Senior Member
beta 3 running on AC86U, 38 hours now.
Soild. No issue, feels like running a final 386.2.
Besides it is running almost 90c at most of the time.......
Got a cheap chinese usb fans kit. They have those air filters. Replaceable too it seems like. With the filters it's only pushing like a very small amount of air. I thought it wouldn't be enough. But yes it was more than enough.

From the lowest 80C and normally at 90C (and more if on load) . To about 50C on the lowest and 60C on load . Pretty big difference right there.

The lowest without fan I could get before 386 was 70C and about 69C (nice)
 

RMerlin

Asuswrt-Merlin dev
Hello.

does this beta 3 have all GT11000 features enable ?

best regards
No. This is the compromise for me supporting the ROG models - I won't be using the ROG UI.
 

ugandy

Very Senior Member
no issues on b3
 

gerardr

Occasional Visitor
what is your output of

netstat -lnp | grep 123
Well, I built OpenNTP and put it on my flash drive, so right now the results would be a distraction.

The single port 123 line in my given 'netstat -peanut' output is the last line. Note that the netstat I use is one I built, not the busybox one included in the firmware.

Note, though, that the issue is built into the most recent busybox code. Here's the relevant comment from busybox/include/libbb.h:

Code:
/* Create stream socket, and allocate suitable lsa.
 * (lsa of correct size and lsa->sa.sa_family (AF_INET/AF_INET6))
 * af == AF_UNSPEC will result in trying to create IPv6 socket,
 * and if kernel doesn't support it, fall back to IPv4.
 * This is useful if you plan to bind to resulting local lsa.
 */

The busybox networking/ntpd.c code specifies NULL for the address, which causes libbb/xconnect.c to then substitute AF_UNSPEC as the protocol family, resulting in only an IPv6 socket, since the kernel clearly supports it, whether it's enabled or not.
 

randomName

Very Senior Member
With Cake disabling Trend Micro, how exposed are the routers with JUST the built in firewall?
 

New2This

Senior Member
Running Suricata here, but haven't tired using Cake...
You could also use Skynet
 

Ubimo

Senior Member
Went from beta2 to beta3 on my AC86U.
I'm seeing these in my syslog:
Code:
Mar 30 21:42:55 wlceventd: wlceventd_proc_event(527): eth6: Auth 00:13:EF:F2:xx:xx, status: Successful (0), rssi:0
Mar 30 21:42:55 wlceventd: wlceventd_proc_event(556): eth6: Assoc 00:13:EF:F2:xx:xx, status: Successful (0), rssi:0
Mar 30 21:42:55 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 00:13:EF:F2:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:42:55 wlceventd: wlceventd_proc_event(527): eth6: Auth 00:13:EF:F2:xx:xx, status: Successful (0), rssi:0
Mar 30 21:42:55 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 00:13:EF:F2:xx:xx, status: Successful (0), rssi:0
Mar 30 21:42:55 kernel: br0: received packet on eth6 with own address as source address
Mar 30 21:45:56 kernel: br0: received packet on eth6 with own address as source address
Mar 30 21:45:56 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 00:13:EF:F2:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:45:56 wlceventd: wlceventd_proc_event(527): eth6: Auth 00:13:EF:F2:xx:xx, status: Successful (0), rssi:0
Mar 30 21:45:56 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 00:13:EF:F2:xx:xx, status: Successful (0), rssi:0
Mar 30 21:48:56 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 00:13:EF:F2:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:48:56 wlceventd: wlceventd_proc_event(527): eth6: Auth 00:13:EF:F2:xx:xx, status: Successful (0), rssi:0
Mar 30 21:48:56 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 00:13:EF:F2:xx:xx, status: Successful (0), rssi:0
Mar 30 21:48:56 kernel: br0: received packet on eth6 with own address as source address
Mar 30 21:51:56 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 00:13:EF:F2:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:51:56 wlceventd: wlceventd_proc_event(527): eth6: Auth 00:13:EF:F2:xx:xx, status: Successful (0), rssi:0
Mar 30 21:51:56 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 00:13:EF:F2:xx:xx, status: Successful (0), rssi:0
Mar 30 21:51:56 kernel: br0: received packet on eth6 with own address as source address
This mac adress is my PC im currently writing on.
 

det721

Part of the Furniture
Went from beta2 to beta3 on my AC86U.
I'm seeing these in my syslog:
Code:
Mar 30 21:42:17 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 00:13:EF:F2:4B:27, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:42:48 wlceventd: wlceventd_proc_event(527): eth5: Auth 00:1A:73:E1:CA:0E, status: Successful (0), rssi:0
Mar 30 21:42:48 wlceventd: wlceventd_proc_event(556): eth5: Assoc 00:1A:73:E1:CA:0E, status: Successful (0), rssi:0
Mar 30 21:42:55 wlceventd: wlceventd_proc_event(527): eth6: Auth 00:13:EF:F2:4B:27, status: Successful (0), rssi:0
Mar 30 21:42:55 wlceventd: wlceventd_proc_event(556): eth6: Assoc 00:13:EF:F2:4B:27, status: Successful (0), rssi:0
Mar 30 21:42:55 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 00:13:EF:F2:4B:27, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:42:55 wlceventd: wlceventd_proc_event(527): eth6: Auth 00:13:EF:F2:4B:27, status: Successful (0), rssi:0
Mar 30 21:42:55 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 00:13:EF:F2:4B:27, status: Successful (0), rssi:0
Mar 30 21:42:55 kernel: br0: received packet on eth6 with own address as source address
Mar 30 21:45:56 kernel: br0: received packet on eth6 with own address as source address
Mar 30 21:45:56 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 00:13:EF:F2:4B:27, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:45:56 wlceventd: wlceventd_proc_event(527): eth6: Auth 00:13:EF:F2:4B:27, status: Successful (0), rssi:0
Mar 30 21:45:56 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 00:13:EF:F2:4B:27, status: Successful (0), rssi:0
Mar 30 21:46:51 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 8A:23:FB:6B:80:A0, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Mar 30 21:46:51 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 8A:23:FB:6B:80:A0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:48:39 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 00:1A:73:E1:CA:0E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:48:56 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 00:13:EF:F2:4B:27, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:48:56 wlceventd: wlceventd_proc_event(527): eth6: Auth 00:13:EF:F2:4B:27, status: Successful (0), rssi:0
Mar 30 21:48:56 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 00:13:EF:F2:4B:27, status: Successful (0), rssi:0
Mar 30 21:48:56 kernel: br0: received packet on eth6 with own address as source address
Mar 30 21:51:56 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 00:13:EF:F2:4B:27, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 21:51:56 wlceventd: wlceventd_proc_event(527): eth6: Auth 00:13:EF:F2:4B:27, status: Successful (0), rssi:0
Mar 30 21:51:56 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 00:13:EF:F2:4B:27, status: Successful (0), rssi:0
Mar 30 21:51:56 kernel: br0: received packet on eth6 with own address as source address
eth6 is my PC im currently writing on.

Known issue. Outside of Merlin's control. Asus simply wont fix it. Set your log level to Normal-Normal and they wont show.
 

skeal

Part of the Furniture
With Cake disabling Trend Micro, how exposed are the routers with JUST the built in firewall?
How did you determine that Trend Micro is disabled by Cake?
 

det721

Part of the Furniture
Thanks for the fast reply.
I can set two different logs. Which one to which setting? I don't see "normal".
Default message log levelemergency alert critical error warning notice info debug
Log only messages more urgent thanalert critical error warning notice info debug all

Thanks for the fast reply.
I can set two different logs. Which one to which setting? I don't see "normal".
Default message log levelemergency alert critical error warning notice info debug
Log only messages more urgent thanalert critical error warning notice info debug all


Sorry it's Notice/Notice
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

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