[Official Release] AiMesh Firmware v3.0.0.4.384.10007 for All Supported Products
- Thread starter lovehikki
- Start date
- Status
arthurlien
Very Senior Member
Basically, I don't think the WPS procedure is proceeding with in all the time. If this is true, you can try to trigger WPS in your client device and it will be pairing successfully.
BTW, I still will check with team.
我從使用 Tapatalk 的 ASUS_Z012DA 發送
BTW, I still will check with team.
我從使用 Tapatalk 的 ASUS_Z012DA 發送
RandomName23
Regular Contributor
WPS seems to be required to setup your nodes as you don't have to go into any UIs and specify your Wifi password to have the nodes connect wirelessly. I'm guessing that WPS would also then be used anytime you changed your wireless password to allow to the nodes to connect with the new settings. I can't imagine any scenario where it should be required outside of those two scenarios.Well, @arthurlien has not stated that it is necessary, so unless they were hiding this fact, then I assume it's not actually necessary for the mesh to work. If it *is* necessary, they really shouldn't hide that fact because a) apparently even a dummy like myself can quickly tell it's on, b) it is a security threat that people should be fully aware of, and c) it goes completely counter to the manual user settings (i.e., it doesn't give the behavior a user would expect, thus looks like a bug).
Really, I can't think of any reason we can't have it closed up or, if it is required, confirmation of such a requirement from official sources. I guess we'll have to wait and see what @arthurlien has to say when he gets back from partying.
Pretty sure @dabears has already said he confirmed it still works.
arthurlien
Very Senior Member
Don't worry about it, I still will discuss with team.
If you would like to do some test, you can try to activate WPS in your client. Than see the results.
我從使用 Tapatalk 的 ASUS_Z012DA 發送
ROBERT CARLSON MD
New Around Here
ROBERT CARLSON MD
New Around Here
Currently, running firmware 3.0.0.4.384_20308 with 2 RT-AC68U meshed together. The older AC68U with hardware version A2 was very hard to update and kept looping back to the same countdown screen and then rebooting over and over again. I'm worried about ever trying to update it again.
The mesh seems to be working fairly well, but I have a question about future firmware updates: When an update comes out, will all the devices in the mesh be updated automatically?
-- R Carlson MD
The mesh seems to be working fairly well, but I have a question about future firmware updates: When an update comes out, will all the devices in the mesh be updated automatically?
-- R Carlson MD
RandomName23
Regular Contributor
You have to perform the update but all the mesh nodes can be updated from a single location in the main router UI.
Richard Li
Regular Contributor
I tried, you can never paired properly if you enable MAC address filtering. And MAC address filtering has a bug now which is now not working in my configuration RT-AC88U as AP and RT-AC68U as node. The 68U just will not accept any wifi connection when MAC filtering is enabled.
ASUS team can now reproduce this problem, need to wait for them to fix this issue.
ROBERT CARLSON MD
New Around Here
ROBERT CARLSON MD
New Around Here
Is it necessary or desirable to use the same SSID for both bands? I noticed on the marketing pages that they show only one "SSID-ASUS-AIMESH" signal in their example... ???
-- R Carlson MD
-- R Carlson MD
RandomName23
Regular Contributor
Personal preference
I went through the steps in flashing 2 ASUS TM-AC1900 routers to RT-AC68U with firmware Version 3.0.0.4.384.20308 to set up an AiMesh network. Both have been successfully flashed. I was able to set one as the router but not able to search the other router to set it up as a node. Can someone help me with this issue? Thanks.
ROBERT CARLSON MD
New Around Here
I just did the same thing today. It's a bit confusing.
The trick is to first update the new node device to the latest firmware, and then reset it back to the factory default settings. Don't worry about configuring the node in any way and boot it up. Place it near the AIMesh router with no ethernet cables connected. Go into the router AIMesh settings and search for another device, and it should pop up. After it configures the node, you can place where you want. After it's set up, and you want to use an ethernet backhaul, make sure you plug the lan ethernet cable into the node's WAN port, NOT one of the lan ports. Weird, but it works.
-- R Carlson MD
The trick is to first update the new node device to the latest firmware, and then reset it back to the factory default settings. Don't worry about configuring the node in any way and boot it up. Place it near the AIMesh router with no ethernet cables connected. Go into the router AIMesh settings and search for another device, and it should pop up. After it configures the node, you can place where you want. After it's set up, and you want to use an ethernet backhaul, make sure you plug the lan ethernet cable into the node's WAN port, NOT one of the lan ports. Weird, but it works.
-- R Carlson MD
OzarkEdge
Part of the Furniture
It's desirable. It's not necessary. And under the circumstances, it's not advisable at this time in AiMesh development, imo, particularly if you are using nodes that do not support SmartConnect aka band selection/steering and have dumb/stubborn wireless clients.
With simple IoT devices that you may have less control over, I think you are better off configuring/forcing them to use one SSID/WLAN; otherwise, they might connect to another SSID/WLAN that you intend for other clients.
Finally, if you experiment with using same SSIDs and then switch to using different SSIDs, you will likely find that wireless clients connect a bit more quickly... you have done the band steering for them... and it appears that some wireless clients are better at connecting to the better of two different SSIDs than they are at connecting to the better of two identical SSIDs. And you'll spend less time inspecting/assessing wireless client connections.
OE
make sure to convert original_cfe.bin to 1.0.2.0 US AiMesh not just 1.0.2.0 US
if you did not go back to step 10 and re-do the conversion.
Last edited by a moderator:
When can we expect KRACK fix on AC86U? This model is getting updates pretty late, comparing to other models.
arthurlien
Very Senior Member
Have you check ASUS web side ? it already fixed in 382.18219 and newer version.
Version 3.0.0.4.382.182192017/10/2455.48 MBytes
ASUS RT-AC86U Firmware version 3.0.0.4.382.18219
Security fixed
- Fixed KRACK vulnerability
- Fixed CVE-2017-14491: DNS - 2 byte heap based overflow
- Fixed CVE-2017-14492: DHCP - heap based overflow
- Fixed CVE-2017-14493: DHCP - stack based overflow
Ok, so AC88U got KRACK fix (very) late, not till 384.20379. Got it.
Jim_Kirk
New Around Here
Hello All,
New user to the forum and have just set up my AiMesh with 3 devices:
Prior to the AiMesh setup I had a router and two AC5300's set up as wired AP's. Lot's of SSID's to look at as I moved around.
My ISP is Comcast and the connection to the house is both Fiber and Cable. I use the Fiber connection into the house for my home network (cable for TV and phone with cable ethernet as a backup if needed).
Fiber provides a static IP and gives me a 1 G ethernet connection(1G up and down) to the Comcast provided Juniper Switch which is in the house not on an outside wall. Setup is: Fiber to the house into Juniper>Juniper 1 gig ethernet port wired to AC5300 Router. Juniper also gives me a 2G fiber port with a dedicated static IP but I'm not networking that port and I only use it with an optical cable for 1 computer.
About 16 wireless and 25 wired clients which I can see in the IOS ASUS Router APP. As I roam around the house (with my iPad or iPhone) I can see in the IOS APP that there is handoff between router and nodes and it seems to be working. Not as good as when I was doing it myself by switching manually but not too bad this early in the FW release cycle.
So far, and that's a very limited time, I've seen that some wireless clients don't show and with only 1 device moving around for testing I see some clients move.
So, two questions at this point.
New user to the forum and have just set up my AiMesh with 3 devices:
- AC5300, FW: 3.0.0.4.384_20379, Router
- AC5300, FW: 3.0.0.4.384_20379, Node 1, wired to Router
- AC5300, FW: 3.0.0.4.384_20379, Node 2, wired to Router
Prior to the AiMesh setup I had a router and two AC5300's set up as wired AP's. Lot's of SSID's to look at as I moved around.
My ISP is Comcast and the connection to the house is both Fiber and Cable. I use the Fiber connection into the house for my home network (cable for TV and phone with cable ethernet as a backup if needed).
Fiber provides a static IP and gives me a 1 G ethernet connection(1G up and down) to the Comcast provided Juniper Switch which is in the house not on an outside wall. Setup is: Fiber to the house into Juniper>Juniper 1 gig ethernet port wired to AC5300 Router. Juniper also gives me a 2G fiber port with a dedicated static IP but I'm not networking that port and I only use it with an optical cable for 1 computer.
About 16 wireless and 25 wired clients which I can see in the IOS ASUS Router APP. As I roam around the house (with my iPad or iPhone) I can see in the IOS APP that there is handoff between router and nodes and it seems to be working. Not as good as when I was doing it myself by switching manually but not too bad this early in the FW release cycle.
So far, and that's a very limited time, I've seen that some wireless clients don't show and with only 1 device moving around for testing I see some clients move.
So, two questions at this point.
- Just curious if there is anything, in particular, I might want to be looking for which might help?
- Also, I see ASUS recently updated (March 5, 2018) this FAQ "[AiMesh] How many AiMesh nodes can be added to an AiMesh system?" https://www.asus.com/us/support/FAQ/1035085
This confuses me. If I use wired connections to the AiMesh router is 2 the maximum number of nodes I can have? Might be nice to add a third wired to the router.
Last edited:
- Status
Similar threads
- Locked
- Deleted member 77025
- ASUSWRT - Official
Similar threads
Similar threads
-
-
ASUS RT-AX86U Pro beta release 9.0.0.6.102_37342 ?
- Started by Phil Dach
- Replies: 7
-
Release ASUS GT-BE98 Pro Firmware version 3.0.0.6.102_37839 5-8-2025 release
- Started by cc666
- Replies: 18
-
-
ASUS ROG Rapture GT-AXE16000 10G port 1 as WAN link in Aimesh
- Started by drabisan
- Replies: 3
-
-
AiMesh with Guest WiFi and a Switch - Configuration and Best Practices
- Started by sandiegoboy
- Replies: 7