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.
@dave14305 you are a smart dude. Running 386.1 Beta 1 on the RT-AX58U, I clicked through the menus without selecting Adaptive QoS and the router appears stable.

I just reflashed 386.1 B1. I dont need or use QOS so will just avoid that tab. Other then that the AX58U is working as expected with the new build.
 
I'm getting this too on my AX-88U. Running one VPN Client on #1 no problem. When I add another client on VPN 2, WAN connection drops. I then have to remove Client #2, then reboot to get WAN back.
I got same problem before I do a WPS reset and reconfigure by hand.
 
Is it possible to see the cpu load and temperature of all nodes in an overview? (administration> temperature)

Everything related to AiMesh is outside of my control.

However, certificate installation actually doesn't work (the browser I use doesn't recognize it), Asus GUI always signal "Waiting for authorization", and the log shows

Try rebooting.

Do we need to factory default reset when 386.1 final will be released?

edit: I mean, coming from this beta to the final release later.

Impossible to predict, as it will depend on whether nvram-related issues are uncovered during the beta cycle.
 
After a dirty flash of beta1 over alpha4 (and a reminder that I did not read the release notes) I did a hard factory reset and reconfigured. Had problems with the Ecobee loosing connection to its server after installing Diversion. Figured that out, fixed my icons, OpenVPN and reserved addresses. Beta 1 is working well. As good as if not better than Alpha 4. Thanks Eric.
 
I'm still having issues after reset to factory defaults. I reset the system to defaults and went out for a while, came back and found the wireless tab to look like this when it's clicked.
ASUS-Wireless-Router-RT-AX88U-General.jpg

I thought it was to do with a bad password, but as you can see it happens with wifi still using open settings. Same thing happens when I configure it right away. Any ideas @RMerlin nothing in the log and nothing in browser console.
 
hm. looks like asus have a custom config and license etc.
i probably can't re-use their binary in spdmerlin

does running /usr/sbin/ookla work without any arguments?

Here is the command line it uses:

ookla -c http://www.speedtest.net/api/embed/vz0azjarf5enop8a/config -f jsonl

You can run it manually with our without the "-f jsonl". Without it, it looks similar to our present ookla speedtest output. With it, lots of output for the fancy dynamic web graphics.

If you go to the weblink, I believe you get a list of local servers.
Unfortunately, there does appear to be a license key and reference to asus as the customer in the file:

threadnum = "8"
packetlength = "32000000"
testlength = "10"
latencytestlength = "5"
uploadfirst = "0"
tracelevel = "2"
licensekey = "91de3bf65fd6ab00-C839c494e00163288-1dddf644be8b9b06"
customer = "asus"
apiurl = "https://www.speedtest.net/api/embed/api.php"
isp = "Spectrum"

servers = [
{
serverid = "14233"
host = "rochester.ny.speedtest.frontier.com:8080"
name = "Rochester, NY"
country = "United States"
sponsor = "Frontier"
},{
serverid = "14148"
host = "speedtest.rit.edu:8080"
name = "Rochester, NY"
country = "United States"
sponsor = "Rochester Institute of Technology"
},{
serverid = "1239"
host = "speedtest-roc.synoptekcloud.com:8080"
name = "Rochester, NY"
country = "United States"
sponsor = "Synoptek"
},{
serverid = "24883"
host = "speedtest.empireaccess.com:8080"
name = "Prattsburgh, NY"
country = "United States"
sponsor = "Empire Access"
},{
serverid = "9276"
host = "192.3.206.14:8080"
name = "Buffalo, NY"
country = "United States"
sponsor = "ColoCrossing"
},{
serverid = "31483"
host = "st.buf.as201971.net:8080"
name = "Buffalo, NY"
country = "United States"
sponsor = "CreeperHost LTD"
},{
serverid = "6989"
host = "speedtest.nyroc.rr.com:8080"
name = "Syracuse, NY"
country = "United States"
sponsor = "Time Warner Cable"
},{
serverid = "16978"
host = "speedtest.nyroc.rr.com:8080"
name = "Syracuse, NY"
country = "United States"
sponsor = "Spectrum"
},{
serverid = "7093"
host = "speedtest-syr1.northland.net:8080"
name = "Syracuse, NY"
country = "United States"
sponsor = "Northland Communications"
},{
serverid = "34363"
host = "speedtest.sparkrack.com:8080"
name = "Cicero, NY"
country = "United States"
sponsor = "Spark Rack"
}
]
 
