I just replaced an older radio “Non MT” that was running DFS due to a lightning strike. I replaced it with an MT link with two R52Hn’s running Ros 5.4. I set the link to the same frequency our old equipment was running on 5260Mhz and enabled DFS radar detect. For some reason it appears that with Radar detect enabled the link defaults to 5180Mhz instead of what I have it set to. Any ideas here?
Chadd
DFS detected that this channel is the less used and started to operate. If you want you can play with the scan-list option to specify what range to use for DFS.
From what I can tell 5180 is the only channel it is checking for radar on. I have it set t0 5260 and when the interface is enabled it says scanning for radar on 5180 instead of 5260.
So if I set a scan list on the side that is set to bridge those are the frequencies that will be used and the actual frequency setting in the wireless tab doesn’t mean anything when using DFS?
Yes.
That did it.
Thanks,
Chadd
Radar only operates on 5600-5650Mhz, so the detection is probably due to self or co-location interference. We had the same issues with our Canopy 5.2 AP’s, and its cause was self-interference from mounting the AP’s too close to each other.
So when you have DFS set to radar detect is it looking for actual radar or just seeing if there is noise on the channel?
Does it meet the current requirements for DFS in the states or not?