Date: Mon, 27 Jun 2011 17:33:50 +0800 From: Adrian Chadd <adrian@freebsd.org> To: freebsd-wireless@freebsd.org Subject: DFS STA/Hostap behaviour; issues! Message-ID: <BANLkTinEvwjFsKuT8hvgWO391awnwXb69A@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
After bernhard and I discussed this a bit, we came to the conclusion this is papering over bug/bugs. So what I've discovered thus far: * If a radar event occurs in CAC, another CSA doesn't go out - the AP just changes channel * If a STA receives a CSA for a DFS channel and the hostap enters CAC, it doesn't immediately send beacon frames, so bmiss is never triggered. However, because of this, if the hostap shuffles away to another channel within the CAC time, the STA doesn't ever get an initial beacon to configure the beacon config from, and thus the STA never generates a bmiss; which means it never initiates another channel scan. Getting back to the original bug: The hostap is actually sending the correct channel in the new beacon frames but there's currently no code in sta_recv_mgmt() to update the bss channel. That should occur (and similarly occur for ibss/mesh modes as well.) Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTinEvwjFsKuT8hvgWO391awnwXb69A>