[384.18_Alpha Builds] Testing all variants

[Deleted member 22229]

Why wouldn't it be?

What i actually meant was anytime soon. I know, it will get done when it gets done.

 

[JWoo]

What I just posted.

Sarcasm rules!!!

 

[JWoo]

Why wouldn't it be?

This is one of those cases where a negative is a positive! Awesome.

 

[Vexira]

Sarcasm rules!!!

from what I understand he actually means it literally he did just make a post with recommendations, seems very far from sarcasm.

 

[Vexira]

This is one of those cases where a negative is a positive! Awesome.

I find it to be more of a rehtotical question, more of a why would Asus not include a fix.

 

[Vexira]

I was actually hyped for Asus new QoS categories update, but now my hopes are deflated, on the upside atlest they added Disney plus and YouTube traffic to the detection signatures, I does help to some degree atlest.

I'm just waiting till I see continuous mode added in, and the eventual FQ-codel update.

 

[CaptnDanLKW]

QOS is mostly (or entirely) negated by most enterprises VPN solutions so once your IPSec or SSL tunnel is established the actual traffic type is part of the packet payload so you lose the benefit.
I used to prioritize clients, by their MAC addresses, my work laptop getting ‘highest’ but not anymore. If you have a connection > 100/20 up/down you probably don't need to mess with QOS anymore. I’m at 500/20 with no QOS for a couple of years and never looked back. At least that’s my experience.
So this ASUS rebranding seems a bit weak in the real world.

 

[Sonyrolfy]

After some weeks of struggling with VOIP over vpn with Asus QOS, especially with lag, i dived deeper in this weekend and found out that UDP is the best setting for VOIP. I was connected over TCP. Tried it with QOS traditional settings with some tweaking with up and down numbers. Now no lag anymore rather then some static from time to time. Happy working from home.

 

[Odkrys]

with merging 384_81846, I can't export client.conf of openvpn server.
nvram get vpn_server1_state stay at 1.
ac86u.

 

[fields987]

i used amcfwm to compile my own RT-AX88U build based on the new commits to the AX repository. Im now on 384.18_alpha1-ga692c42b83. Not sure if this is a bug with the firmware or my dns setup. My trend micro signature version had been stuck at either 2.174 or 2.176 (cant remember exactly) with the last update showing as 5/5/20. Seems like a long period to go without an update. Anytime I would try to check for updates, it would say check for updates was successful. After I flashed my new build last night, I had noticed the signature version was 2.180, but still showed last update was 5/5/20. Still getting a success when checking for updates. During this time, I've also been experiementing with NextDNS, both their DoH proxy and DoT using Merlin's config on the wan page. I'm showing dlcdnets.asus.com resolving and not getting blocked, but this is something I changed over my previous cleanbrowsing security DoT config. reverting back to that and testing didn't generate any different results. Fairly minor issue, but thought it was worth mentioning. Dont think Merlin has much control over it anyway since all the trend stuff is closed source.

PS - for anyone wondering, i can confirm the wireless log bug has been fixed.

 

[octopus]

https://onedrive.live.com/?authkey=!AGY2taGX02nVmWA&id=CCE5625ED3599CE0!1427&cid=CCE5625ED3599CE0


384.18 (xx-xxx-2020)
- UPDATED: Merged GPL 384_8563 for AX models.
- UPDATED: Merged GPL 384_81846 for mainline models (code is almost
identical to 385_20490)
- UPDATED: Merged SDK + binary blobs from 384_81846 for RT-AC86U.
- UPDATED: Merged SDK + binary blobs from 384_81844 for RT-AC5300.
- UPDATED: Merged SDK + binary blobs from 385_20490 for RT-AC68U
and RT-AC3100.
- UPDATED: Merged SDK + binary blobs 384_8563 for RT-AX58U.
- UPDATED: amtm to 3.1.7.
- FIXED: ssh/scp client would fail to connect while negotiating
a chacha20 connection (themiron)

EDIT: All build is relesed today.

New Builds.

 

[L&LD]

Installed on RT-AX88U (main) and RT-AX58U (AiMesh node, wired).

Working without issues for the last few hours.

Dirty install to both routers (just 'safely removed' USB drive from (main).

 

[RAH-66]

New Builds.

RT-AC87U_384.13_8-gaf00569f60.zip

384.13_9 (xx-xxx-2020)
This release is only available for the RT-AC87U and RT-AC3200.
- UPDATED: Wireless driver from 382_52230 for RT-AC87U (should
address Kr00k)

384.13_8 (26-Apr-2020)
This release is only available for the RT-AC87U and RT-AC3200.
- UPDATED: dnsmasq to 2.81-openssl (themiron)
- UPDATED: openvpn to 2.4.9.
- UPDATED: openssl-1.1 to 1.1.1g (themiron)

 

[MDM]

RT-AC87U_384.13_8-gaf00569f60.zip

384.13_9 (xx-xxx-2020)
This release is only available for the RT-AC87U and RT-AC3200.
- UPDATED: Wireless driver from 382_52230 for RT-AC87U (should
address Kr00k)

384.13_8 (26-Apr-2020)
This release is only available for the RT-AC87U and RT-AC3200.
- UPDATED: dnsmasq to 2.81-openssl (themiron)
- UPDATED: openvpn to 2.4.9.
- UPDATED: openssl-1.1 to 1.1.1g (themiron)

And for the download you get only "RT-AC87U_384.13_8-gaf00569f60" from 4h ago, but inside in the Changelog 384.13_9 is mentioned and no 3200 option at all??!

 

[TechTinkerer]

How stable is this now even though alpha?

 

[fields987]

How stable is this now even though alpha?

My ax88u has been very stable for almost a month since the first alpha came out and a few new alpha builds using amcfwm to compile since. Ymmv

 

[New2This]

TOR is not working atm, with this update

NVM, It was my mistake.......Everything is working

 

[LimJK]

Installed on RT-AX88U (main) and RT-AX58U (AiMesh node, wired).

Working without issues for the last few hours.

Dirty install to both routers (just 'safely removed' USB drive from (main).

Just like L&LD,

I "safely removed" USB Thumb Drive, before I Dirty Flash 384.18_alpha1(May 29) over 384.18_alpha1(May 7) on my AiMesh Router (RT-AX88U) + 2x AiMesh Nodes (RT-AC86U) with stock FW 3.0.0.4_384_81918. All seems good, running for about 6 hours:

• Stable Wifi: Using Fixed WiFi Control Channel & bandwidth (2.4GHz: Ch 11 20MHz, 5.0GHz: Ch 149 80MHz)
• GUI Configuration: AiProtection, Asus DDNS (Let's Encrypt), OpenVPN Server (working with Tunnelblick (macOS Catalina) & OpenVPN Connect (iOS 13))
• Scripts - Amtm, Diversion, Skynet, connmon

Browser (Safari on macOS Catalina) related issues has been fixed

• System Log -> Wireless Log
• AiProtection -> Network Protection -> Alert Preference

Thank You!

 

[MNoisy]

It has been a long week so forgive me if I completely missed the post after searching, but why is the AC88 excluded from this alpha at this point?

 

[SheikhSheikha]

Dirty upgrade from 384.17 on one of my RT-AC5300 routers to test the waters. So far everything stabile.