[Official Release] AiMesh Firmware v3.0.0.4.384.20308 for All Supported Products

[RandomName23]

I used 60 seconds, but seems once the router locks up, it will not release until reboot.

This is what I found as well, once locked you have to reboot to release. I haven’t tried if it is tied to MAC address or not. So make a couple tries, change Mac, make a couple tries, change Mac, etc.

I just wish there was something in the logs or in aiprotection that WPS became locked.

 

[RandomName23]

I have decided to go back and turn on WPS for my AiMesh Nodes. I found that there are so many NVRAM WPS related settings which I have no clue what they might do to AiMesh; which might impact/break AiMesh that has been running very well for me now

WPS is only used to connect to a wireless network so once the connection is established unless you are changing passwords or something WPS should not be needed.

 

[Richard Li]

This is what I found as well, once locked you have to reboot to release. I haven’t tried if it is tied to MAC address or not. So make a couple tries, change Mac, make a couple tries, change Mac, etc.

I already used the command

wifite -mac

in which it will randomize the mac address, still no luck. Will try something more and see how it goes.

 

[indark]

So far it has been an interesting and fun experience to try out aimesh, however, it's not completely reliable yet for me as I will start experience poor speed and high latency (like 1k+ ms)till I reset the node.

I suspect it might due to the compatibility between ASUS PCE-AC88 and first gen RT-AC68 (probably weakest CPU for all the aimesh router?).
Speed is normal when I remove the AC68 node and connect to AC3100 main router.
And it will be fine for a while when I reestablish the connection between node and main router.
Then start slows down over time.

I often sees spams of

Feb 22 21:43:25 roamast: discover candidate node [](rssi: -55dbm) for weak signal strength client [](rssi: -59dbm)
Feb 22 21:43:25 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)

and start experience extremely slow speed on say youtube after a day or 2, depends on my internet usage
my guess is that they eats up all the resources as I later had completely kernel dump and the aimesh node gone completely till reset.

I had sent the complete syslog via email and hopefully it will help to id the issue.

keep up the good work and hopefully it will soon be mature enough for me to continue use.

 

[LimJK]

I used 60 seconds, but seems once the router locks up, it will not release until reboot.

Richard,

Thanks

 

[LimJK]

WPS is only used to connect to a wireless network so once the connection is established unless you are changing passwords or something WPS should not be needed.

Thanks.

I actually turnoff WPS of AiMesh Router via the GUI. However, I have decided to leave the WPS state of the AiMesh Nodes as it were by default; as I discovered that there are so many other WPS related NVRAM settings which I have no clue what they are for. I just want to avoid the scenario this can break AiMesh that is working fine for me now.

 

[Quad80]

I used 60 seconds, but seems once the router locks up, it will not release until reboot.

Do you know how many attempts you made before it locked up? Previous evidence suggested only a handful of times (i.e., less than 10). I'm wondering if you saw the same.

Thanks for testing and reporting back!

 

[OzarkEdge]

Does the wireless backhaul connect time listed in the Wireless Log reset normally? I'm watching it and wondering what to expect.

By my observation, 2.4/5.0 wireless backhaul connect times do reset and are not in sync.

OE

 

[badbob001]

I'm not looking to disable all wifi, just the 2.4 GHz band.

So with aimesh enabled, you can't reach the management gui of the nodes, but you can still ssh into them (you may need to enable ssh on the master node first) and then run commands to enable/disable radios and even set their power level. I've only tried setting the power level and I think it works.

wl0 refers to the 2.4GHZ radio and wl1 refers to the 5GHZ radio. Not sure what wl itself is related to.

The nvram variables to turn on/off each radio are:

• wl_radio (???)
• wl0_radio (2.4GHZ)
• wl1_radio (5GHZ)

To see your current variable settings, try:

nvram show | grep _radio​

To turn off all radios:

nvram set wl_radio=0
nvram set wl0_radio=0
nvram set wl1_radio=0
nvram commit
reboot​

To turn on all radios:

nvram set wl_radio=1
nvram set wl0_radio=1
nvram set wl1_radio=1
nvram commit
reboot​

The transmit power level (1-100) variables are:

• wl_txpower=50 (???)
• wl0_txpower=50 (2.4GHZ)
• wl1_txpower=50 (5GHZ)

To see your current variable settings, try:

nvram show | grep power​

To set the radio to 50%:

nvram set wl_txpower=50
nvram set wl0_txpower=50
nvram set wl1_txpower=50
nvram commit
reboot​

 

[CootjeNL]

So with aimesh enabled, you can't reach the management gui of the nodes, but you can still ssh into them (you may need to enable ssh on the master node first) and then run commands to enable/disable radios and even set their power level. I've only tried setting the power level and I think it works.

wl0 refers to the 2.4GHZ radio and wl1 refers to the 5GHZ radio. Not sure what wl itself is related to.

