What's new

[ 386.4 alpha Build(s) ] Testing available build(s)

  • 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.
I don't have the exact same DNS error, but similar problem with this upgrade from 386.4 Alpha 1: I have only IP4 enabled, and my DDNS provider is DNS-O-Matic. This has always worked perfectly in the past, but now I am seeing the yellow exclamation point (on the main index page near the top with the DDNS info) with "Request error! Please try again" when hovering over the exclamation point. Yet when I check the logs of this actual provider, I do see that updates are taking place as scheduled (in other words, I have verified that my login info is correct). Perhaps the return code is indicating that no update is needed, as my IP address hasn't changed, but odd that this exclamation point issue hasn't happened before.

Edit: This issue was resolved with the latest version (Dec.9 or 10th) of 386.4 Alpha 3. New version of inadyn was incorporated.
 
Last edited:
got it running here since posted
okay so far, using as a router, not using service providers DNS but cloudflare, and with ipv6 enabled
 
Last edited:
I don't have the exact same DNS error, but similar problem with this upgrade from 386.4 Alpha 1: I have only IP4 enabled, and my DDNS provider is DNS-O-Matic. This has always worked perfectly in the past, but now I am seeing the yellow exclamation point (on the main index page near the top with the DDNS info) with "Request error! Please try again" when hovering over the exclamation point. Yet when I check the logs of this actual provider, I do see that updates are taking place as scheduled (in other words, I have verified that my login info is correct). Perhaps the return code is indicating that no update is needed, as my IP address hasn't changed, but odd that this exclamation point issue hasn't happened before.

I'm using Google DDNS and I have normal updates with no indication of error in the GUI or anywhere else.
 
yesterday clean flash Alpha 3 and all work just fine, except spdMerlin 4.4.1 from amtm, while install happens this error: Error: near line 1: near ",": syntax error
 
Upgraded AC86U from Alpha1 to Alpha3 yesterday. It is running lot cooler (atleast by 8 deg) than any recent builds. Ambient temp also dropped a bit here but I don't think that's the reason. Looks like it is really running cooler.
 
Asus upgraded the Ookla test client with 45958.
Does that mean it won't run?

Code:
➜ ookla
[2021-11-29 20:34:03.009] [error] ConfigurationError - Could not retrieve or read configuration (Configuration)
{"type":"log","timestamp":"2021-11-29T19:34:03Z","message":"Configuration - Could not retrieve or read configuration (ConfigurationError)","level":"error"}

A manually downloaded version of Speedtest by Ookla 1.0.0.2 (5ae238b) Linux/aarch64-linux-musl 4.1.27 aarch64 runs fine though.
 
Maybe a clean install?

Nov 29 20:38:46 kernel: potentially unexpected fatal signal 6.
Nov 29 20:38:46 kernel: CPU: 0 PID: 4191 Comm: dnsmasq Tainted: P O 4.1.27 #2
Nov 29 20:38:46 kernel: Hardware name: Broadcom-v8A (DT)
Nov 29 20:38:46 kernel: task: ffffffc012c9eb40 ti: ffffffc011690000 task.ti: ffffffc011690000
 
dirty upgrade to Alpha3 from Alpha1. So far it is sailing smooth
 
Is alpha 3 only available for a couple devices? Cannot see a link for ax86u? Cheers
 
Don't look at the OP. Download the firmware and look within.
 
There's no alpha 3 for ax86u as far as I could see.
I’m also waiting on one specific device the ac68u before i update both of my routers
 
Does that mean it won't run?

Code:
➜ ookla
[2021-11-29 20:34:03.009] [error] ConfigurationError - Could not retrieve or read configuration (Configuration)
{"type":"log","timestamp":"2021-11-29T19:34:03Z","message":"Configuration - Could not retrieve or read configuration (ConfigurationError)","level":"error"}

A manually downloaded version of Speedtest by Ookla 1.0.0.2 (5ae238b) Linux/aarch64-linux-musl 4.1.27 aarch64 runs fine though.
I don`t know, I'm not the developer of that addon.
 
@DiGz_Au, then there's nothing to compare. :)
 
Is the alpha 3 a big update from alpha 2? No changelist currently on the op. Cheers
The changes are always on Github for alpha snapshots.

Code:
merlin@ubuntu-dev:~/amng$ git log --oneline 952c6bdecc..7d7073bf09
7d7073bf09 (origin/45958) Bump revision to alpha 3
b454925d96 Update build tools for new models
bd06e54067 Merge RT-AC88U/3100/5300 SDK + binary blobs from 45958
81b1f1ba63 miniupnpd: fix compiling under 2.6 kernel
b35877c914 build: updated copy-prebuilt - added new models, removed old ones improved copy/syncing
4ddcf06932 webui: apply AM general.js changes to the GT-AXE11000 copy
ac145a8417 webui: add 6 GHz support to Wireless Log page
e67e9fe3db webui: add 6G support to Tools Sysinfo page
ad911e3a38 rc: add LED control support to GT-AXE11000
26e8d2b290 httpd: add temperature report for GT-AXE11000
04f67ef827 Merge GT-AXE11000 SDK + binary blobs from 45958
2899e16357 Merged RT-AC68U_V4 binary blobs + SDK from 45958
aa46c15ba6 Updated documentation
4fd55c9770 Enable wireguard module + tool on RT-AC86U/GT-AC2900
79c06ed80c Fix visualization bin location
4abc3bf300 Merge GT-AC2900 binary blobs from 45958
6157117000 Revert "rc: fully disable wanduck DNS probing if disabled on the webui"
d0169015d8 Merge RT-AC86U SDK + binary blobs from 45958
2fa751e1f8 Merge with GPL 386_45958 (from RT-AC86U)
8a77382a6e (origin/master, master) Updated documentation
23e27eb262 (origin/45581, 45581) build: disable the rest of the wireguard code, keeping only kernel + userspace
 
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