What's new

Smart connect: Using 2.4ghz as fall back for clients far away.

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

leerees

Senior Member
Smart connect comes setup with the default values as follows:

2.4ghz RSSI = Greater than -62
5Ghz RSSI = Less than -82

I can't get my head round that. Surely, the overlapping numbers is what's causing our STA's to constantly bounce around the bands.

I want our network to use 2.4Ghz only for clients that are out of range of useful 5ghz.

Therefore, shouldn't it actually be setup like this...

2.4ghz RSSI = Greater than -70
5Ghz RSSI = Less than -70

Am I correct in assuming a client that doesn't support 5Ghz won't be booted off the the 2.4ghz network if it's RSSI reaches the 5ghz trigger point?
 
Last edited:
No. You can't compare RSSI levels between the two bands.
 
No. You can't compare RSSI levels between the two bands.
Of course, now it makes sense.

I think I have a little bit too much 2.4ghz for our liking.

Lets say I accidentally set the 2.4ghz threshold too high. What happens if an STA's RSSI meets the threshold for too high 5ghz but it's RSSI isn't low enough to meet the joining threshold for 2.4ghz, would it be booted off completely, or will it be allowed to stay on 5ghz until accepted by 2.4ghz?
 

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