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

[JWoo]

I imagine you are still waiting for the GPL code.

This seems to be an issue for Asus. It is really surprising that, as but 1 example, most of the RT-AX58U variants are all on different GPL bases if I am looking at this correctly. 5 code bases for 7 routers which use the same basic PCB and chipset. That is a really expensive way to develop and maintain software.

RT-AX58U, 48908
RT-AX3000, 48908
TUF-AX3000, 48377
RT-AX82U, 48664
GS-AX3000, 43588
GS-AX5400, 46061

 

[SomeWhereOverTheRainBow]

This seems to be an issue for Asus. It is really surprising that, as but 1 example, most of the RT-AX58U variants are all on different GPL bases if I am looking at this correctly. 5 code bases for 7 routers which use the same basic PCB and chipset. That is a really expensive way to develop and maintain software.

RT-AX58U, 48908
RT-AX3000, 48908
TUF-AX3000, 48377
RT-AX82U, 48664
GS-AX3000, 43588
GS-AX5400, 46061

I just don't see how it is efficient as well.

 

[RMerlin]

This seems to be an issue for Asus. It is really surprising that, as but 1 example, most of the RT-AX58U variants are all on different GPL bases if I am looking at this correctly. 5 code bases for 7 routers which use the same basic PCB and chipset. That is a really expensive way to develop and maintain software.

It's all the same code base, just that builds are generated at different point in time. Since I release all models at once, that's why all my my models share the same GPL version. This has both advantages and disadvantages. For instance it takes a long time for them to test and build all models on that specific GPL for me, which means longer wait between my releases.

Asus has like 40-50 different models to support. They can't QA all of these models at the same time, hence their releases are staggered, and therefore based on a different version. So basically build a few models, while these go through QA the dev team continue working on the code. By the time they are ready to QA another batch of models, the code has progressed, hence a different version at that point.

 

[JWoo]

Gotcha. The upside is that routers are getting the latest corrections available when their firmware was compiled. The downside is that Asus winds up with lots of software variations in the field which can be rough on support teams.

 

[learning_curve]

Dirty flashed from the previous 386.5_2 on to the latest 386.7_alpha1-g8ee6420ea6 firmware

All running perfectly for me so far. Thanks again @RMerlin for everything to date.

 

[foxyserg]

Hello, my router RT-AX86U stopped turning on when updating from 386.5_2 to RT-AX86U_386.7_alpha1-g0ad1a4faae

 

[iJorgen]

Flashed Alpha 1 over 386.5_2 on my AX86U and got some issues. After a reboot I got a message saying I had to manually reboot the router. I did after a few minutes, but now I didn't get the logon screen (https).
When I logged in using the IP-address instead and looked around I saw that JFFS wasn't mounted. Probably why the cert and settings were not loading. Any tips or best thing is to do a nuke/reset?!

Update: Did a "Format JFFS partition at next boot" and now JFFS is back in business.
Update 2: After re-config of client names, manual assign IP's, network service filters, SSL-cert and scripts all has run fine the past 6 hours.

Also noticed that "debug logging" for WiFi seems to be activated again by Asus, like it was before for AX86U models.

Jun  5 08:41:02 kernel: CONSOLE: 146250.747 wl1: wlc_ampdu_recv_addba_resp: 20:df:b9:xx:xx:xx: Failed. status 37 wsize 64 policy 1
Jun  5 08:41:04 kernel: CONSOLE: 146252.738 wl1: wlc_ampdu_recv_addba_resp: 44:07:0b:xx:xx:xx: Failed. status 37 wsize 64 policy 1
Jun  5 08:41:04 kernel: CONSOLE: 146252.738 wl1: wlc_ampdu_recv_addba_resp: 44:07:0b:xx:xx:xx: Failed. status 37 wsize 64 policy 1
Jun  5 08:41:05 kernel: CONSOLE: 146253.735 wl1: wlc_ampdu_recv_addba_resp: b0:2a:43:xx:xx:xx: Failed. status 37 wsize 64 policy 1
Jun  5 08:41:05 kernel: CONSOLE: 146253.735 wl1: wlc_ampdu_recv_addba_resp: 44:07:0b:xx:xx:xx: Failed. status 37 wsize 64 policy 1

 

[kernol]

Hello, my router RT-AX86U stopped turning on when updating from 386.5_2 to RT-AX86U_386.7_alpha1-g0ad1a4faae

Flashed Alpha 1 over 386.5_2 on my AX86U and got some issues. After a reboot I got a message saying I had to manually reboot the router. I did after a few minutes, but now I didn't get the logon screen (https).
When I logged in using the IP-address instead and looked around I saw that JFFS wasn't mounted. Probably why the cert and settings were not loading.

I do hope this is not an indication that Asus have yet to resolve the nasty hiccup they had with some AX86U's getting nuked beyond repair on their last stock release ... https://www.snbforums.com/threads/rt-ax86u-bricked-after-update-version-3-0-0-4-386-48377.78437/ ???

They recalled that firmware for the AX86U and I can't find evidence that they have issued a newer release version since ?

 

[trecrunur]

AX86U bricked after 386.7_alpha1-g8ee6420ea6 OTA

 

[Samuel_1975]

AX86U bricked after 386.7_alpha1-g8ee6420ea6 OTA

i had just downloaded firmware for asus router rt-ax86u but hesitate to update it after your post of alpha version

have a good day hope you get your router running again

 

[trecrunur]

i had just downloaded firmware for asus router rt-ax86u but hesitate to update it after your post of alpha version

have a good day hope you get your router running again

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.

 

[Paul Smedley]

Installed fine on AX68U

 

[charlie2alpha]

So we got 2 reports already of bricked RT-AX86Us. Seems I'll be skipping this release, the first since many years but I will not risk my AX86U.

 

[Tvbaas]

AX86U bricked after 386.7_alpha1-g8ee6420ea6 OTA

@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?

 

[omrij]

Am I the only one facing issues with IPV6 (native)? It's not getting IPV6 PD.

GT-AX6000

 

[qiuyan81]

为什么ipv6通过https在外网是无法访问内网的？防火墙我已经关闭了，ping IPv6地址也是能正常的。但是不能访问路由器的管理界面，端口转发与dmz也不行。。但是内网的nas通过ipv6地址也是可以直接访问的。

我的路由器是GT-AX6000

 

[laracroftonline]

为什么ipv6通过https在外网是无法访问内网的？防火墙我已经关闭了，ping IPv6地址也是能正常的。但是不能访问路由器的管理界面，端口转发与dmz也不行。。但是内网的nas通过ipv6地址也是可以直接访问的。

我的路由器是GT-AX6000

We only give support to people that speak English

 

[qiuyan81]

We only give support to people that speak English

Is this racism?

 

[laracroftonline]

Is this racism?

No this is a rule of this forum.

 

[qiuyan81]

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