From: Johannes Berg <johannes@sipsolutions.net>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-wireless Mailing List <linux-wireless@vger.kernel.org>,
netdev <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: Wed, 13 Nov 2013 19:30:22 +0100 [thread overview]
Message-ID: <1384367422.14578.20.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAMP44s1yJMd+9G5yu988GqafRYnAteN-y-WWDe-rJh_qQpSPkQ@mail.gmail.com> (sfid-20131111_190659_870378_D4E90928)
On Mon, 2013-11-11 at 12:06 -0600, Felipe Contreras wrote:
> > The not receiving part is a bug. I think you're probably receiving
> > beacons once associated though?
>
> Nope. Never.
That's odd, firmware bug? But it's still odd since windows works?
> Moreover, if continuing the association without beacons has a legal a
> problem, that problem would exist for drivers that don't have the
> IEEE80211_HW_NEED_DTIM_BEFORE_ASSOC flag, wouldn't it? How exactly
> would trying to associate with need_beacon break the law, but not if
> !need_beacon?
Well, it's actually somewhat unlikely you'd break the law, although
possible, since eventually you'd get disconnected from the AP anyway?
In any case - your argumentation above isn't true because every device
listens for beacons, and if none are received then it should eventually
disconnect. That should be true even with your hack here.
In any case, I'm not really comfortable connecting to an AP that we
never ever receive beacons from. I can try to investigate why this
doesn't happen on windows and what we should be doing though.
johannes
next prev parent reply other threads:[~2013-11-13 18:30 UTC|newest]
Thread overview: 16+ 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-11 6:41 ` Krishna Chaitanya
2013-11-11 11:01 ` Felipe Contreras
2013-11-11 9:08 ` Johannes Berg
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: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-13 18:30 ` Johannes Berg [this message]
2013-11-14 10: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=1384367422.14578.20.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 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).