I have a request.
As I have 3 equal AIMesh, it would be nice to have the possibility to name them yourself. Or add more fixed names to the list.
Very strange. I don’t have that option. (We have different HW).You can do that already, assigning a custom name to a router (both router and AImesh nodes). Choose 'custom' from the list and then you can specify your own description for the choosen router.
Very strange. I don’t have that option. (We have different HW).
It's a scrollable list, try using the mouse wheel. RT-AC68U here.Very strange. I don’t have that option. (We have different HW).
Thanks. I’m using iPad, and it wasn’t obvious.It's a scrollable list, try using the mouse wheel. RT-AC68U here.
3.5 miles from each other? Via OpenVPN, or?
On AX-86U with "rough" Beta4 and before that Beta3. I'm seeing high memory use for both Beta firmwares: after rebooting eight hours ago, the memory usage has moved up from ~65% to 97%
Used 997 MB
Free 27 MB
Total 1024 MB
I haven't used Asus stock firmware, so don't know if stock is more stable for memory usage.
I am seeing the same thing on an AX-88U with Beta 3
RAM
Used 907 MB
Free 117 MB
Total 1024 MB
top
Scroll all the way to the bottom of the list of names/locations, you'll find "Custom", use that and name the nodes what you like.I have a request.
As I have 3 equal AIMesh, it would be nice to have the possibility to name them yourself. Or add more fixed names to the list.
Has Beta 4 for the RT-AX88U been released? i'm seeing discussions on beta 4 but don't see it anywhere. ThanksKnown issues:
- Lots of "messages suppressed" on RT-AX88U syslog when using Guest Network 1 (upstream issue, was reported to Asus. As a workaround use Guest Network 2 instead, though it won't be shared across AiMesh nodes)
RT-AX58U crashes when enabling the Trend Micro engine (missing flowcache userspace tool, fixed in beta 2)RT-AC3100 and RT-AC5300 networkmap/AiMesh/other issues (failed hardware validation, fixed in beta 2)VPN clients occasionally missing routes (possibly related to new route creation in OpenVPN 2.5, will test reverting to iproute2 for beta 2 on 2.6.xx kernels)Route issues when managing multiple VPN clients, even on HND models(Bug in OpenVPN 2.5's netlink implementation where the retrieved current default gateway is sometime from another client rather than from the WAN interface, reverted to iproute2 for all models in beta 3)Missing runner status on RT-AC86U (fcctl on early HND models don't report runner status, fixed in beta 3 by retrieving it in a different method)Missing Speedtest on RT-AX56U and RT-AX58U (This is by design, checking with Asus on the reason they are disabling it on these two models)- Let's Encrypt renewal issues (bug caused by a change in root CA by LE, fix being implemented upstream by Asus, awaiting updated code from them)
- WAN or OpenVPN UDP connectivity issues (Go to your WAN page and make sure your MTU is set to 1500 or 1492 (PPPoE) instead of being blank)
- Adaptive QoS issues on RT-AX56U/RT-AX58U (Fixed upstream, awaiting updated code from them)
- Adaptive QoS/Bandwidth Monitor issues on RT-AX86U (Fixed upstream, updated GPL hasn't been merged in yet)
DNS over TLS on both, and HTTPS with external cert and strong key length. DDOS active. One port forwarded. Accessed by sub-domain with login.
I've been using beta4 on my AX-86U. Aiprotection time scheduling seems to work just on web browsers but not for other services: whatsapp, spotify, ecc.On AX-86U with Beta4, AiProtection - Time Scheduling seems to be working as expected. A printer that was set for restricted internet could not access firmware update information over the internet, and after giving it one-hour access it's now updating its firmware.
I have the ac5300. I initially moved to 361 beta 1 a few weeks ago and had many issues. reverted back to 384.19 which is stable (did a factory reset to revert back). Today I dirty flashed to beta 3. So far all looks good. I have 25 IPs on the network, some ethernet, some on each of the 3 wifi networks. I have 3 other routers, one a wireless client bridge, and two ethernet connected APs. All is working. The network map shows correctly (was an issues with beta 1).
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!