What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Beta Asuswrt-Merlin 3006.102.5 Beta is now available

Trying to upgrade my GT-AX6000 from 3006.102.5_beta1 to 3006.102.5_beta2.

For more than 15 minutes it displays "Please wait, Applying Settings..." and when I ssh into the router it still reports 3006.102.5_beta1.

How long should I wait before taking any actions? (Which?)
Accidentally hit reload in the tab displaying that and got back to the router login page (was still on beta 1).

Second upgrade attempt worked fine.
 
Upgraded from 3006_102.4 to 3006_102.5_beta1.

Cpu temps went from 60s on 102.4 to 80s on 102.5_beta1. Side note, I had high temps in the 80s on 3004 firmware as well until I upgraded to 3006.

Cpu usage is low. Never more than 50% when I'm watching the usage.

Rebooting had no effect.

Any suggestions? Is there somewhere I can go to see diagnostic data as to why it might be high all of a sudden?
 
Last edited:
Try the beta2
i just saw the beta 2 released. Downloaded and it had no effect. probably going to factory reset next weekend as the post above suggested.
 
Forgot my router model. I apologize. Its axe16000
 
Does anyoneknow if the wireless drivers are the same on Beta 2 as the newly release firmware for the GT-BE 98PRO?

CC
 
Site Survey not working. Left it quite a bit to discover networks but no luck.

GT-AX6000 Beta2
Make sure you don't have disabled bands or MAC filtering in places - they will break the Site Survey.
 
Make sure you don't have disabled bands or MAC filtering in places - they will break the Site Survey.
I have MAC rejection filters on every network and vlan in my setup on my GT BE 98PRO. The site survey works fine, took about 15 seconds to populate but it does work

CC
 
This is still happening in beta2.

52 devices connected via my server (0 with .4). And rising.
100+ "clients" in total... and rising (stable at 20-30 with .4).

I don't see these "clients" anywhere. Just the numbers increasing until they drop and start counting up again.
Maybe just visual but it does not feel right.

Edit 164-128=36 is probably near the right number of real clients. Dropped to 0 connected through and now counting up again, and repeats indefinitely. ;)

This has suddenly stopped happening when checking again now. So that's... good I guess.
Haven't tried fresh boot yet, close to 8h uptime and things works.

Edit: Just kidding! It's doing it again. No reboot.
 
Last edited:
Still experiencing issues with internet access and the display of active ports. I installed beta 2 on my BE92U and performed a "hard reset" (WPS & power). The issues that I observed were described in messages 7 & 12.

The following outlines the "Ethernet Ports" display issue. The table is the mapping seen if "plugged into" this port, it "appeared on" this port.
- Plugged into 10G appeared as if on 10G WAN/LAN-1.
- Plugged into LAN-1 appeared as if on LAN-4.
- Plugged into LAN-2 appeared as if on LAN-1.
- Plugged into LAN-3 appeared as if on LAN-2.
- Plugged into LAN-4 appeared as if on LAN-3.

I performed the following three tests:
1) Primary WAN set to "Auto Detection"
- Plugged into 10G -- internet was available.
- Internet access was not available on any other port.
2) Primary WAN set to "10G WAN/LAN-1"
- Plugged into 10G -- internet was available.
- Plugged into LAN-1 -- internet was not available.
- Internet access was not available on any other port.
3) Primary WAN set to "2.5G WAN/LAN-1"
- Plugged into LAN-2 -- internet was available.
- Internet access was not available on any other port.
 
Did an upgrade from beta1, then proceeded to do a full aimesh system reboot, and things seem to have come up and running well. Will watch over the week to see how things go.
 
Updated from beta 1 to beta 2 on my AX-86U Pro without issue, but just noticed that if I view the client list from the Network Map, that all of my wireless clients that have static IPs are showing as DHCP connections. All of the wired clients with Static IPs are labelled correctly as "Static".

Not sure if this is a change from the first beta, or indeed a change at all, but figured it was worth mentioning.

ASUS client list implementations have always been a little flakey for me, and it might also be complicated by the fact that I am running an RT-AC86U as a wired AiMesh node (I seem to recall running any sort of node would always confuse the client list). Also running v1.0.8 of YazDHCP, which might be another complication.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top