Feedback: Solved Repeater mode setup on ASUS Aimesh Network

Router
1

Just a heads up on my trials and solution with an ASUS (RT-AX88U Pro with RT-AX3000 Node) AiMesh system when trying to add a Beryl AX (MT-3000) as a Repeater.

What I found was that the AiMesh kernel module intercepts and drops the Beryl's DHCP packets because its 5GHz (or 2.4GHz) MAC looks like an unrecognised mesh client, preventing it from ever getting a gateway.

The solution was to add the MAC to amas_no_monitor_sta_list on the ASUS, as follows.

Issue these from the Main ASUS Router's SSH CMD Line (the MACs are your Factory 5Ghz and 2.4GHz MACs resp). FYI, it did work natively with 2.4Ghz, it never worked with 5Ghz until I issued this:

nvram set amas_no_monitor_sta_list="92:BB:CC:DD:EE:FF 9E:BB:CC:DD:EE:FF"
nvram commit
service restart_wireless

Revised working solution in post below

1 Like
2

Hi

Thanks for sharing and for providing the solution!

5

Spoke too soon; works on 2.4GHz, still not on 5Ghz.

Tried

  • 4.5.16 last known one to work with 5GHz apparently but that broke BOTH bands
  • 4.8.3 2026-03-23
  • Reverted to 4.8.2 beta 5.
  • Did not try OpenWRT.

I cannot believe that we cannot get a simple 5Ghz repeater working reliably on this thing, a Travel Router.

6

OK, with a bit more investigating, I have a solution that now really does work. The underlying problem was the same as in my first post, but I discovered if I selected one of my Guest Networks, the Repeater worked.

Underlying Problem

So, as per my first post above, the issue is the same:

i.e. the ASUS AiMesh kernel module monitors wireless clients on the main network (br0) that it suspects may be wireless mesh nodes — specifically those sending DHCP requests with certain MAC characteristics — and when it cannot confirm them as valid AiMesh nodes, it simply intercepts and silently drops their DHCP requests, preventing e.g. a repeater device from obtaining a gateway and DNS server.

This prevented the GL.iNet Beryl AX from obtaining a gateway/DNS via DHCP when connecting as a 5GHz repeater to the MAIN Network (a combined SSID on Smart Connect), leaving it with no internet., despite being associated and showing an IP in the network map.

The Guest network set up using Guest Network Pro (NETGuest) worked on both bands because it runs on br52, completely outside the AiMesh module's scope.

Solution

On the Beryl AX GL.iNet admin panel, go to Internet → Repeater → Modify → Manually Set Static IP and configure:

  • IP: 192.168.x.yyy
  • Gateway: 192.168.x.1
  • DNS: 192.168.x.1
  • Netmask: 255.255.255.0

By assigning a static IP, the Beryl bypasses DHCP entirely — no discover packets are sent, so the AiMesh module has nothing to intercept, and the connection works perfectly on both 2.4GHz and 5GHz.

Now a very happy camper. Hope this helps someone else.

1 Like