The nvram variables to turn on/off each radio are:

• wl_radio (???)
• wl0_radio (2.4GHZ)
• wl1_radio (5GHZ)

To see your current variable settings, try:

nvram show | grep _radio​

To turn off all radios:

nvram set wl_radio=0
nvram set wl0_radio=0
nvram set wl1_radio=0
nvram commit
reboot​

To turn on all radios:

nvram set wl_radio=1
nvram set wl0_radio=1
nvram set wl1_radio=1
nvram commit
reboot​

The transmit power level (1-100) variables are:

• wl_txpower=50 (???)
• wl0_txpower=50 (2.4GHZ)
• wl1_txpower=50 (5GHZ)

To see your current variable settings, try:

nvram show | grep power​

To set the radio to 50%:

nvram set wl_txpower=50
nvram set wl0_txpower=50
nvram set wl1_txpower=50
nvram commit
reboot​

Now let's find a way to enable guest on the nodes through ssh.

Verstuurd vanaf mijn SM-N950F met Tapatalk

 

[OzarkEdge]

Now let's find a way to enable guest on the nodes through ssh.

Why? Because ASUS can't figure it out? Does it really make sense to hack AiMesh for its shortcomings at this time in its development?

I don't think so. Anyone running AiMesh should be glad it's working as it is, imo.

OE

 

[CootjeNL]

Why? Because ASUS can't figure it out? Does it really make sense to hack AiMesh for its shortcomings at this time in its development?

I don't think so. Anyone running AiMesh should be glad it's working as it is, imo.

OE

I agree that Asus should fix it, but I'm pragmatic and need a workaround. Although I understand that Asus still need to fix some issues and make it lot more stable.

Verstuurd vanaf mijn SM-N950F met Tapatalk

 

[OzarkEdge]

I agree that Asus should fix it, but I'm pragmatic and need a workaround. Although I understand that Asus still need to fix some issues and make it lot more stable.

If fixing it was as easy as flipping some settings, it would be working by now. I admire your faith in the hackers!

I need guest isolation, too! I can't remember if I had guest networks on my repeater mode node... I didn't need it then.

OE

 

[RandomName23]

If fixing it was as easy as flipping some settings, it would be working by now. I admire your faith in the hackers!

I need guest isolation, too! I can't remember if I had guest networks on my repeater mode node... I didn't need it then.

OE

Guest networks are going to require much more than a few NVRAM settings. VLANs, routing tables, etc. for starters, definitely not something for the novice to try and configure.

 

[OzarkEdge]

Guest networks are going to require much more than a few NVRAM settings. VLANs, routing tables, etc. for starters, definitely not something for the novice to try and configure.

I suspect so... a good chunk of work remaining for ASUS.

And if they do release this, it may not run on an older router like the RT-AC68U, which does not support SmartConnect now.

I decided today to revert to unique SSIDs... it's a better fit all around at this time, especially with no SmartConnect band steering here.

OE

 

[bbunge]

RT-AC66U_B1 - recently switched to Merlin 384-3 to give it a try. Decided to go back to Asus 384-20308. Did factory default. Set up with auto setup via Firefox 58.02 64 BIT. After some initial settings changes the router restarted and I could not log in with the freshly entered user and password. Reset via power cycle and WPS button, entered SSID and user/password. Again could not log into the router. Did this two more times with the same results. Switched to Edge to configure but this time entered a different user/password and when the web gui came up I went to Admin/System and changed the user/password. Logged out of Edge and back in with Firefox OK. I had recently upgraded Firefox from Firefox ESR to Firefox Quantum. Never had issues with older version of Firefox!

 

[AlphaGator]

Is there an anticipated release date for the next firmware update?

 

[OzarkEdge]

I've noticed that wireless clients listed correctly in the router Wireless Log can be listed as wired or on the wrong band on the Network Map client lists. The Android app does not appear to exhibit these false listings, although its general lag in list update can muddy the issue.

The Wireless Log seems accurate; the Network Map client lists are regularly inaccurate.

OE

 

[AlphaGator]

I've noticed that wireless clients listed correctly in the router Wireless Log can be listed as wired or on the wrong band on the Network Map client lists. The Android app does not appear to exhibit these false listings, although its general lag in list update can muddy the issue.

The Wireless Log seems accurate; the Network Map client lists are regularly inaccurate.

OE

I've noticed this as well and have posted about it here.

 

[OzarkEdge]

I've noticed this as well and have posted about it here.

I am reporting that the Wireless Log and app appear to be accurate while the router Network Map client lists do not. I am not reporting missing nodes. I am not reporting nodes being listed as clients in the Network Map client lists.

If I had your installation with nodes missing and nodes being listed as clients, I would start over from scratch according to my install notes. If that did not help, I would not use AiMesh at this time.

OE