Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

[ATLga]

I see! Possibly Asus believes we're getting very close for 386 to become official release.
And I tend to agree. My setup is as stable as it was on 384 plus additional features added by 386

I would put this another way; .386 IS an official release as of Oct 22nd AND is still in beta. From my issues and others, the .386 version released to the public is not fully baked yet.

 

[KingBravery]

I updated both my ZenWiFi XT8 a while back with rc4 linked here and have been looking to update the firmware again when this forum deemed a new version more stable, because I have had a lot of problems with disconnections etc like many others.
I updated the main unit this morning without issue, but when I want to update the other mesh unit it won't let me connect to it.

I login via my browser and go to the firmware update page, and when I choose to manually update the firmware for the secondary unit a popup window shows that the connection is refused, so I don't even get far enough along to select which firmware file I want to try to update it with.
I thought that maybe this was because I updated the main unit first to rc7 and then somehow they couldn't cooperate properly longer, so I downgraded the main unit back to rc4 with the plan to update the secondary unit first to rc7.
However this didn't change anything, I still can't select a file to update the secondary unit with.
I've also tried updating the main unit with the latest official firmware but this didn't change anything either.
I've tried rebooting both units, no change.

I see that the secondary unit is working as normally though and connecting units, allowing them network and internet access so besides from not being able to update the firmware it is working as expected.
So, it definitely backhauls properly to the main unit and they seem to work together in all aspects.

Any idea on what I can do next to update the firmware on the secondary unit?

I think you can try factory reset both first. Resetup and then proceed for upgrade.

 

[Sebastien Bougie]

Hello

I'm having a weird problem, I get the DNS Maximum reach message but before I get that i get the follow in the log, alot of those

Oct 30 06:01:36 syslog: wlceventd_proc_event(491): wl0.1: Disassoc B4:E6:2D:22:10:9B, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 30 06:01:36 syslog: wlceventd_proc_event(510): wl0.1: Auth B4:E6:2D:22:10:9B, status: Successful (0)
Oct 30 06:01:36 syslog: wlceventd_proc_event(539): wl0.1: Assoc B4:E6:2D:22:10:9B, status: Successful (0)
Oct 30 06:01:37 syslog: wlceventd_proc_event(491): wl0.1: Disassoc B4:E6:2D:20:62:98, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 30 06:01:37 syslog: wlceventd_proc_event(510): wl0.1: Auth B4:E6:2D:20:62:98, status: Successful (0)
Oct 30 06:01:37 syslog: wlceventd_proc_event(539): wl0.1: Assoc B4:E6:2D:20:62:98, status: Successful (0)
Oct 30 06:01:38 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:38 kernel: 00:F6:20:44:FC:64 not mesh client, can't update it's ip
Oct 30 06:01:38 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:38 kernel: 00:F6:20:44:FC:64 not mesh client, can't update it's ip
Oct 30 06:01:38 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:39 kernel: 00:F6:20:44:FC:64 not mesh client, can't update it's ip
Oct 30 06:01:39 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:39 syslog: wlceventd_proc_event(491): wl0.1: Disassoc DC:4F:22:EF:609, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 30 06:01:39 syslog: wlceventd_proc_event(510): wl0.1: Auth DC:4F:22:EF:609, status: Successful (0)
Oct 30 06:01:39 syslog: wlceventd_proc_event(539): wl0.1: Assoc DC:4F:22:EF:609, status: Successful (0)
Oct 30 06:01:39 kernel: 00:F6:20:44:FC:64 not mesh client, can't update it's ip
Oct 30 06:01:39 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:39 syslog: wlceventd_proc_event(491): wl0.1: Disassoc DC:4F:22:EC:52:E2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 30 06:01:39 syslog: wlceventd_proc_event(510): wl0.1: Auth DC:4F:22:EC:52:E2, status: Successful (0)
Oct 30 06:01:39 syslog: wlceventd_proc_event(539): wl0.1: Assoc DC:4F:22:EC:52:E2, status: Successful (0)
Oct 30 06:01:39 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:39 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:40 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:40 syslog: wlceventd_proc_event(491): wl0.1: Disassoc DC:4F:22:EE:FD:E7, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 30 06:01:40 syslog: wlceventd_proc_event(510): wl0.1: Auth DC:4F:22:EE:FD:E7, status: Successful (0)
Oct 30 06:01:40 syslog: wlceventd_proc_event(539): wl0.1: Assoc DC:4F:22:EE:FD:E7, status: Successful (0)
Oct 30 06:01:40 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:40 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:40 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:40 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:41 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:41 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:41 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:41 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:41 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:42 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:42 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:42 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:42 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:42 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:43 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:43 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:43 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:43 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:43 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:44 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:44 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:44 syslog: wlceventd_proc_event(474): wl0.1: Deauth_ind 68:57:2D:8B:46:BC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Oct 30 06:01:44 syslog: wlceventd_proc_event(491): wl0.1: Disassoc 68:57:2D:8B:46:BC, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 30 06:01:44 syslog: wlceventd_proc_event(474): wl0.1: Deauth_ind 68:57:2D:8B:43:45, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Oct 30 06:01:46 syslog: wlceventd_proc_event(510): wl0.1: Auth 68:57:2D:8B:46:BC, status: Successful (0)
Oct 30 06:01:47 syslog: wlceventd_proc_event(539): wl0.1: Assoc 68:57:2D:8B:46:BC, status: Successful (0)
Oct 30 06:01:47 kernel: 80:5E:4F:A9:17:2F not mesh client, can't update it's ip
Oct 30 06:01:51 syslog: wlceventd_proc_event(510): wl0.1: Auth 68:57:2D:8B:43:45, status: Successful (0)
Oct 30 06:01:51 syslog: wlceventd_proc_event(539): wl0.1: Assoc 68:57:2D:8B:43:45, status: Successful (0)

