[ALPHA] 386.9_alpha1 for WiFi 5 (802.11ac) Models (GT-AC2900, RT-AC68U, and RT-AC86U)

[RiskyBusiness]

That's AiMesh failing to initialize due to failure in model validation. It seems that the RT-AC3100 GPL incorrectly contained wireless components from the RT-AC88U. I will have to wait for a fixed GPL from Asus.

Thanks Rmerlin. Everything else appears to be running fine, so won't concern myself with it for now.

 

[Gar]

Latest Alpha running smoothly on AC86 on my simple config. Thanks.

 

[RiskyBusiness]

That's AiMesh failing to initialize due to failure in model validation. It seems that the RT-AC3100 GPL incorrectly contained wireless components from the RT-AC88U. I will have to wait for a fixed GPL from Asus.

Flashed the latest alpha and it appears to have corrected the errors I was seeing in the log. Thanks @RMerlin

 

[BlackIce]

Merlin,

I wanted to pass along to you something that happened to me when changing a password using
386.9 Alpha 1 on my RT-AC86u.
I changed the password last night. Even rebooted and logged in with the new password. Everything working
good so I backed up the new settings and restored to my Spare RT-AC86u as well. Logged into that and confirmed
everything working good. This morning I attempted to login with the new password. Could not login with the new password.
(The router would have rebooted on a scheduled reboot before doing this)...I tried multiple times but could not login using
the new password or the old password. I pulled the spare router off the self and put it online trying to login with the new password.
NOPE. Could not login the spare router either. WTF. So I hard reset the router and restored the settings I had backed up after changing the password.
After doing this I still could not get logged in with the new password I had assigned last night. At this point I gave up and restored
386.7_2 firmware....Logged in and restored the settings that were with the old password. Everything working again on both the main and spare router
using 386.7_2. No idea what might have happened and why I could not login with the new password on 386.9 Alpha 1 (Even though I could last night)...
Thought I should report this as there "MAY" be an issue with setting a new password on 386.9 Alpha 1 with the RT-AC86u.

 

[L&LD]

Regardless if there is a password issue on this firmware, you shouldn't be creating a backup config file on one router and restoring it on another.

 

[bennor]

Everything working good so I backed up the new settings and restored to my Spare RT-AC86u as well.

Exporting the configuration file from one router and importing it into another router is generally NOT a good idea, nor do I think most here would recommend doing it. It can potentially introduce issues in the secondary router. It is also generally not a good idea to import a configuration file from an older firmware version into a later firmware version (and vice versa). And it is definitely not a good idea to import an ASUS stock firmware configuration file into Asus-Merlin (and vice versa).

As a general troubleshooting step. When weird issues arise with the firmware, it is best to do a hard factory reset and manually reconfigure the router from scratch without importing a configuration file.

 

[SteveyB]

Latest Alpha running smoothly on my RT-AC86U (with 35 devices) for 4 days with no issues to reported so far. Thanks!

 

[heysoundude]

Nice to see how stable the alpha seems to be.
Will Santa Merlin skip right over beta testing and drop a release in our stockings for Christmas, I wonder?

 

[Gar]

Nice to see how stable the alpha seems to be.
Will Santa Merlin skip right over beta testing and drop a release in our stockings for Christmas, I wonder?

I was thinking the same.

 

[laracroftonline]

Wished ASUS pushed their gpl for the ac5300.

 

[Dedel66]

My RT-AC86U in Bridged Mode is working as expected after flashing "dirty" from 386.7_2 to 386.9_alpha1-gfb36317a30.
Reconnected immediatly after reboot.

 

[tombono]

There is nothing in the 386.9 (xx-xxx-xxxx) changelog about wireguard.
Does this mean there will be no wireguard on RT-AC86u routers?

 

[Dedel66]

Does this mean there will be no wireguard on RT-AC86u routers?

That´s the fact. No AC-Model will get wireguard.

 

[bennor]

Does this mean there will be no wireguard on RT-AC86u routers?

Correct. The AC routers won't be getting Wireguard included in the Asus firmware. The 388.x firmware for the AX series routers are getting Wireguard included in the GUI, the AC routers are not getting the 388.x firmware. RMerlin has commented on this in the past about the AC routers not getting 388.x firmware.

[Dev] Asuswrt-Merlin 388.1 development

That's unfortunate You already have everything included in 388 in Asuswrt-Merlin 386 plus extras.

www.snbforums.com

Beta - Asuswrt-Merlin 388.1 Beta is available for select models

Asuswrt-Merlin 388.1 Beta is now available for all Wifi 6 (AX) models. This release marks the merge with the new 388 code base from Asus. I don't want to list every 388-specific changes made by Asus, so I recommend checking Asus' own changelogs for more details. I will highlight the most...

