public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lars Ericsson" <Lars_Ericsson@telia.com>
To: "'Ivo van Doorn'" <ivdoorn@gmail.com>
Cc: <hostap@lists.shmoo.com>, <linux-wireless@vger.kernel.org>,
	<rt2400-devel@lists.sourceforge.net>
Subject: RE: [Rt2400-devel] mac80211 / rt2x00 / rt61 and adhoc status
Date: Sun, 17 Aug 2008 22:42:38 +0200	[thread overview]
Message-ID: <059801c900a9$c9eee740$0b3ca8c0@gotws1589> (raw)
In-Reply-To: <059401c90071$d71609e0$0b3ca8c0@gotws1589>

> > > > > Two tests cases, but same behaviour:
> > > > > 1) Linx.git: 2.6.26 and wpa_supplicant 0.5.9
> > > > > 2) rt2x00.git: Version 2.2.0 and wpa_supplicant 0.5.9
> > > > 
> > > > Are any beacons going out? Is there anything in the logs which
> > > > indicates what is happening?
> > > > 
> > > 
> > > As you can se in the trace below, the configuration 
> > proceeds and the adhoc
> > > is created.
> > > The warnon might give some clues.
> > 
> > So how about those beacons? are they getting out?
> > 
> 
> After patching the wpa_suplicant (0.5.9) adhoc works.
> When first started, as the only part in the adhoc net, the 
> driver just scans
> around for other adhoc members.
> This happen in mac80211 state 4 and no beacons are sent, as 
> far as I can
> tell. Only probe requests are sent.
> 
> When an other node (N2) shows up in the same adhoc net work, N2 starts
> sending beacons immediately.
> The RT61 catch that and merge that ibss, switch to state 5 
> and all is fine.
> At this time ping works in both directions.
> 
> When removing the second note, leaving the RT61 alone, RT61 
> starts sending
> beacons, still in state 5.

The reason for the above behaviour are timeouts.
- Mac80211 will create an ibss after 20 seconds probing for existing ibss.
- Wpa_supplicant will restart this timer every 5 second ....

Changing the wpa timer will make the rt61 start sending beacons even if no
other STA is available.

I think that wpa_supplicant 0.5.10 addresses this issue, I will check and
come back.

/Lars


  reply	other threads:[~2008-08-17 20:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17  5:36 mac80211 / rt2x00 / rt61 and adhoc status Lars Ericsson
2008-08-17  9:05 ` [Rt2400-devel] " Ivo van Doorn
2008-08-17  9:54   ` Lars Ericsson
2008-08-17  9:58     ` Ivo van Doorn
2008-08-17 10:25       ` Lars Ericsson
2008-08-17 14:02       ` Lars Ericsson
2008-08-17 20:42         ` Lars Ericsson [this message]
2008-08-18 14:34           ` Dan Williams
2008-08-18 19:27             ` Lars Ericsson
2008-08-18 19:35               ` Dan Williams
2008-08-19 17:38                 ` Jouni Malinen

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='059801c900a9$c9eee740$0b3ca8c0@gotws1589' \
    --to=lars_ericsson@telia.com \
    --cc=hostap@lists.shmoo.com \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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