[Beta] Asuswrt-Merlin 384.14 Beta is now available

[JohnSmith]

Upgrade RT-AX88U & RT-AC3100 from V384.14_beta1 to V384.14_beta2 via dirty firmware upgrade. 30+ devices and all appears to be working for main AX88U router.

 

[HyperCris]

No issues detected. 30% improvement on Wireless 2.4ghz. Running smooth.
Error found in the log's, but do not affect the operation.

Nov 25 06:53:52 start_ddns: update WWW.ASUS.COM update@asus.com, wan_unit 0
Nov 25 06:53:52 inadyn[1467]: In-a-dyn version 2.5 -- Dynamic DNS update client.
Nov 25 06:53:52 inadyn[1467]: /etc/inadyn.conf:4: unexpected token '='
Nov 25 06:53:52 inadyn[1467]: Parse error in /etc/inadyn.conf
Nov 25 06:53:52 inadyn[1467]: Error code 74: Missing .conf file

Out of curiosity why the 2.4 GHz band should be improved? I wonder which new feature or tweak could make the signal stronger or more stable.

 

[Sebastien Bougie]

Completed a dirty upgrade over B1 to B2 (Main only), and glad to report I haven't noticed a single issue yet (27 clients connected). My current setup (AiMesh), is in my signature. I have also tried multiple reboots via the GUI and completed some test schedule reboots, and at least so far, my 86U Main, has rebooted every time, would seem the reboot/schedule reboot issue (hang), may also be fixed with the 86U.

For AiMesh, I am only using the roaming assistant and not smart connect. A quick test of the roaming for me, also is working, with walking between my nodes, switching between the nodes is occurring without any issue, for both Android and Apple mobile devices, same SID for both bands.

Had a play with WI-FI radar also, has no issues, client list also stable.

My general log is also quiet with the settings level of "notice" for both log entry types. I use no scripting and or VPN. My setup is pretty basic, no AiProtection and no Adaptive QoS also. Chanel's are fixed and using a set bandwidth.

Thanks Merlin.....without your continued support, I for one, wouldn't be using ASUS without your dedication to your firmware support.

