Release Asuswrt-Merlin 386.1 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.

XIII

Very Senior Member
Currently not on my local network and can't log in remotely on my router via SSH (though I thought I enabled that).

I can still remotely log in to a Pi connected to the router and from there "locally" log in to the router.

Which nvram variable should I check to see whether I enabled/disabled SSH over WAN?

And which service do I need to restart after changing that variable's value?
 

Rango

Senior Member
No more AC-87U Merlin updates?

What is the latest scoop?

Thank you in advance.
 

chongnt

Regular Contributor
Can anyone help to see what these messages means?
Code:
Feb 21 20:43:43 RT-AC86U-DBA8 kernel: Init chrdev /dev/idp with major 190
Feb 21 20:43:43 RT-AC86U-DBA8 kernel: tdts: tcp_conn_max = 8000
Feb 21 20:43:43 RT-AC86U-DBA8 kernel: tdts: tcp_conn_timeout = 300 sec
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: SHN Release Version: 2.0.1 851496c
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: UDB Core Version: 0.2.18
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: Init chrdev /dev/idpfw with major 191
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: IDPfw: flush fc
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: IDPfw: IDPfw is ready
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: sizeof forward pkt param = 280
Feb 21 20:43:46 RT-AC86U-DBA8 BWDPI: fun bitmap = 3

I don't use any of the Trend Micro services. Before the messages, there is no BWDPI_FILTER in PreRouting output. It only appears after the above messages. I don't have QoS setting too.

Code:
[email protected]:/jffs/Div_list# iptables -nvL PREROUTING -t mangle --line
Chain PREROUTING (policy ACCEPT 20647 packets, 23M bytes)
num   pkts bytes target     prot opt in     out     source               destination         
1        0     0 MARK       all  --  br0    *       0.0.0.0/0            0.0.0.0/0            match-set WAN_IP dst MARK or 0x8000
2      323 37631 MARK       all  --  br0    *       0.0.0.0/0            0.0.0.0/0            match-set VPN_IP dst MARK or 0x1000
3        0     0 MARK       all  --  tun22  *       0.0.0.0/0            0.0.0.0/0            match-set Astro dst MARK or 0x8000
4     1059 52611 MARK       all  --  br0    *       0.0.0.0/0            0.0.0.0/0            match-set Astro dst MARK or 0x8000
5     962K  764M BWDPI_FILTER  udp  --  ppp0   *       0.0.0.0/0            0.0.0.0/0
 

NX3

Occasional Visitor
Thanks for the responce. Ok so I need to reset it I guess to get control back or do anything, I can't see any other option but loathed to do that without making a note of all the settings.
To self reply, I got in saved settings factory reset but put back together and all running well now. Thanks.
 

maxbraketorque

Very Senior Member
Amazon has fans specifically for routers powered by the usb ports. I use them on all my routers, makes a big difference in temps.

https://www.amazon.com/gp/product/B07ZYY91YP/?tag=snbforums-20

https://www.amazon.com/dp/B0721SYYTF/?tag=snbforums-20

I've got a fan setup like those for one of my AC86Us. I also have another AC86U with the fan in the link below. It snaps in place rather than requiring tape, screws or velcro. And it has an adjustable speed and dust filter. Its very nifty. Delivery time was much faster than indicated on the Amazon website.

https://www.amazon.com/gp/product/B07XDGXWC3/?tag=snbforums-20
 

bluepoint

Very Senior Member
Can anyone help to see what these messages means?
Code:
Feb 21 20:43:43 RT-AC86U-DBA8 kernel: Init chrdev /dev/idp with major 190
Feb 21 20:43:43 RT-AC86U-DBA8 kernel: tdts: tcp_conn_max = 8000
Feb 21 20:43:43 RT-AC86U-DBA8 kernel: tdts: tcp_conn_timeout = 300 sec
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: SHN Release Version: 2.0.1 851496c
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: UDB Core Version: 0.2.18
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: Init chrdev /dev/idpfw with major 191
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: IDPfw: flush fc
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: IDPfw: IDPfw is ready
Feb 21 20:43:46 RT-AC86U-DBA8 kernel: sizeof forward pkt param = 280
Feb 21 20:43:46 RT-AC86U-DBA8 BWDPI: fun bitmap = 3

I don't use any of the Trend Micro services. Before the messages, there is no BWDPI_FILTER in PreRouting output. It only appears after the above messages. I don't have QoS setting too.

Code:
[email protected]:/jffs/Div_list# iptables -nvL PREROUTING -t mangle --line
Chain PREROUTING (policy ACCEPT 20647 packets, 23M bytes)
num   pkts bytes target     prot opt in     out     source               destination       
1        0     0 MARK       all  --  br0    *       0.0.0.0/0            0.0.0.0/0            match-set WAN_IP dst MARK or 0x8000
2      323 37631 MARK       all  --  br0    *       0.0.0.0/0            0.0.0.0/0            match-set VPN_IP dst MARK or 0x1000
3        0     0 MARK       all  --  tun22  *       0.0.0.0/0            0.0.0.0/0            match-set Astro dst MARK or 0x8000
4     1059 52611 MARK       all  --  br0    *       0.0.0.0/0            0.0.0.0/0            match-set Astro dst MARK or 0x8000
5     962K  764M BWDPI_FILTER  udp  --  ppp0   *       0.0.0.0/0            0.0.0.0/0
You'll see the kernel prompt(log) when you access "Adapttive QOS" then exit from it, that's normal.
 

