From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] libertas: automatically re-associate
Date: Thu, 11 Oct 2007 00:00:44 -0400 [thread overview]
Message-ID: <1192075245.31110.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20071010165921.GG5962@tuxdriver.com>
On Wed, 2007-10-10 at 12:59 -0400, John W. Linville wrote:
> On Wed, Oct 10, 2007 at 10:58:58AM -0400, Dan Williams wrote:
>
> > I won't throw a hissy fit over the reassociation patch as long as it
> > only tries this in open & WEP situations where a supplicant is not
> > necessary. That means you cannot simply requeue an association in
> > libertas_mac_event_disconnected(), but you should check the association
> > request and not requeue if:
> >
> > 1) the assoc request's mode is ad-hoc (is there a point to retrying
> > assoc in adhoc?)
>
> I'm not sure I see why ad-hoc is a special case?
A STA can't ever get disassociation management frames in an IBSS, right?
I don't believe the firmware will ever disconnect you once you've
started an IBSS, but there may be a difference between the start-adhoc
and join-adhoc commands that get sent to firmware. However, it's not
like loss of becaons in IBSS mode will cause a disconnection, because it
just looks like the network split and you are the only member of it, and
then your STA takes up beaconing responsibility by itself until the
world ends. AFAIK.
Dan
next prev parent reply other threads:[~2007-10-11 4:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 12:04 [PATCH] libertas: automatically re-associate Holger Schurig
2007-10-09 14:19 ` Dan Williams
2007-10-09 15:13 ` Holger Schurig
2007-10-09 15:37 ` Dan Williams
2007-10-10 7:43 ` Holger Schurig
2007-10-10 14:58 ` Dan Williams
2007-10-10 16:59 ` John W. Linville
2007-10-11 4:00 ` Dan Williams [this message]
2007-10-10 19:00 ` Holger Schurig
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=1192075245.31110.9.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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