Then no more internet, if i disable my guest network then turn off the router and back on , no more problem

Any ideas? I already did 2 factory reset on both main router and mesh....

Thanks


update: I went back to the 385 Firmware... Problem Solve... For sure something is wrong with this version

I will wait for the next one

 

[NSNE]

With an AX88U running RC2-7 with WAN aggregation enabled, I've noticed that adding MAC/IP bound clients on the LAN immediately causes WAN aggregation to go into an unknown state (denoted by the "!" in the GUI). Can anyone else confirm?

 

[GHammer]

I have an AX58U and an AX86U in AIMesh. I have an Ethernet backhaul and while it works, it shows differently in the GUI of the router.
Is there a setting or two I have missed? Or, just a beta bug? I have file feedback for this, but I'm curious.

 

[Moabdave]

When you try RC2-7 , take more time configuring it... might help to discover where it goes south.

OE

I'm doing that now. So far same problems as with RC6. "master router" GT-Ac5300, 2-88U's as satellite routers, Upgrade to RC7, factory reset, manual configuration transfer, no config file import. Same as last time. I can successfully navigate the wizard for adding the first Aimesh node, and the wizard claims success, but the node does not remain in the list of nodes for long. I try to add the 2nd node, and that's when the freezes and reboots begin. Virtually identical as RC6.
The one discovery I have made is that if I first try to add the AiMesh nodes before any other configuration (other than what the bootup wizard makes you do) only the AINodes freeze up, the main router appears to function normally. If I configure the main router with the guest network, DHCP IP info, etc. then add the AInodes, all routers freeze up.

But what I find most curious, and this also happened with RC-6, is even the LAN ports on the satellite routers are non-functional after trying to attach them as AInotdes. (I have tons of hardwared devices in my home office, that's why I went with the 88U's in the first place, cut down on the number of switches in my home)

 

[Travelor]

Good Afternoon ASUS Beta Testers/Developers - your work to extend, strengthen, and optimize the our ASUS devices is highly appreciated.
I have the ROG GT-AX11000 which has the ROGized GUI - I had the latest non-beta firmware installed prior to upgrading to RC-7 -
My question is this: Is the GUI supposed to change from the ROGized to the ASUSWRTized GUI?
I did do the upgrade and the
I sincerely apologize if this question was asked/answered - In most cases a search for GUI resulted in a "too short" message - Not a power user of this forum software so I'm learning as I go.

Again, my thanks go out to the developers of the BETA RC. Your work is appreciated and I am thankful for your work.
Trav...

 

[L&LD]

@Travelor use the 'Better search' option instead.

 

[Moabdave]

My question is this: Is the GUI supposed to change from the ROGized to the ASUSWRTized GUI?

I have the "ROGized" GT-AC5300, and the ROGized gui remained after installing beta firmware. With that said, I actually don't like the ROG gui and frankly wouldn't care if it magically reverted back to the stock WRT guid

 

[jass]

Good Afternoon ASUS Beta Testers/Developers - your work to extend, strengthen, and optimize the our ASUS devices is highly appreciated.
I have the ROG GT-AX11000 which has the ROGized GUI - I had the latest non-beta firmware installed prior to upgrading to RC-7 -
My question is this: Is the GUI supposed to change from the ROGized to the ASUSWRTized GUI?
I did do the upgrade and the
I sincerely apologize if this question was asked/answered - In most cases a search for GUI resulted in a "too short" message - Not a power user of this forum software so I'm learning as I go.