Will edit this post if I see anything over the next few days.[/QUOTE

Hello

Do you think you can share your roaming assist settings

Thanks

 

[Butterfly Bones]

Here is a new one, I have never seen this before.

nslookup: getaddrinfo*.gaih_getanswer: got type "HINFO"

They are coming at about 4-5 per second, for the last half hour, but no effect on router performance that I can see. Google search and SNB search get zero results, which is rare indeed!

Well, the attempts are changing now.

Nov 25 13:01:26 RT-AC86U-4608 nslookup: getaddrinfo*.gaih_getanswer: got type "HINFO"
Nov 25 13:01:27 RT-AC86U-4608 ping: getaddrinfo*.gaih_getanswer: got type "HINFO"
Nov 25 13:01:31 RT-AC86U-4608 curl: getaddrinfo*.gaih_getanswer: got type "HINFO"

 

[RAH-66]

ASUS RT-AX88U Firmware version 3.0.0.4.384.7756

 

[gburlingame]

I just updated from beta 1 to beta 2 on a RT-AC88U.

I noticed this popping up in the System Log every few minutes. Sometimes a single entry, sometimes multiple bursts.

Nov 25 06:28:44 dnsmasq-script[314]: connect error: No such file or directory
Nov 25 06:28:44 dnsmasq-script[314]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.

It's probably nothing, but I thought I should report it.

Cheers!

Just curious, is anyone else seeing this error message in their system logs?

If others are seeing this I will just leave it alone, but if not I will spend some time trying to sort out what is causing it.

Thanks!

 

[RMerlin]

Why the expired certificate yet everything in the log looks fine?

Asus fixed the certificate last night (it's still missing the nwsrv-ns1 SAN however).

Had to reboot my AC88U because after the dirty flash from beta 1 my USB drive was not mounted. After a reboot it seems to be fixed.

Something new I noticed..:

"Your router will be automatically upgraded to the latest firmware at night. Or you can check your firmware version by visiting Administration > Firmware Upgrade page and decide if updating the latest firmware version to your router."

Noticed where? My firmware does not support auto-upgrade, so that message should only appear with the stock firmware.

 

[skeal]

Asus fixed the certificate last night.

So is this ok? Or.....? Do I have something messed up?

 

[RMerlin]

Well, the attempts are changing now.

Nov 25 13:01:26 RT-AC86U-4608 nslookup: getaddrinfo*.gaih_getanswer: got type "HINFO"
Nov 25 13:01:27 RT-AC86U-4608 ping: getaddrinfo*.gaih_getanswer: got type "HINFO"
Nov 25 13:01:31 RT-AC86U-4608 curl: getaddrinfo*.gaih_getanswer: got type "HINFO"

Check your installed add-ons. I can't even find the gaih_getanswer string through the whole source code.

EDIT: found it, it's within libnss_dns.so. No idea what it means, a few references to it on the web, sounds like debugging output tied to the resolver. It's apparently tied to DNSSEC.

EDIT2: looks like debugging output left behind in libnss, as per https://marc.info/?l=glibc-alpha&m=146176688926759&w=2 .

 

[RMerlin]

So is this ok? Or.....? Do I have something messed up?

There is nothing to do from the end-user's point of view. Beta 2 instructs inadyn to ignore any certificate error when dealing with Asus DDNS (other providers will still have their certificate validated at update time).

 

[easyriider]

Since the update from beta1 to beta2 I have this acsd lines in my log which I have never seen before:

Nov 25 13:28:52 acsd: selected channel spec: 0xd92e (48u)
Nov 25 13:28:52 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 13:28:52 acsd: selected channel spec: 0xd92e (48u)
Nov 25 13:28:54 acsd: eth6: NONACSD channel switching to channel spec: 0xd92e (48u)
Nov 25 13:43:58 acsd: selected channel spec: 0xd92e (48u)
Nov 25 13:43:58 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 13:43:58 acsd: selected channel spec: 0xd92e (48u)
Nov 25 13:59:03 acsd: selected channel spec: 0xd92e (48u)
Nov 25 13:59:03 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 13:59:03 acsd: selected channel spec: 0xd92e (48u)
Nov 25 14:14:07 acsd: selected channel spec: 0xd826 (36l)
Nov 25 14:14:07 acsd: Adjusted channel spec: 0xd826 (36l)
Nov 25 14:14:07 acsd: selected channel spec: 0xd826 (36l)
Nov 25 14:14:07 acsd: acs_set_chspec: 0xd826 (36l) for reason APCS_CSTIMER
Nov 25 14:29:11 acsd: selected channel spec: 0xd92e (48u)
Nov 25 14:29:11 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 14:29:11 acsd: selected channel spec: 0xd92e (48u)
Nov 25 14:29:11 acsd: acs_set_chspec: 0xd92e (48u) for reason APCS_CSTIMER
Nov 25 14:44:16 acsd: selected channel spec: 0xd92e (48u)
Nov 25 14:44:16 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 14:44:16 acsd: selected channel spec: 0xd92e (48u)
Nov 25 14:59:21 acsd: selected channel spec: 0xd92e (48u)
Nov 25 14:59:21 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 14:59:21 acsd: selected channel spec: 0xd92e (48u)
Nov 25 15:14:26 acsd: selected channel spec: 0xd826 (36l)
Nov 25 15:14:26 acsd: Adjusted channel spec: 0xd826 (36l)
Nov 25 15:14:26 acsd: selected channel spec: 0xd826 (36l)
Nov 25 15:14:26 acsd: acs_set_chspec: 0xd826 (36l) for reason APCS_CSTIMER
Nov 25 15:29:30 acsd: selected channel spec: 0xd92e (48u)
Nov 25 15:29:30 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 15:29:30 acsd: selected channel spec: 0xd92e (48u)
Nov 25 15:29:30 acsd: acs_set_chspec: 0xd92e (48u) for reason APCS_CSTIMER
Nov 25 15:44:34 acsd: selected channel spec: 0xd92e (48u)
Nov 25 15:44:34 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 15:44:34 acsd: selected channel spec: 0xd92e (48u)
Nov 25 15:59:39 acsd: selected channel spec: 0xd92e (48u)
Nov 25 15:59:39 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 15:59:39 acsd: selected channel spec: 0xd92e (48u)
Nov 25 16:14:44 acsd: selected channel spec: 0xd92e (48u)
Nov 25 16:14:44 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 16:14:44 acsd: selected channel spec: 0xd92e (48u)
Nov 25 16:29:48 acsd: selected channel spec: 0xd92e (48u)
Nov 25 16:29:48 acsd: Adjusted channel spec: 0xd92e (48u)
Nov 25 16:29:48 acsd: selected channel spec: 0xd92e (48u)
Nov 25 16:44:52 acsd: selected channel spec: 0xd826 (36l)
Nov 25 16:44:52 acsd: Adjusted channel spec: 0xd826 (36l)
Nov 25 16:44:52 acsd: selected channel spec: 0xd826 (36l)
Nov 25 16:44:52 acsd: acs_set_chspec: 0xd826 (36l) for reason APCS_CSTIMER
Nov 25 16:44:53 acsd: selected channel spec: 0xd986 (136u)
Nov 25 16:44:53 acsd: Adjusted channel spec: 0xd986 (136u)
Nov 25 16:44:53 acsd: selected channel spec: 0xd986 (136u)
Nov 25 16:44:53 acsd: acs_set_chspec: 0xd986 (136u) for reason APCS_DFS_REENTRY
Nov 25 16:45:25 acsd: eth6: NONACSD channel switching to channel spec: 0xd986 (136u)

 

[QuikSilver]

Asus fixed the certificate last night (it's still missing the nwsrv-ns1 SAN however).



Noticed where? My firmware does not support auto-upgrade, so that message should only appear with the stock firmware.

I see the same thing @RMerlin under the system log section.

 

[Kingp1n]

I tried updating the alpha and beta firmwares on my RT-AC86U router. ...but I'm having issues with 2.4ghz after updating. Anyone notice any disconnects with 2.4ghz on the latest beta2? It seemed it happened after I rebooted the router and the signal never came back. I went back to 384.13 and no issues again.

UPDATE: I updated the routers domain name and it seems this fix my issue.

UPDATE 2: So, 2.4ghz is working with no issues. Also, I noticed that HW Acceleration and Flow cache are both enabled even though I have adaptive QOS enabled as well. Is this normal?

 

[Zastoff]

Check your installed add-ons. I can't even find the gaih_getanswer string through the whole source code.

EDIT: found it, it's within libnss_dns.so. No idea what it means, a few references to it on the web, sounds like debugging output tied to the resolver. It's apparently tied to DNSSEC.

EDIT2: looks like debugging output left behind in libnss, as per https://marc.info/?l=glibc-alpha&m=146176688926759&w=2 .

There is a hinfo(default) setting in DNSCrypt-proxy.toml @Butterfly Bones
Looks like this from the example file

## Response for blocked queries.  Options are `refused`, `hinfo` (default) or
## an IP response.  To give an IP response, use the format `a:<IPv4>,aaaa:<IPv6>`.
## Using the `hinfo` option means that some responses will be lies.
## Unfortunately, the `hinfo` option appears to be required for Android 8+

# blocked_query_response = 'refused'

 

[princi]

Does anyone have an AX connection working on the AX88U?

I just tried with Beta 2 and an iPhone 11 - seems to be just an AC connection.

Perhaps I will have to wait for the 7756 GPL to be integrated.

 

[QuikSilver]

I tried updating the alpha and beta firmwares on my RT-AC86U router. ...but I'm having issues with 2.4ghz after updating. Anyone notice any disconnects with 2.4ghz on the latest beta2? It seemed it happened after I rebooted the router and the signal never came back. I went back to 384.13 and no issues again.

UPDATE: I updated the routers domain name and it seems this fix my issue.

UPDATE 2: So, 2.4ghz is working with no issues. Also, I noticed that HW Acceleration and Flow cache are both enabled even though I have adaptive QOS enabled as well. Is this normal?

Yea, couple of us noticed that on ours.
https://www.snbforums.com/threads/b...eta-is-now-available.60037/page-3#post-524998

 

[Butterfly Bones]

There is a hinfo(default) setting in DNSCrypt-proxy.toml @Butterfly Bones
Looks like this from the example file

## Response for blocked queries.  Options are `refused`, `hinfo` (default) or
## an IP response.  To give an IP response, use the format `a:<IPv4>,aaaa:<IPv6>`.
## Using the `hinfo` option means that some responses will be lies.
## Unfortunately, the `hinfo` option appears to be required for Android 8+

# blocked_query_response = 'refused'

Thanks, I only installed dnscrypt recently, have read the key posts many times, but never thought to look at the .toml file nor had any idea it was the dns resolver issue until RMerlin found that information. Bottom line is not using the anon-cd-usnv anonymous relay - it caused the trouble as you saw my post in the Skynet thread.

 

[Hawk]

Does anyone have an AX connection working on the AX88U?

I just tried with Beta 2 and an iPhone 11 - seems to be just an AC connection.

Perhaps I will have to wait for the 7756 GPL to be integrated.

On Samsung S10, I have no issues with ax mode and using RT-AX88U. I have used on both bands, on 2.4 Ghz it performs better than 5Ghz.

 

[princi]

On Samsung S10, I have no issues with ax mode and using RT-AX88U. I have used on both bands, on 2.4 Ghz it performs better than 5Ghz.

Please pardon my ignorance, but are you saying AX connections are possible on 2.4 GHz as well?

 

[Hawk]

Please pardon my ignorance, but are you saying AX connections are possible on 2.4 GHz as well?

Yes, indeed it is possible. Remember to set wireless mode to auto for 2.4 ghz.