linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Cavallari <Nicolas.Cavallari@lri.fr>
To: Antonio Quartulli <antonio@open-mesh.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Will Hawkins <hawkinsw@opentechinstitute.org>
Subject: Re: [PATCHv3 2/2] mac80211: in AD-HOC mode wait for the AUTH response
Date: Mon, 08 Apr 2013 09:53:55 +0200	[thread overview]
Message-ID: <51627793.1040505@lri.fr> (raw)
In-Reply-To: <20130407211654.GA6083@open-mesh.com>

On 07/04/2013 23:17, Antonio Quartulli wrote:
> Hi all,
> 
> let's resurrect this thread :)
> 
> On Thu, Jan 31, 2013 at 06:26:13AM -0800, Johannes Berg wrote:
>> On Thu, 2013-01-31 at 15:18 +0100, Nicolas Cavallari wrote:
>>
>>>> I think that's acceptable, but if it requires a wpa_s change anyway we
>>>> could just implement reboot detection there instead of adding all these
>>>> new events etc.? I.e. rather than having a new supplicant say "OK I will
>>>> listen to the right event when handling reboot detection", it could just
>>>> use the existing infrastructure and implement it itself?
>>>
>>> Well i already have wpa_supplicant patches for that. Might just need to clean that up a
>>> bit so it's at least configurable.
>>>
> 
> Would you mind sharing this code?

Well yes, i just need to untangle it with some other local policies ;)

> Maybe I can help and offload some work. :)
> Anyhow I did not understand how you can detect a node reboot from userspace if, as
> you stated, wpa_s is not able to distinguish encrypted from un-encrypted frames.

Well, you do it the same way as you do in the kernel, using auth frames. Except you're not
in the kernel.

>>> But now i'm reminded that transmitting management frames from userspace requires a
>>> frequency. For wpasupp to be race-free during ibss merges, we should have a way to
>>> transmit management frames to the current bss without specifying a frequency...
>>
>> That seems reasonable.
>>
> 
> This is a common problem I faced in other contexts too...

I sent a patch shorty after this message, trying to solve the problem, except Johannes
pointed out that it could still introduce races, at least in some non-mac80211 drivers,
the most problematic being ath6kl. I don't have any ath6kl hardware here, and i don't like
patching things that i can't test.

  reply	other threads:[~2013-04-08  8:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 13:40 [PATCHv3 1/2] cfg80211: add the new IBSS_STA event Antonio Quartulli
2012-12-10 13:40 ` [PATCHv3 2/2] mac80211: in AD-HOC mode wait for the AUTH response Antonio Quartulli
2012-12-28 14:51   ` Johannes Berg
2013-01-02  6:32     ` Antonio Quartulli
2013-01-02  9:40       ` Nicolas Cavallari
2013-01-07 11:40         ` Antonio Quartulli
2013-01-07 13:16           ` Nicolas Cavallari
2013-01-25 22:05             ` Johannes Berg
2013-01-26 12:09               ` Nicolas Cavallari
2013-01-29 11:37                 ` Johannes Berg
2013-01-29 13:59                   ` Nicolas Cavallari
2013-01-29 21:50                     ` Will Hawkins
2013-01-31 13:34                     ` Johannes Berg
2013-01-31 14:18                       ` Nicolas Cavallari
2013-01-31 14:26                         ` Johannes Berg
2013-04-07 21:17                           ` Antonio Quartulli
2013-04-08  7:53                             ` Nicolas Cavallari [this message]
2013-04-08  9:11                               ` Antonio Quartulli
2013-01-31 14:32                         ` Antonio Quartulli
2013-02-01 17:11                         ` [PATCH] {cfg,nl}80211: tx_mgmt: use current bss channel if omitted Nicolas Cavallari
2013-02-04 16:04                           ` Johannes Berg
2013-02-04 17:15                             ` Nicolas Cavallari
2013-01-03 21:05       ` [PATCHv3 2/2] mac80211: in AD-HOC mode wait for the AUTH response Will Hawkins
2013-01-25 21:45         ` Johannes Berg
2013-01-29 21:54           ` Will Hawkins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51627793.1040505@lri.fr \
    --to=nicolas.cavallari@lri.fr \
    --cc=antonio@open-mesh.com \
    --cc=hawkinsw@opentechinstitute.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).