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

[Jeffrey Young]

We only give support to people that speak English

Still with a little effort;

What ipv6 is inaccessible over https on the intranet? The firewall I have turned off and pinging the IPv6 address is fine. However, the management interface of the router cannot be accessed, nor can port forwarding and dmz. However, the nas of the intranet can also be accessed directly through the ipv6 address.

My router is a GT-AX6000

 

[Samuel_1975]

Unfortunately its dead, no signs of life, cant get in recovery mode - but thanks anyway. Aware of updating your AX86U guys - registered here specially to say that.

I should have listened to you and I wanted to test with my rt-ax86u and speech it is completely dead and does not start, remove the alpha update it completely destroyed my router

will not get a new router from asus or update my sister's router at risk of destroying it with want yes do not

so good advice do not download it

 

[trecrunur]

@trecrunur
Did you check for the correct firmware? The alfa version you mention in your post is for the AC86.
The AX86 version is RT-AX86U_386.7_alpha1-g0ad1a4faae_cferom_pureubi.w.
So did you accidently selected the wrong firmware , that did brick your router?

Copied wrong file name, so no, i didnt miss version - was installed RT-AX86U_386.7_alpha1-g0ad1a4faae_cferom_pureubi ofcourse.

 

[trecrunur]

will not get a new router from asus

Why? I think it can be classified as waranty if you say it was dead a couple of month already.

 

[Samuel_1975]

yes download the correct version of merlin asuswrt on rt-ax86u on alpha

remove before destroying for others with

have ordered a new router and mine is completely dead and can no longer be used

mine was destroyed today Sunday the 5th of June 2022 pch had had the router not so long so insurance does not apply in the same way


no no more download from merlin after this

 

[clweb]

Alpha versions aswell as Betas are always risky.
So you should know what you are doing before installing.

 

[Ubimo]

I discovered a entry in syslog, which I haven't seen before:

Jun  5 17:08:20 smbd[10520]: [2022/06/05 17:08:20.829946,  0] lib/pidfile.c:146(pidfile_create)
Jun  5 17:08:20 smbd[10520]:   ERROR: smbd is already running. File /var/run/samba/smbd.pid exists and process id 7634 is running.

I'm on latest alpha AC86U.

What's this?

 

[hancox]

Alpha versions aswell as Betas are always risky.
So you should know what you are doing before installing.

Come on - bricking is a little more than "risky".

Has anyone actually successfully flashed an AX86U? The conjecture (and note on the original post) is kind of misleading - the user simply copied the wrong filename into their post, not badly onto their router, if I'm reading right.

 

[mistercoffee1]

Alpha versions aswell as Betas are always risky.
So you should know what you are doing before installing.

Bricking should never be on the table though.
Bugs? Sure.
But never bricking.

 

[RMerlin]

Has anyone actually successfully flashed an AX86U?

I did. My own RT-AX86U is running fine, which is why I uploaded this alpha build.

no no more download from merlin after this

The bug is within Asus's code, it's not mine, and it also happened with their own firmware released a few weeks ago:

RT-AX86U bricked after update Version 3.0.0.4.386.48377

Need help guys. Tonight my asus app presented me an update Version 3.0.0.4.386.48377 for my main router AX86U and my Ethernet backhaul connected router AX82U. My other ethernet backhaul connected router AX86S did not needed to update So via the Asus app i started the update and forgot about it...

www.snbforums.com

The issue does not happen for everyone. It didn't happen with my own router.

have ordered a new router and mine is completely dead and can no longer be used

Contact Asus for an RMA. Since the issue also occurred with their own firmware, they may still accept to replace it.

 

[learning_curve]

Why can't ipv6 access the internal network on the external network through https? I have turned off the firewall, and ping the IPv6 address is normal. But I can't access the router's management interface, nor can port forwarding and dmz. However, the nas of the intranet can also be directly accessed through the ipv6 address.

My router is GT-AX6000

We're on different routers, but both on 386.7 Alpha releases... I have no issues at all with IPv6. All aspects of IPv6 work for me, without any faults or errors (internal / external / tested and verified) so the issues might be specific to your router & this specific release? No doubt other users will confirm or deny this soon.

 

[DJones]

GT-AX11000 dirty update seems stable only encountered issue is Aura RGB reenables itself after scheduled reboot despite previously disabling either through settings or button prior to the device rebooting.

RT-AX58u dirty update device used as node in mesh seems fine no noticeable issues.

 

[hancox]

I did. My own RT-AX86U is running fine, which is why I uploaded this alpha build.


The bug is within Asus's code, it's not mine, and it also happened with their own firmware released a few weeks ago:

RT-AX86U bricked after update Version 3.0.0.4.386.48377

Need help guys. Tonight my asus app presented me an update Version 3.0.0.4.386.48377 for my main router AX86U and my Ethernet backhaul connected router AX82U. My other ethernet backhaul connected router AX86S did not needed to update So via the Asus app i started the update and forgot about it...

www.snbforums.com

The issue does not happen for everyone. It didn't happen with my own router.


Contact Asus for an RMA. Since the issue also occurred with their own firmware, they may still accept to replace it.

