[ath9k-devel] IBSS can't beacon after rejoin / regression in TSF syncing code?

[Antonio Quartulli <antonio@meshcoding.com>]

On 28/01/14 02:41, Sujith Manoharan wrote:
> Simon Wunderlich wrote:
>> Yeah, this patch works for my case. I'm not completely sure why we only unlink 
>> for this special case (no stations & bssid = zero), I don't see why it would 
>> hurt to always throw away that BSS and rescan on the next join?
>>
>> I'm CCing Teemu, who introduced this roughly 3.5 years ago ("mac80211: remove 
>> BSS from cfg80211 list when leaving IBSS", 
>> 5ea096c0c85e80335889539899af9a4717976e0b) , maybe he can explain it more.  I 
>> couldn't understand that from the commit message and the corresponding mail 
>> thread.
> 
> I think we can drop the BSS when we leave an IBSS network. The only advantage
> of not doing so is a slightly faster join command that is given after
> leaving - if there are more than 2 nodes in the cell, that is. But it would
> be prudent to scan and check if the network exists before trying to join it,
> so I'll send the patch for review.

Right now no scan takes place if you specify bssid and freq (+
fixed_freq attr). Then no matter if the BSS is already the scan list:
the join command will be fast.


Cheers,

-- 
Antonio Quartulli

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140128/e3e33ee1/attachment.pgp