From: Bob Copeland <me@bobcopeland.com>
To: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: "devel@lists.open80211s.org" <devel@lists.open80211s.org>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] mac80211: mesh_plink: handle confirm frames with new plid
Date: Thu, 3 Jul 2014 11:10:34 -0400 [thread overview]
Message-ID: <20140703151034.GA10238@localhost> (raw)
In-Reply-To: <20140703142837.GA11380@localhost>
On Thu, Jul 03, 2014 at 10:28:37AM -0400, Bob Copeland wrote:
> > What is the consequence if we don't handle this case? Is the peer
> > going to do the re-auth again?
> >
> > Regards,
> > Chun-Yeow
>
> It shouldn't be a big problem -- looking at 802.11-2012 figure 13-2:
Actually, thinking about it more, a worse case is if B reaches
ESTAB and then A reboots. Now, A sends an Open, gets back
a Confirm that A will ignore (due to no plid). A will still
timeout and send a Close frame to restart everything, but we
would have to wait quite a while to re-establish the peering.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2014-07-03 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1403987726-17576-1-git-send-email-me@bobcopeland.com>
2014-06-28 20:54 ` [PATCH 1/2] mac80211: mesh_plink: handle confirm frames with new plid Bob Copeland
2014-07-03 12:36 ` Yeoh Chun-Yeow
2014-07-03 14:28 ` Bob Copeland
2014-07-03 15:10 ` Bob Copeland [this message]
2014-07-04 3:12 ` Yeoh Chun-Yeow
2014-07-24 10:58 ` Johannes Berg
[not found] ` <1403987726-17576-2-git-send-email-me@bobcopeland.com>
2014-06-28 20:54 ` [PATCH 2/2] mac80211: mesh_plink: use get_unaligned_le16 instead of memcpy Bob Copeland
2014-07-24 10:59 ` Johannes Berg
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=20140703151034.GA10238@localhost \
--to=me@bobcopeland.com \
--cc=devel@lists.open80211s.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=yeohchunyeow@gmail.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;
as well as URLs for NNTP newsgroup(s).