RT-AC68U Aimesh Node 2.4 Ghz not working?

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

JT Strickland

Senior Member
RT-AC86U w/ 384.16, RT-AC68U Aimesh node w/ same, Diversion, UiDivstats, Skynet, AiProtection, Scribe, UiScribe, Conmon, SpdMerlin, ScMerlin, Nsrum, NtpMerlin, OpenVPN selective clients

I don't think my 68U node is working on the 2.4 ghz frequency. How can I be sure since I can't access it directly? I have a lots of drops from weak signals in the log file that have just appeared, and I can't connect to the 2.4 ghz frequency network with clients out of the wireless range of the primary RT-AC86U router. I have separate networks established for the 2.4 and 5 ghz bands. How can I address it?
tia,
jts
 

CaptnDanLKW

Regular Contributor
Since you have separate SSID that means you are not using Smart Connect - something I've had problems with when mixing a 68U node in with an 86U main unit and another 86U node.

On your 86U use wifi radar --> Start Survey. You should see two entries for each SSID, the weaker signal one would be the node.

upload_2020-4-24_9-21-25.png


Dont forget to 'Start Data Collection' in the Site Survey Configuration screen. Then dont forget to turn it off.
 

JT Strickland

Senior Member
Since you have separate SSID that means you are not using Smart Connect - something I've had problems with when mixing a 68U node in with an 86U main unit and another 86U node.

On your 86U use wifi radar --> Start Survey. You should see two entries for each SSID, the weaker signal one would be the node.

View attachment 23022

Dont forget to 'Start Data Collection' in the Site Survey Configuration screen. Then dont forget to turn it off.

Thank You. I will take a look at that and see what I learn there to fix it.
jts
 

JT Strickland

Senior Member
Well, it is there, but I can't connect to it, right below the jones network. It shows only 5 ghz clients attached to my node.
And my log has a lot of these:

Apr 24 08:52:33 RT-AC86U-8F38 roamast: determine candidate node [xx:xx:xx:xx:xx:xx](rssi: -41dbm) for client [xx:xx:xx:xx:xx:xx](rssi: -82dbm) to roam
Apr 24 08:52:33 RT-AC86U-8F38 roamast: eth5: disconnect weak signal strength station [xx:xx:xx:xx:xx:xx]
Apr 24 08:52:33 RT-AC86U-8F38 roamast: eth5: remove client [xx:xx:xx:xx:xx:xx] from monitor list
Apr 24 08:53:23 RT-AC86U-8F38 ovpn-client1[4547]: TLS: tls_process: killed expiring key

network-24-2020-04-24 085450.png
 

JT Strickland

Senior Member
All is well now, for some reason my Node was stuck and clients couldn't join the 2.4 Ghz network through it, even though it was broadcasting to some degree.
A second reboot fixed it seems like, and I upgraded to 384.17 beta1 firmware while I was at it. No issues with this currently.
Thanks for the help.
jts
 

Latest threads

Sign Up For SNBForums Daily Digest

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