-Once updated, my custom certificate would not load. After several checks it seems that now ECC keys are not supported, only RSA certs. In the previous version there was no problem with using an ECC certificate.

Are you sure? Because I never implemented any ECC support to httpd.

QoS Class page does not show any graphs or rates. It does appear perfectly below the classifications made to traffic, but not graph or rates. Tested with several browsers, and nothing to highlight in their console or log. Maybe related to FlexQoS or dirty Flash?

Re-test without any third party script.

The router then crashed and rebooted. So yes, it appears the Adaptive QoS is the stinker. @RMerlin it looks like the culprit is the Adaptive QoS causing the router crashes. Thanks @dave14305 for the great idea.

Can you check the crashlog entries in your System Log?
 
@dave14305 you are a smart dude. Running 386.1 Beta 1 on the RT-AX58U, I clicked through the menus without selecting Adaptive QoS and the router appears stable. I then clicked on but did not change the menu options for Adaptive QoS and noticed these new processes running

I was verifying this just as the follow ups were posted. I'm using traditional QOS and can't get my AX58U to crash no matter how many different things I clicked. Sounds like the issue is confirmed, good job reporting this.
 
I updated my AX88U and 2 AX58u mesh nodes to B1 coming from Alpha 4.

Following @RMerlin first note under Upgrade notes (the one that says must) I did a factory reset on all 3 using the WPS button.

Reconnected the 2 AX58 nodes to the AX88U - all running well.

There's times for "dirty" flashes and times for not. This one is a not ;-)
 
Installed 386.1 Beta on my AX86U.

Everything seems fine so far - I'm very happy - only one thing is odd - the CPU Statistics are crazy - spiking around the whole time in "idle" - BUT with HTOP there are no services or things with high CPU usage - so it seems to me it's just a visual bug ?!

1607284772587.png
1607285150701.png
 
Are you sure? Because I never implemented any ECC support to httpd.



Re-test without any third party script.



Can you check the crashlog entries in your System Log?
Yes. I also uploaded the crash logs yesterday at https://www.snbforums.com/threads/a...eta-is-now-available.68205/page-3#post-638721

In the crashlog from today, I can see BWDPI in there just before the crash. If there is something else you'd like me to provide or look for let me know and I'll do it.