Thanks - I figured as such. I didn't want the speculation/misunderstanding to take over the convo.

 

[visortgw]

I did. My own RT-AX86U is running fine, which is why I uploaded this alpha build.


The bug is within Asus's code, it's not mine, and it also happened with their own firmware released a few weeks ago:

RT-AX86U bricked after update Version 3.0.0.4.386.48377

Need help guys. Tonight my asus app presented me an update Version 3.0.0.4.386.48377 for my main router AX86U and my Ethernet backhaul connected router AX82U. My other ethernet backhaul connected router AX86S did not needed to update So via the Asus app i started the update and forgot about it...

www.snbforums.com

The issue does not happen for everyone. It didn't happen with my own router.


Contact Asus for an RMA. Since the issue also occurred with their own firmware, they may still accept to replace it.

I successfully flashed two (2) RT-AX86U AiMesh nodes to 386.7 alpha1. These same two nodes were previously successfully flashed to the Asus baseline that caused some users issues.

 

[octopus]

I successfully flashed two (2) RT-AX86U AiMesh nodes to 386.7 alpha1. These same two nodes were previously successfully flashed to the Asus baseline that caused some users issues.

Did you flash over ethernet or OTA?

 

[kernol]

FIRSTLY ... a repeat CAUTION ... Alpha firmware versions are, by their nature, HIGH risk!
Doubly so these days when RMerlin is working on and including in his firmware Asus GPL's for firmware not released as yet for all affected router models (in several recent cases ... the Asus GPL version had not been released into the "wild" on ANY models).

Merlin's RT-AX86U 386.7 Alpha has, graciously, been withdrawn ... so not sure much useful info will come from the Poll included with this thread.
We know that two new members, both first time posters on this forum [sorry for your loss @trecrunur and @foxyserg] , have bricked their routers within hours of the release of the Alpha firmware for this model.

We know that not all RT-AX86U's will get bricked by this firmware ... but the HUGE hassle of having to go through the RMA process to have a bricked router replaced by Asus ... just does not [in my view] justify playing Russian Roulette with your AX86 !!

The LAST thing customers should expect is that a released firmware may brick a router even though correctly applied!
Reputational harm for Asus will certainly flow through to RMerlin when disasters like this one strike even a few users.

Let's hope that Asus resolves the firmware for this model AND FULLY TESTS it before letting it loose on their customers [whether via RMerlin or Asus stock].

 

[kernol]

Microsoft OneDrive

onedrive.live.com

Available builds:
...
RT-AX86U (June 05, 2022) Flash with caution make sure to use RT-AX86U not RT-AC86U, some brick is reported!!!
.....

The RT-AX86U Alpha firmware has been withdrawn - and no one has flashed their RT-AX86U's with the wrong 386.7 alpha version [besides if the firmware webui is so sloppy as not to be able to prevent the wrong model firmware from being uploaded - it should not be released to customers].

I am aware that "intrepid" members may use direct code to upload firmware and bypass version checks - but they get what they deserve if they screw up .

I really enjoy the speed with which you leap out the blocks to announce Alpha Releases - so thanks for that. {Thumbs-Up}
Could I encourage you to include a standard CAVEAT in the hopes [perhaps vain?] of discouraging Noobs from playing on the wild side .
I am sad that two first time posters have ended with bricked RT-AX86U's !

 

[DJones]

The RT-AX86U Alpha firmware has been withdrawn - and no one has flashed their RT-AX86U's with the wrong 386.7 alpha version [besides if the firmware webui is so sloppy as not to be able to prevent the wrong model firmware from being uploaded - it should not be released to customers].

I am aware that "intrepid" members may use direct code to upload firmware and bypass version checks - but they get what they deserve if they screw up .

I really enjoy the speed with which you leap out the blocks to announce Alpha Releases - so thanks for that. {Thumbs-Up}
Could I encourage you to include a standard CAVEAT in the hopes [perhaps vain?] of discouraging Noobs from playing on the wild side .
I am sad that two first time posters have ended with bricked RT-AX86U's !

At least Merlin’s firmware isn’t as as volatile as say DDWRT, I’ve bricked a few routers using it every firmware update you have to check if someone experienced a bricked router otherwise your leading the pack. I’ve learned how to solder a JTAG serial connection to possibly resurrect my routers, but even then it can be too far gone if you install the wrong firmware.

 

[Smokey613]

On another note, I ALWAYS upload new firmware over an ethernet connection. The router and my computer are on a UPS. I want to minimize any chance of corruption during the process.

 

[SomeWhereOverTheRainBow]

Why can't ipv6 access the internal network on the external network through https? I have turned off the firewall, and ping the IPv6 address is normal. But I can't access the router's management interface, nor can port forwarding and dmz. However, the nas of the intranet can also be directly accessed through the ipv6 address.

My router is GT-AX6000

The router WebUI interface only binds to ipv4. You can determine this by, netstat -nlp | grep lighttpd Notice that it only binds to tcp and not tcp6, where as your Nas probably binds to both tcp and tcp6 which is why you can access its interface over ipv6