Again, my thanks go out to the developers of the BETA RC. Your work is appreciated and I am thankful for your work.
Trav...

View attachment 27300

Have you tried ctrl + F5 ?

 

[Travelor]

@Travelor use the 'Better search' option instead.

@L&LD
Not intending to highjack this thread with a discussion on Forum usage - I did try the "better search" and I have been able to learn a lot more about the SNB Forum usage - I like the "search thread" option. But even searching this thread produced no result specific to my question. I will post any further search or forum usage questions in the proper space..

I have the "ROGized" GT-AC5300, and the ROGized gui remained after installing beta firmware. With that said, I actually don't like the ROG gui and frankly wouldn't care if it magically reverted back to the stock WRT guid

@Moabdave
Thanks for the confirmation on the GUI for our ROGized devices.
I am with you as well regarding the ROGized GUI - I was expecting (wanting) a GUI change, thus my question -

Thanks for the prompt replies, I feel a bit more comfortable that the RC-7 update was completed correctly.

Will report any issues as they arise.

Trav...

 

[bumpengrinder]

I have the "ROGized" GT-AC5300, and the ROGized gui remained after installing beta firmware. With that said, I actually don't like the ROG gui and frankly wouldn't care if it magically reverted back to the stock WRT guid

The GT-AC2900 has the ROGgie GUI too.

Not too fussed about it, but then I thought I'd be switching off the coloured LEDs when I got this... but I actually find myself quite liking them... must be the mid-life crisis kicking in!

Look how lovely my son's Lego ship in bottle looks with it...

Edit: I just thought - this will be great at Christmas!

 

[Travelor]

Have you tried ctrl + F5 ?

@jass
Great suggestion - I have all my browsers setup to auto delete as much cache as possible whenever the browser is closed - That said, I did take it a step further and manually cleared all temp/cache files.

Trav...

 

[Travelor]

The GT-AC2900 has the ROGgie GUI too.
I just thought - this will be great at Christmas!

@bumpengrinder
I change my RGB based on the holiday and/or season. Currently on Orange - So in the corner of the my den, there's a seasonal glow, that goes unnoticed until one makes a midnight raid to the fridge.. But alas, I have to remember to change the RGB to match the season. Needless to say, but St. Patty Green, remained until yesterday.. Laugh...
Trav...

 

[bumpengrinder]

@bumpengrinder
I change my RGB based on the holiday and/or season. Currently on Orange - So in the corner of the my den, there's a seasonal glow, that goes unnoticed until one makes a midnight raid to the fridge.. But alas, I have to remember to change the RGB to match the season. Needless to say, but St. Patty Green, remained until yesterday.. Laugh...
Trav...

Great idea! Now you've got me thinking... hmmm... Guy Fawkes night coming up... I'll see if I can find a setting that looks like fireworks/a bonfire...

PS How long before we get told off for going off topic?

 

[Deleted member 22229]

PS How long before we get told off for going off topic?

This is getting off topic please lets stick to the beta testing.

 

[Travelor]

Just to bring it back on topic and to answer the question:
Does the GUI (Graphic User Interface) change from the ASUS ROG branded (ROGized) GUI to the ASUSWRT GUI when updating to new ASUSWRT Beta Firmware?
NO - the GUI does not change from ROG to ASUSWRT.

Great idea! Now you've got me thinking... hmmm... Guy Fawkes night coming up... I'll see if I can find a setting that looks like fireworks/a bonfire...

PS How long before we get told off for going off topic?

This is getting off topic please lets stick to the beta testing.

Trav...

 

[bumpengrinder]

Just to bring it back on topic and to answer the question:
Does the GUI (Graphic User Interface) change from the ASUS ROG branded (ROGized) GUI to the ASUSWRT GUI when updating to new ASUSWRT Beta Firmware?
NO - the GUI does not change from ROG to ASUSWRT.

Trav...

I can also confirm that the crazy ROG lighting does not change to cool blue

 

[bumpengrinder]

This is getting off topic please lets stick to the beta testing.

I'll shut up now

 

[SoulSlayer]

I have a Ax88 with two XT8 nodes. I had the merlin firmware in the Ax88 and the production firmware on the XT8. Had some problems with the dhcp, because i have a lot of iot devices with tasmota firmware and sometimes they are disconnected and never connect again.
1) Tried to flash latest RC7 to the AX88 and to XT8, but it didn't detect my nodes, because i have them connected to an unmanaged switch. I can only have one node working in RC7.
2) Tried RC4 in all of the devices but it is unstable and sometimes the nodes are not connected.
3) The most stable i am having is AX88 with RC7 and the two XT8 with production firmware.