Dec 6 12:07:11 kernel: Init chrdev /dev/idp with major 190
Dec 6 12:07:11 kernel: tdts: tcp_conn_max = 8000
Dec 6 12:07:11 kernel: tdts: tcp_conn_timeout = 300 sec
Dec 6 12:07:16 kernel: SHN Release Version: 2.0.1 4b635f32
Dec 6 12:07:16 kernel: UDB Core Version: 0.2.18
Dec 6 12:07:16 kernel: Init chrdev /dev/idpfw with major 191
Dec 6 12:07:16 kernel: IDPfw: flush fc
Dec 6 12:07:16 kernel: IDPfw: IDPfw is ready
Dec 6 12:07:16 kernel: sizeof forward pkt param = 192
Dec 6 12:07:16 BWDPI: fun bitmap = 3
May 5 00:05:08 syslogd started: BusyBox v1.25.1
May 5 00:05:08 crashlog: LOG
May 5 00:05:08 crashlog: <6>console [ttyAMA0] enabled
May 5 00:05:08 crashlog: <6>bootconsole [earlycon0] disabled
May 5 00:05:08 crashlog: <4>Broadcom Logger v0.1
May 5 00:05:08 crashlog: <6>bcmhs_spi bcmhs_spi.1: master is unqueued, this is deprecated
May 5 00:05:08 crashlog: <4>skb_free_task created successfully with start budget 256
May 5 00:05:08 crashlog: <4>^[[0;34mBLOG v3.0 Initialized^[[0m
May 5 00:05:08 crashlog: <4>BLOG Rule v1.0 Initialized
May 5 00:05:08 crashlog: <4>Broadcom IQoS v1.0 initialized
 
In the crashlog from today, I can see BWDPI in there just before the crash. If there is something else you'd like me to provide or look for let me know and I'll do it.

For reference, this is what I needed:

Code:
May  5 01:05:08 crashlog: <6>Init chrdev /dev/idp with major 190
May  5 01:05:08 crashlog: <6>tdts: tcp_conn_max = 8000
May  5 01:05:08 crashlog: <6>
May  5 01:05:08 crashlog: <6>tdts: tcp_conn_timeout = 300 sec
May  5 01:05:08 crashlog: <6>
May  5 01:05:08 crashlog: <4>SHN Release Version: 2.0.1 4b635f32
May  5 01:05:08 crashlog: <4>UDB Core Version: 0.2.18
May  5 01:05:08 crashlog: <6>Init chrdev /dev/idpfw with major 191
May  5 01:05:08 crashlog: <6>IDPfw: flush fc
May  5 01:05:08 crashlog: <6>
May  5 01:05:08 crashlog: <6>IDPfw: IDPfw is ready
May  5 01:05:08 crashlog: <4>sizeof forward pkt param = 192
May  5 01:05:08 crashlog: <6>IDPfw: Exit IDPfw
May  5 01:05:08 crashlog: <6>mod epilog takes 0 jiffies
May  5 01:05:08 crashlog: <6>IDPfw: Exit IDPfw
May  5 01:05:08 crashlog: <6>Exit chrdev /dev/idpfw with major 191
May  5 01:05:08 crashlog: <6>Exit chrdev /dev/idp with major 190
May  5 01:05:08 crashlog: <1>Unable to handle kernel NULL pointer dereference at virtual address 00000002
May  5 01:05:08 crashlog: <1>pgd = c0014000
May  5 01:05:08 crashlog: <1>[00000002] *pgd=00000000
May  5 01:05:08 crashlog: <0>Internal error: Oops: 17 [#1] PREEMPT SMP ARM
May  5 01:05:08 crashlog: <4>CPU: 0 PID: 239 Comm: bcmsw_rx Tainted: P           O    4.1.52 #1
May  5 01:05:08 crashlog: <4>Hardware name: Generic DT based system
May  5 01:05:08 crashlog: <4>task: d772c800 ti: d77b2000 task.ti: d77b2000
May  5 01:05:08 crashlog: <4>PC is at br_dev_xmit+0xe0/0x3d4
May  5 01:05:08 crashlog: <4>LR is at br_dev_xmit+0x94/0x3d4
May  5 01:05:08 crashlog: <4>pc : [<c04359e0>]    lr : [<c0435994>]    psr: 000c0013
May  5 01:05:08 crashlog: <4>sp : d77b3ae8  ip : 00000000  fp : deecaf8e
May  5 01:05:08 crashlog: <4>r10: deecaf80  r9 : d4b314c0  r8 : c0665ad0
May  5 01:05:08 crashlog: <4>r7 : d4b31000  r6 : 00000000  r5 : deecae43  r4 : fede8dc8
May  5 01:05:08 crashlog: <4>r3 : 000002b6  r2 : 0000015b  r1 : 0000ffff  r0 : 0001eb44
May  5 01:05:08 crashlog: <4>Flags: nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
May  5 01:05:08 crashlog: <4>Control: 10c5387d  Table: 1378404a  DAC: 00000015
May  5 01:05:08 crashlog: <0>Process bcmsw_rx (pid: 239, stack limit = 0xd77b2210)
May  5 01:05:08 crashlog: <4>Modules linked in: nf_nat_sip init_addr(  (null) -   (null)), core_addr(bf0c7000 - bf0c86d0)
May  5 01:05:08 crashlog: <4> nf_conntrack_sip init_addr(  (null) -   (null)), core_addr(bf129000 - bf12bdbc)
May  5 01:05:08 crashlog: <4> nf_nat_h323 init_addr(  (null) -   (null)), core_addr(bf0b1000 - bf0b1f50)
May  5 01:05:08 crashlog: <4> nf_conntrack_h323 init_addr(  (null) -   (null)), core_addr(bf0f7000 - bf0fa8d4)
May  5 01:05:08 crashlog: <4> nf_nat_rtsp init_addr(  (null) -   (null)), core_addr(bf0ad000 - bf0ad830)
May  5 01:05:08 crashlog: <4> nf_conntrack_rtsp init_addr(  (null) -   (null)), core_addr(bf06a000 - bf06b208)
May  5 01:05:08 crashlog: <4> nf_nat_ftp init_addr(  (null) -   (null)), core_addr(bf010000 - bf010228)
May  5 01:05:08 crashlog: <4> nf_conntrack_ftp init_addr(  (null) -   (null)), core_addr(bf005000 - bf005b88)
May  5 01:05:08 crashlog: <4> thfsplus(O) init_addr(  (null) -   (null)), core_addr(bf1ab000 - bf1b6c10)
May  5 01:05:08 crashlog: <4> tntfs(PO) init_addr(  (null) -   (null)), core_addr(bfd69000 - bfdb78fc)
May  5 01:05:08 crashlog: <4> tfat(PO) init_addr(  (null) -   (null)), core_addr(bfd1a000 - bfd4bf54)
May  5 01:05:08 crashlog: <4> uas init_addr(  (null) -   (null)), core_addr(bfd13000 - bfd14d48)
May  5 01:05:08 crashlog: <4> usb_storage init_addr(  (null) -   (null)), core_addr(bfd00000 - bfd03824)
May  5 01:05:08 crashlog: <4> sg init_addr(  (null) -   (null)), core_addr(bfcf5000 - bfcf8e80)
May  5 01:05:08 crashlog: <4> sd_mod init_addr(  (null) -   (null)), core_addr(bfce9000 - bfced840)
May  5 01:05:08 crashlog: <4> scsi_mod init_addr(  (null) -   (null)), core_addr(bfcba000 - bfcc8a54)
May  5 01:05:08 crashlog: <4> cdc_mbim init_addr(  (null) -   (null)), core_addr(bfcb5000 - bfcb5a70)
May  5 01:05:08 crashlog: <4> qmi_wwan init_addr(  (null) -   (null)), core_addr(bfcac000 - bfcac688)
May  5 01:05:08 crashlog: <4> cdc_wdm init_addr(  (null) -   (null)), core_addr(bfca7000 - bfca85b8)
May  5 01:05:08 crashlog: <4> cdc_ncm init_addr(  (null) -   (null)), core_addr(bfc9f000 - bfca0fb8)
May  5 01:05:08 crashlog: <4> rndis_host init_addr(  (null) -   (null)), core_addr(bfc9a000 - bfc9ab0c)
May  5 01:05:08 crashlog: <4> cdc_ether init_addr(  (null) -   (null)), core_addr(bfc96000 - bfc9677c)
May  5 01:05:08 crashlog: <4> ax88179_178a init_addr(  (null) -   (null)), core_addr(bfc8e000 - bfc90544)
May  5 01:05:08 crashlog: <4> asix init_addr(  (null) -   (null)), core_addr(bfc85000 - bfc87510)
May  5 01:05:08 crashlog: <4> libphy init_addr(  (null) -   (null)), core_addr(bfc7a000 - bfc7cf84)
May  5 01:05:08 crashlog: <4> cdc_acm init_addr(  (null) -   (null)), core_addr(bfc71000 - bfc731fc)
May  5 01:05:08 crashlog: <4> usbnet init_addr(  (null) -   (null)), core_addr(bfc67000 - bfc69ecc)
May  5 01:05:08 crashlog: <4> mii init_addr(  (null) -   (null)), core_addr(bfc63000 - bfc639e4)
May  5 01:05:08 crashlog: <4> ohci_pci init_addr(  (null) -   (null)), core_addr(bfc5f000 - bfc5f1f4)
May  5 01:05:08 crashlog: <4> ohci_platform init_addr(  (null) -   (null)), core_addr(bfc5b000 - bfc5b6c0)
May  5 01:05:08 crashlog: <4> ohci_hcd init_addr(  (null) -   (null)), core_addr(bfc50000 - bfc54b58)
May  5 01:05:08 crashlog: <4> ehci_pci init_addr(  (null) -   (null)), core_addr(bfc4c000 - bfc4c584)
May  5 01:05:08 crashlog: <4> ehci_platform init_addr(  (null) -   (null)), core_addr(bfc47000 - bfc4773c)
May  5 01:05:08 crashlog: <4> ehci_hcd init_addr(  (null) -   (null)), core_addr(bfc3a000 - bfc41224)
May  5 01:05:08 crashlog: <4> xhci_pci init_addr(  (null) -   (null)), core_addr(bfc36000 - bfc3659c)
May  5 01:05:08 crashlog: <4> xhci_plat_hcd init_addr(  (null) -   (null)), core_addr(bfc32000 - bfc324a0)
May  5 01:05:08 crashlog: <4> xhci_hcd init_addr(  (null) -   (null)), core_addr(bfc16000 - bfc25234)
May  5 01:05:08 crashlog: <4> bcm_usb init_addr(  (null) -   (null)), core_addr(bfc11000 - bfc110b8)
May  5 01:05:08 crashlog: <4> usbcore init_addr(  (null) -   (null)), core_addr(bfbe4000 - bfbf9250)
May  5 01:05:08 crashlog: <4> usb_common init_addr(  (null) -   (null)), core_addr(bfbe0000 - bfbe0170)
May  5 01:05:08 crashlog: <4> dhd init_addr(  (null) -   (null)), core_addr(bfb09000 - bfb73ca8)
May  5 01:05:08 crashlog: <4> wl(P) init_addr(  (null) -   (null)), core_addr(bf259000 - bf683c78)
May  5 01:05:08 crashlog: <4> dpsta(P) init_addr(  (null) -   (null)), core_addr(bf217000 - bf2196d8)
May  5 01:05:08 crashlog: <4> cfg80211 init_addr(  (null) -   (null)), core_addr(bf1dd000 - bf1ff23c)
May  5 01:05:08 crashlog: <4> igs(P) init_addr(  (null) -   (null)), core_addr(bf1d4000 - bf1d6ed4)
May  5 01:05:08 crashlog: <4> emf(P) init_addr(  (null) -   (null)), core_addr(bf1cc000 - bf1ce764)
May  5 01:05:08 crashlog: <4> hnd init_addr(  (null) -   (null)), core_addr(bf15d000 - bf18c648)
May  5 01:05:08 crashlog: <4> otp(P) init_addr(  (null) -   (null)), core_addr(bf159000 - bf159504)
May  5 01:05:08 crashlog: <4> bcm_thermal init_addr(  (null) -   (null)), core_addr(bf154000 - bf1547b4)
May  5 01:05:08 crashlog: <4> pwrmngtd(P) init_addr(  (null) -   (null)), core_addr(bf150000 - bf150480)
May  5 01:05:08 crashlog: <4> bcm_pcie_hcd init_addr(  (null) -   (null)), core_addr(bf143000 - bf147fb4)
May  5 01:05:08 crashlog: <4> bcmmcast init_addr(  (null) -   (null)), core_addr(bf12f000 - bf13852c)
May  5 01:05:08 crashlog: <4> bcm_enet init_addr(  (null) -   (null)), core_addr(bf102000 - bf1187bc)
May  5 01:05:08 crashlog: <4> archer(P) init_addr(  (null) -   (null)), core_addr(bf0ca000 - bf0e3f38)
May  5 01:05:08 crashlog: <4> cmdlist(P) init_addr(  (null) -   (null)), core_addr(bf0b4000 - bf0bf1dc)
May  5 01:05:08 crashlog: <4> pktflow(P) init_addr(  (null) -   (null)), core_addr(bf06e000 - bf093424)
May  5 01:05:08 crashlog: <4> bcm_ingqos(P) init_addr(  (null) -   (null)), core_addr(bf034000 - bf037ac8)
May  5 01:05:08 crashlog: <4> chipinfo(P) init_addr(  (null) -   (null)), core_addr(bf030000 - bf030104)
May  5 01:05:08 crashlog: <4> bcmvlan(P) init_addr(  (null) -   (null)), core_addr(bf012000 - bf01fa10)
May  5 01:05:08 crashlog: <4> bcmlibs(P) init_addr(  (null) -   (null)), core_addr(bf008000 - bf00a47c)
May  5 01:05:08 crashlog: <4> wlcsm(P) init_addr(  (null) -   (null)), core_addr(bf000000 - bf0011ac)
May  5 01:05:08 crashlog: <4> [last unloaded: tdts]

The crash occurs in bcmsw_rx, which indicate the issue has nothing to do with browsing web settings or even bwdpi itself - the crash occurs in the Broadcom drivers, possibly tied to hardware acceleration (a few lines before bwdpi tried to flush the flowcache tables).
 
It seems that the wireless page issue I was having was centered around WPA3. When the WPA3 is selected in any way my page ends up reformatted and unresponsive. Changed the setting to WPA2 personal and all is well.
When I click on client list it freezes my GUI, When I apply settings on the wireless tab it freezes or reboots somehow and is unresponsive for a while.
This is on my AX88U. I would have to say that the Beta is a work in progress, some bugs to iron out.
 
No. The problem is these alpha builds have some invalid nvram values.
well i updated with no factory reset so far no problems , of course i jusrt use the rt5300 as a router no scripts or mesh , hope i don't have to factory rest
 
Is your AI-Mesh connection wired or wireless? Some users reported earlier that they had to setup AI-Mesh wired and once that was working, they were able to connect wireless.

I tried both ways
 
well i updated with no factory reset so far no problems , of course i jusrt use the rt5300 as a router no scripts or mesh , hope i don't have to factory rest

The biggest problem is related to MTU. If you go to the WAN page and make sure the MTU is set to 1500 after you are on beta 1 then in theory you should be fine, but I can't guarantee it 100% as there might be other nvram settings that are problematic if you ran an alpha build.

Symptoms of an incorrect MTU can be flat out weird at times. For instance, OpenVPN clients will fail to connect over UDP but work fine over TCP if your MTU is misconfigured (i.e. if your WAN has a default MTU of 576, then UDP packet fragmentation will break everything).
 
My first attempt to upgrade from 384.19 to 386.1 Beta 1 failed because I accidentally downloaded the AX86U firmware instead of the AC86U variant... (minor disadvantage of that new model now being supported ;))

Forgot about the guest network changes, but apparently my IoT devices on 2.4 GHz network 1 all still have the IP address I manually assigned them via the DHCP server tab.

Maybe because I allow intranet access for this particular guest network?
 
I still can't flash any of these new 386 firmwares on my AX58u, the router just reboots. Only resetting the router allows me to upgrade. I've attached my syslog with the crashlog if anybody wants to take a look and decipher whats going on.
 
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