What's new

Beta Asuswrt-Merlin 386.1 Beta 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.
Have been using Merlin on a AC68u for years. On that platform have also been running the NordVPN setup without problem using default settings.

Purchased a new AC86u and today updated from stock ASUS firmware and migrated to 386.1 beta 2. Performed factory default resets as recommended and all appeared to go well. Now attempting to again setup VPN using Merlin's OpenVPN Client Settings uploading NordVPN's UDP config file and the VPN appears to install/load flawlessly. Under Service State on the VPN Client tab it states "Connected" with a local and Public IP address listed. BUT - if I go online and request my IP address it still lists my ISP address (Comcast) and at NordVPN's homepage the widget states my "status" as "unprotected". What am I doing wrong or is there a bug?
 
Can someone please confirm that Adaptive QOS with default settings (RUNNER=ENABLED) is generally (still) broken in Beta 2 on RT-AX86U?

I observed that with CakeQoS (RUNNER disabled) the Bandwith Monitor is working - but with default Adaptive QoS or even with FlexQoS - only a few kb traffic are shown.

If I manually disable the Runner via "runner disable" I can see that the Bandwith Monitor and FlexQoS are working again and are showing the right amounts - BUT - even if I disable the runner via CLI - after some minutes, or after every change in settings - its enabling again.

I had the same issue with stock firmware 3.0.0.4.384.9318 2020/10/23 (QoS not working) - why I stayed on 3.0.0.4.384.9298 2020/08/18 until Merlin-Beta1.

Has this to do with the stock GPL "drivers" which are used in the firmwares? I'm not nagging - I just want to understand why this is happening.

Thanks for any inputs.
 
Does this fix the issue with losing the ability to log into the router? I continuously lose the ability to log into the router when it's been up for over a week. When attempting to pull pull up the webgui in any browser it just sits and spins. Rebooting the router fixes the issue. I'm on RT-AC3100 running 384.19
 
The purpose of a Beta release is to test what has been fixed. After flashing and fully resetting it to start from a good/known base. If you want to contribute, please test for this issue on your router and let us (and RMerlin) know too what you find. :)
 
Does this fix the issue with losing the ability to log into the router? I continuously lose the ability to log into the router when it's been up for over a week. When attempting to pull pull up the webgui in any browser it just sits and spins. Rebooting the router fixes the issue. I'm on RT-AC3100 running 384.19

I'm on a 3100 running 384.19, and have been since it was released. I haven't had the issue you described, and I've been running lots of bell and whistles on mine (2 vpn servers, 1 vpn client, ddns, usb file sharing, etc).

I strongly suspect you just need a factory reset.
 
Hi there, not to sound ungrateful or like I'm rushing you guys (love you Merlin!), but is there an ETA for the final release? Mother in law has been complaining about internet issues (she has the Spectrum Router... *Shudders*). Thinking of getting her an AX58U with Merlin for Christmas. Can do 384, but would rather do the latest and greatest if it's available. She's a 4 hour drive away, so having to update after the fact (perhaps with a full reset) isn't doable. Thank you!
 
ANyone know why this is happening. I have been running the router (AX88U) for 4-5 hrs then suddenly it start doing "kernel: protocol 0800 is buggy, dev eth1"
Prior to "Dec 15 08:51:36 RT-AX88U-2340 kernel: Init chrdev /dev/idp with major 190" the log was completely clean.



Dec 15 08:51:36 RT-AX88U-2340 kernel: Init chrdev /dev/idp with major 190
Dec 15 08:51:36 RT-AX88U-2340 kernel: tdts: tcp_conn_max = 8000
Dec 15 08:51:36 RT-AX88U-2340 kernel: tdts: tcp_conn_timeout = 300 sec
Dec 15 08:51:38 RT-AX88U-2340 kernel: SHN Release Version: 2.0.1 4b635f32
Dec 15 08:51:38 RT-AX88U-2340 kernel: UDB Core Version: 0.2.18
Dec 15 08:51:38 RT-AX88U-2340 kernel: Init chrdev /dev/idpfw with major 191
Dec 15 08:51:38 RT-AX88U-2340 kernel: IDPfw: flush fc
Dec 15 08:51:38 RT-AX88U-2340 kernel: IDPfw: IDPfw is ready
Dec 15 08:51:38 RT-AX88U-2340 kernel: sizeof forward pkt param = 280
Dec 15 08:51:38 RT-AX88U-2340 BWDPI: fun bitmap = 3
Dec 15 08:51:38 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:38 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:38 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:43 RT-AX88U-2340 kernel: net_ratelimit: 1121 callbacks suppressed
Dec 15 08:51:43 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
 
