Hi everyone,
I upgraded routeos to 7.13 and encounter DFS problem in new CAPsMAN. New CAPsMAN persists in doing DFS check at channel 48-64, while old CAPsMAN does not. Setting "all" in Skip DFS channels or/and changing country does not work. How to get rid of DFS? Thhanks.
Re: Annoying DFS at channel 48-64
Do you have it configured to use a specific, non- DFS channel? If not, you should.
-
-
enigma1939
just joined
- Posts: 20
- Joined:
Re: Annoying DFS at channel 48-64
I create channel 36(5180mhz)-64(5320mhz) and channel 149(5745mhz)-165(5825mhz), one by one. These channels and frequencies are all legal in local. I pick up 4 channels with width 20/40/80mhz but channel 48-64 activate DFS, detecting military radar signal in 1 minute.Do you have it configured to use a specific, non- DFS channel? If not, you should.
This is local 5G channel and frequency compliance, which yellow marked are all legal.
https://img-blog.csdnimg.cn/de52600dd03 ... db3c07.png
Re: Annoying DFS at channel 48-64
Since you went into trouble of configuring frequencies ... as you found out that some are troublesome, why don't you simply omit those from the list?I create channel 36(5180mhz)-64(5320mhz) and channel 149(5745mhz)-165(5825mhz), one by one.Do you have it configured to use a specific, non- DFS channel? If not, you should.
It doesn't matter if the regulatiobs say it's legal (if it's illegal, then you better don't use oart of spectrum even if it seems to be unused), fact us that cheap wireless devices aren't good at identifying non-802.11 signals and if some are detected on DFS channels they better assume it's radars. Yes, it would be nice if ROS remembered that it detected signals and avoid those channels, but we have what ve've got.
-
-
enigma1939
just joined
- Posts: 20
- Joined:
Re: Annoying DFS at channel 48-64
I wish ROS would be intelligent enough to automatically allocate channel, frequency, width and so on depending on local EM environment but yet it is not. I tried and found channels got high overlapping degree or widths got too narrow. It must be attributed to lack for wireless resource rather than ROS but I wish ROS would be able to forget DFS or let end-user to get rid of DFS.Since you went into trouble of configuring frequencies ... as you found out that some are troublesome, why don't you simply omit those from the list?
I create channel 36(5180mhz)-64(5320mhz) and channel 149(5745mhz)-165(5825mhz), one by one.
It doesn't matter if the regulatiobs say it's legal (if it's illegal, then you better don't use oart of spectrum even if it seems to be unused), fact us that cheap wireless devices aren't good at identifying non-802.11 signals and if some are detected on DFS channels they better assume it's radars. Yes, it would be nice if ROS remembered that it detected signals and avoid those channels, but we have what ve've got.
Re: Annoying DFS at channel 48-64
As to skip DFS setting: ROS, being the kind which really allows user to fine tune things and doesn't offer too much of "click and forget" functionality, seemingly assumes that if you manually configure frequency list then you "know better" and uses that frequency list despites the "skip-dfs-channels" setting. And IMO that's the right thing, if you start with manual overrides, you must know what you're doing.
-
-
enigma1939
just joined
- Posts: 20
- Joined:
Re: Annoying DFS at channel 48-64
To some extent, I know what I did. I was just wondering why all my manual settings worked smoothly in old CapsMAN while something wrong popped-up in new CapsMAN. I am not a designer and cannot understanding the background logic.As to skip DFS setting: ROS, being the kind which really allows user to fine tune things and doesn't offer too much of "click and forget" functionality, seemingly assumes that if you manually configure frequency list then you "know better" and uses that frequency list despites the "skip-dfs-channels" setting. And IMO that's the right thing, if you start with manual overrides, you must know what you're doing.