www.snbforums.com

[Dev] Asuswrt-Merlin 388.1 development

Good to see the AX86U Pro is supported! Might be my AC86U replacement? Does anyone know when this model will be available in Europe?

www.snbforums.com

AC series router users can use the WireGuard Manager add-on script.

Wireguard - Session Manager (4th) thread

Another 6 months are up (thanks to SNB forum member @greenspanner for the heads-up); details of WireGuard® Manager can be found @the following: https://github.com/MartineauUK/wireguard and @ZebMcKayhan's invaluable Hint's and Tips Guide...

www.snbforums.com

 

[Sonyrolfy]

Dirty upgrade from RT-AC86U_386.9_alpha1-g58fb40f04e to RT-AC86U_386.9_alpha1-gfb36317a30

May 5 07:05:26 uiDivStats: Waiting for NTP to sync...
May 5 07:05:26 Diversion: Mounting Diversion WebUI page
May 5 07:05:26 (x3mRouting.sh): 2384 Entware not available - wait time 107 secs left
May 5 07:05:26 kernel: ip_set: protocol 6
May 5 07:05:26 (x3mRouting.sh): 2384 IPSET restored: (NTP not synced but running all my custom ipset's)

NTP still not synced, but scripts /entware do start anyway.

Dec 23 20:28:18 kernel: [0000006e] *pgd=00000000151b7003, *pud=00000000151b7003, *pmd=0000000016796003, *pte=0000000000000000
Dec 23 20:28:18 kernel: CPU: 0 PID: 4468 Comm: dnsmasq Tainted: P O 4.1.27 #2

NTP synced, but scripts and entware do not restart.

Dnsmasq: updated to 2.88 is my problem i think?

 

[heysoundude]

Dnsmasq: updated to 2.88 is my problem i think?

that version rings a bell from the entware update (last week?) https://www.snbforums.com/threads/update-and-upgrade.82385/
have you updated and upgraded entware packages from amtm? (I think the command is ep to get the optional process started - they did some stuff to entware recently, including a bunch of chrony stuff for NTP, if that's what you're using, and unbound)

I'm also RT-AC86 here, but not running this alpha...

 

[Sonyrolfy]

that version rings a bell from the entware update (last week?) https://www.snbforums.com/threads/update-and-upgrade.82385/
have you updated and upgraded entware packages from amtm? (I think the command is ep to get the optional process started - they did some stuff to entware recently, including a bunch of chrony stuff for NTP, if that's what you're using, and unbound)

I'm also RT-AC86 here, but not running this alpha...

FWIW I dont use unbound, i just updated entwere after the above notice when scripts en ovpn did start without time was set on the second alpha. The update (ep) afterwards didnt help.
IMHO its related to dnsmasq 2.88 beacause the dnsmasq Tainted: P is in my log. It doenst appear on the first alpha. We 've seen this before when dnsmasq was updated. But lets see what ppl have after some time. Maybe i just need a fresh install by then.

 

[bluepoint]

Dirty upgrade from RT-AC86U_386.9_alpha1-g58fb40f04e to RT-AC86U_386.9_alpha1-gfb36317a30

May 5 07:05:26 uiDivStats: Waiting for NTP to sync...
May 5 07:05:26 Diversion: Mounting Diversion WebUI page
May 5 07:05:26 (x3mRouting.sh): 2384 Entware not available - wait time 107 secs left
May 5 07:05:26 kernel: ip_set: protocol 6
May 5 07:05:26 (x3mRouting.sh): 2384 IPSET restored: (NTP not synced but running all my custom ipset's)

NTP still not synced, but scripts /entware do start anyway.

Dec 23 20:28:18 kernel: [0000006e] *pgd=00000000151b7003, *pud=00000000151b7003, *pmd=0000000016796003, *pte=0000000000000000
Dec 23 20:28:18 kernel: CPU: 0 PID: 4468 Comm: dnsmasq Tainted: P O 4.1.27 #2

NTP synced, but scripts and entware do not restart.

Dnsmasq: updated to 2.88 is my problem i think?

Your NTP is not syncing on time affecting your addons. Correct time is essential for the router to function properly. Find out the reason then make corrections.

 

[SheikhSheikha]

Dirty upgrade to 386.9 Alpha on RT-AC5300's. Running smooth from start so very promising .... Thanks Erik

 

[laracroftonline]

The alpha works very stable on my AC5300. Thanks @RMerlin for your hard work!

Last time it was this stable was on 5_2 for me so finally on a new version that doesn't give me headaches.