From: Johannes Berg <johannes@sipsolutions.net>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v2] mac80211: add assoc beacon timeout logic
Date: Mon, 11 Nov 2013 10:08:52 +0100 [thread overview]
Message-ID: <1384160932.14334.6.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1384119945-31213-1-git-send-email-felipe.contreras@gmail.com> (sfid-20131110_225237_639267_0727F79C)
On Sun, 2013-11-10 at 15:45 -0600, Felipe Contreras wrote:
> We don't want to be waiting forever for a beacon that will never come,
> just continue the association.
This makes no sense, IMO.
If there really are no beacons at all, then nothing can work with the AP
-- things like HT, regulatory/radar, powersave, multiple virtual
interfaces and many others require beacons.
If the AP is sending beacons but the device isn't receiving them, then
it's a driver bug and mac80211 shouldn't work around it.
johannes
next prev parent reply other threads:[~2013-11-11 9:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 21:45 [PATCH v2] mac80211: add assoc beacon timeout logic Felipe Contreras
2013-11-10 21:45 ` Felipe Contreras
2013-11-11 6:41 ` Krishna Chaitanya
2013-11-11 6:41 ` Krishna Chaitanya
2013-11-11 11:01 ` Felipe Contreras
2013-11-11 11:01 ` Felipe Contreras
2013-11-11 9:08 ` Johannes Berg [this message]
2013-11-11 10:59 ` Felipe Contreras
2013-11-11 15:43 ` Johannes Berg
2013-11-11 16:23 ` Felipe Contreras
2013-11-11 16:23 ` Felipe Contreras
2013-11-11 16:41 ` Johannes Berg
2013-11-11 16:53 ` Felipe Contreras
2013-11-11 16:56 ` Felipe Contreras
2013-11-11 17:01 ` Johannes Berg
2013-11-11 17:00 ` Johannes Berg
2013-11-11 18:06 ` Felipe Contreras
2013-11-11 18:06 ` Felipe Contreras
2013-11-13 18:30 ` Johannes Berg
2013-11-14 10:44 ` Felipe Contreras
2013-11-27 6:44 ` Felipe Contreras
2013-11-27 6:44 ` Felipe Contreras
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=1384160932.14334.6.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=felipe.contreras@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.