Has anyone gotten the noise-floor-threshold to work? We have tried this before without success and just setup RB511/CM9(Station Mode, 5180mhz) and an RB532/CM9 (AP-Bridge Mode, 5180mhz) and set the “Noise Floor Threshold” to -127 thinking that it would break the connection. Rebooted - connections came back up. Power cycled - connections came back up. The connection always stays up. Shouldn’t a -127 setting cause all rf to be considered noise and, therefore, break the client connection? We are trying to make sure the radios ignore noise on our wireless backhauls where we have great signal strength (i.e. -65dBm) and a high noise floor (i.e. -79 to -88dBm).
A similar setting worked magic when we used it on a Trango AP and we were hoping for the same results with Mikrotik.
Hmm, the noise-floor-threshold does tell RouterOS to consider everything BELOW the configured value as noise. So you effectively told it that everything BETTER than -127 dBm has to be “signal”. And that way you won’t kill an otherwise good RF link.
You could set noise-floor-threshold=-50, then you would have to have a signal level above -50 dBm to get a link established.
I’ve used this on 2.4 to get DHCP client to work better on some APs: set at -95 or so. Should act as a squelch with -127 wide open. Don’t know as docs are slim. I’ve set it higher (tighter) than the connected signal and not disconnnected.
So, if a client is showing -40dBm signal strength in the AP and the noise-floor-threshold is then set to -35dBm, shouldn’t the client be disconnected?That is, the radio should ignore all rf that has signal strengh at or below the noise-floor-threshold?
I don’t have any mini-PCI cards with the Atheros 5211 chipset, but I tried it with set of cards that have the 5213 chipset and the noise-floor-threshold was ignored no matter whether it was set to 127(default setting), 0, -30 or -127. What mini-PCI cards have the 5211 chipset?
I think it will be very hard to find these cards.
Right now only connection list contains entry min-signal strength, but the same matcher is implemented in RouterOS3 in ‘access-list’. It means that RouterOS3 will allow to manage connected clients per signal-strength.