scottegos2

Occasional Visitor
So, try as I may, and after trying both 386.2alpha and, now 386.1_2 release, as well as the related ASUS 9.9.9.4_386 release, this release is still FUBAR. Literally every other time I hit the "apply" key to make any change whatsoever -- latest being to enable and then disable MAC filtering -- my RT-AC5300 crashes. Symptoms: Power and LAN LEDs turn off (other three stay on and white) and router is otherwise completely dead until I power cycle it. Only oddity in the log (and I have no idea whether this is normal for this firmware) is that the reboot logs as May 5 0:0 until after ntpd kicks in and fixes the time up again (log times before reboot are all nominal). NONE of this ever happens with 384.19, to which I have reverted. I have, as I had mentioned in earlier posts, done a complete reset and manual entry of my relatively few non-default settings. I don't THINK this happened with 386.1 beta 3, though I wouldn't swear it. Could someone please help???
 

GregS

Occasional Visitor
Wrong interface? On my AX88 5G WLAN is on eth7 and 2.4G on eth6 and wl commands works fine there..
Did you enable wl0.1 (guest network)? There are currently some (logging) issues with guest 1 - maybe you run into another problem... :rolleyes:
Whoops, you're right, I disabled Guest Network 1 due to the log spamming. Already had forgotten, thanks.
 

XIII

Very Senior Member
Currently not on my local network and can't log in remotely on my router via SSH (though I thought I enabled that).

I did enable it, but as soon as I log out and back in again it reverts to “LAN only”.

Is this a known bug of this release? (On AC86u)
 

jomcty

Occasional Visitor
I'm facing a problem with RT-AC86U where the devices is unable to connect to 2.4GHz after a certain time (from days to weeks). I can see the SSID but it just refused to connect.
I have no problem with 5GHz. This issues seems to begin from 384.18 onwards and now I'm on 386.1_2 and it's still happening.
By the time I notice the problem and view the logs, its already rolled over.

Any method or any logs I can check for the issue?


Code:
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind B0:95:75:70:B0:4E, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 28:6C:07:B9:00:A2, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 28:6C:07:B9:00:A2, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind B0:95:75:70:B0:4E, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 28:6C:07:B9:00:A2, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 00:03:7F:77:0D:76, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 00:03:7F:77:0D:76, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 00:03:7F:77:0D:76, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind B0:95:75:70:B0:4E, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 34:CE:00:FB:63:2C, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind B0:95:75:70:B0:4E, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 34:CE:00:FB:63:2C, status: Successful (0), rssi:0
Feb 20 14:46:02 wlceventd: wlceventd_proc_event(526): eth5: Auth 34:CE:00:FB:63:2C, status: Successful (0), rssi:0
Feb 20 14:46:02 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind B0:95:75:70:B0:4E, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:02 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:02 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Try manually assigning your 2.4 MHz channel to the one with the least signal. I had this problem with my IoT Nexx Garage Opener until did that.
 

XIII

Very Senior Member
I did enable it, but as soon as I log out and back in again it reverts to “LAN only”.

Is this a known bug of this release? (On AC86u)

Apparently this is configured by nvram variable sshd_enable.

Even after setting it manually to 1 ("LAN & WAN") via SSH (and restarting sshd), I cannot log in via SSH remotely.

EDIT: I can log in remotely via SSH once and then the variable sshd_enable is reset to 2... remote log in via SSH fails again.

Can somebody else please test/verify this?
 
Last edited:

XIII

Very Senior Member
OOPS: I forgot that I had done a factory reset and Skynet was still set to Secure Mode (which disables WAN access).

However, even disabling Secure Mode does not help.

EDIT: Seems solved after upgrading to 386.1 Alpha 2 and/or unbanning my (external) IP in Skynet?
 
Last edited:

fitnesspmm

Regular Contributor
Everything fine except my Swann Security Cameras lag and drop out, any suggestions on how to fix?

I think I'll go back to 384.18, I found no issues with this version compared to the new versions.
 

scarzy

Occasional Visitor
I've got a fan setup like those for one of my AC86Us. I also have another AC86U with the fan in the link below. It snaps in place rather than requiring tape, screws or velcro. And it has an adjustable speed and dust filter. Its very nifty. Delivery time was much faster than indicated on the Amazon website.

https://www.amazon.com/gp/product/B07XDGXWC3/?tag=snbforums-20
This looks great! I noticed one of the reviews says this fan did not fit on the AC2900 (AC86u). Can you confirm you are using this fan as intended by snapping in place on a RT-AC86u? I just wanted to check before placing an order. Any idea how many degrees this dropped your CPU temperature? Thanks for your help!
 

maxbraketorque

Very Senior Member
This looks great! I noticed one of the reviews says this fan did not fit on the AC2900 (AC86u). Can you confirm you are using this fan as intended by snapping in place on a RT-AC86u? I just wanted to check before placing an order. Any idea how many degrees this dropped your CPU temperature? Thanks for your help!

Yes, it fits my AC86U as intended, and the air flow ports on the back of the router match up with the air flow ports on the fan assembly. The GT-AC2900 has different air flow ports.


 

lala_cai

Occasional Visitor
Try manually assigning your 2.4 MHz channel to the one with the least signal. I had this problem with my IoT Nexx Garage Opener until did that.
Normally I’ll just fixed to channel 1 after the initial reset. Will try to fixed it to other channel and see if this is still happening.
 
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

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