Hi there, not to sound ungrateful or like I'm rushing you guys (love you Merlin!), but is there an ETA for the final release? Mother in law has been complaining about internet issues (she has the Spectrum Router... *Shudders*). Thinking of getting her an AX58U with Merlin for Christmas. Can do 384, but would rather do the latest and greatest if it's available. She's a 4 hour drive away, so having to update after the fact (perhaps with a full reset) isn't doable. Thank you!

No way to know for sure when 386.1 will go final but generally Merlin has been updating the Alpha and beta's about once a week on average. If there is no Beta 3 then likely in a week or so. Again just estimating.
 
Hi there, not to sound ungrateful or like I'm rushing you guys (love you Merlin!), but is there an ETA for the final release? Mother in law has been complaining about internet issues (she has the Spectrum Router... *Shudders*). Thinking of getting her an AX58U with Merlin for Christmas. Can do 384, but would rather do the latest and greatest if it's available. She's a 4 hour drive away, so having to update after the fact (perhaps with a full reset) isn't doable. Thank you!
For the same money the AC86U has 3x3 2.4 GHZ and 4x4 5 GHZ while the AX58U is a 2x2 device.
 
ANyone know why this is happening. I have been running the router (AX88U) for 4-5 hrs then suddenly it start doing "kernel: protocol 0800 is buggy, dev eth1"
Prior to "Dec 15 08:51:36 RT-AX88U-2340 kernel: Init chrdev /dev/idp with major 190" the log was completely clean.



Dec 15 08:51:36 RT-AX88U-2340 kernel: Init chrdev /dev/idp with major 190
Dec 15 08:51:36 RT-AX88U-2340 kernel: tdts: tcp_conn_max = 8000
Dec 15 08:51:36 RT-AX88U-2340 kernel: tdts: tcp_conn_timeout = 300 sec
Dec 15 08:51:38 RT-AX88U-2340 kernel: SHN Release Version: 2.0.1 4b635f32
Dec 15 08:51:38 RT-AX88U-2340 kernel: UDB Core Version: 0.2.18
Dec 15 08:51:38 RT-AX88U-2340 kernel: Init chrdev /dev/idpfw with major 191
Dec 15 08:51:38 RT-AX88U-2340 kernel: IDPfw: flush fc
Dec 15 08:51:38 RT-AX88U-2340 kernel: IDPfw: IDPfw is ready
Dec 15 08:51:38 RT-AX88U-2340 kernel: sizeof forward pkt param = 280
Dec 15 08:51:38 RT-AX88U-2340 BWDPI: fun bitmap = 3
Dec 15 08:51:38 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:38 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:38 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:39 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:43 RT-AX88U-2340 kernel: net_ratelimit: 1121 callbacks suppressed
Dec 15 08:51:43 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Dec 15 08:51:44 RT-AX88U-2340 kernel: protocol 0800 is buggy, dev eth1
Check up post #682 in this thread. Worked for me.
 
For the same money the AC86U has 3x3 2.4 GHZ and 4x4 5 GHZ while the AX58U is a 2x2 device.

Been through 2 faulty 86Us myself, so I think I'm done with that line. Figure the 58 is new enough to be supported for a while, and for now no hiccups have come up. She's on either 100mbit or 200 I think, so that should be enough with a 58.
 
No way to know for sure when 386.1 will go final but generally Merlin has been updating the Alpha and beta's about once a week on average. If there is no Beta 3 then likely in a week or so. Again just estimating.
Here's hoping! Will get there the 25th. Thanks!
 
The purpose of a Beta release is to test what has been fixed. After flashing and fully resetting it to start from a good/known base. If you want to contribute, please test for this issue on your router and let us (and RMerlin) know too what you find. :)

Unfortunately I can't as it's my only router and the wife and i both work from home. So beta testing is out of the question. :)
 
is there an ETA for the final release?

There isn't. Whenever I'm satisfied with the current state.

ANyone know why this is happening. I have been running the router (AX88U) for 4-5 hrs then suddenly it start doing "kernel: protocol 0800 is buggy, dev eth1"

Read post #2.
 
For the same money the AC86U has 3x3 2.4 GHZ and 4x4 5 GHZ while the AX58U is a 2x2 device.

AX58U is a 2x4 on the 5GHz band. And what clients do you know of that are greater then 2x2 ?
 
There isn't. Whenever I'm satisfied with the current state.



Read post #2.
Will there be any issues other than the log messages if I leave my guest network set to #1? I have two ax88u, main and node. Need to use aimesh for the node. Moving to 2/3 would defeat the purpose of aimesh 2.0
 
Last edited:
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