From: Johannes Berg <johannes@sipsolutions.net>
To: reinette chatre <reinette.chatre@intel.com>
Cc: Ben Greear <greearb@candelatech.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: use beacons for connection monitoring
Date: Thu, 30 Jul 2009 21:47:05 +0200 [thread overview]
Message-ID: <1248983225.10971.5.camel@johannes.local> (raw)
In-Reply-To: <1248975923.1216.1074.camel@rc-desk>
[-- Attachment #1: Type: text/plain, Size: 3310 bytes --]
On Thu, 2009-07-30 at 10:45 -0700, reinette chatre wrote:
> I captured the exchange when this problem occurs using a third system.
> The card does indeed try several times to send a probe request and they
> are making it out over the air. The AP never responds.
>
> Is there perhaps anything in this exchange that can help us understand
> what is going on?
>
> No. Time Source Destination Protocol Info
> 163883 401.891153 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=980, FN=0, Flags=........, SSID="XXX"
> 163885 401.891482 00:14:f2:XX:XX:XX 00:16:ea:XX:XX:XX IEEE 802.11 Probe Response, SN=3557, FN=0, Flags=........, BI=100, SSID="XXX"
It's responding here,
> 165523 404.884405 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=981, FN=0, Flags=........, SSID="XXX"
> 165525 404.885265 00:14:f2:XX:XX:XX 00:16:ea:XX:XX:XX IEEE 802.11 Probe Response, SN=3827, FN=0, Flags=....R..., BI=100, SSID="XXX"
and here,
> 166981 407.884161 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=982, FN=0, Flags=........, SSID="XXX"
> 166983 407.884555 00:14:f2:XX:XX:XX 00:16:ea:XX:XX:XX IEEE 802.11 Probe Response, SN=4034, FN=0, Flags=........, BI=100, SSID="XXX"
and here,
> 168133 410.884167 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=........, SSID="XXX"
> 168134 410.884430 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
> 168135 410.884643 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
> 168136 410.884904 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
> 168137 410.885073 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
> 168138 410.885330 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
> 168139 410.885580 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
> 168140 410.885769 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
> 168141 410.886618 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
> 168142 410.887087 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
> 168143 410.887308 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
> 168144 410.887532 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Probe Request, SN=983, FN=0, Flags=....R..., SSID="XXX"
but then it stops -- try to send that frame 12 times in quick
succession.
> 168191 411.084889 00:16:ea:XX:XX:XX 00:14:f2:XX:XX:XX IEEE 802.11 Deauthentication, SN=984, FN=0, Flags=........
And then give up. Oddly, that frame is not retried?! I would expect that
to be retried too if the AP has gone south!?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-07-30 19:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 21:32 [PATCH] mac80211: use beacons for connection monitoring Reinette Chatre
2009-07-29 21:39 ` Ben Greear
2009-07-30 10:30 ` Johannes Berg
2009-07-30 14:41 ` Ben Greear
2009-07-30 17:45 ` reinette chatre
2009-07-30 19:47 ` Johannes Berg [this message]
2009-07-29 21:45 ` Johannes Berg
2009-07-29 21:50 ` reinette chatre
2009-07-30 5:24 ` Maxim Levitsky
2009-07-29 22:10 ` Ben Greear
2009-07-30 10:28 ` Johannes Berg
2009-07-30 2:39 ` Marcel Holtmann
2009-07-30 9:36 ` Helmut Schaa
2009-07-30 9:54 ` Johannes Berg
2009-07-31 7:08 ` Maxim Levitsky
2009-07-31 7:43 ` Johannes Berg
2009-07-31 7:58 ` Johannes Berg
2009-07-31 8:04 ` Maxim Levitsky
2009-07-31 9:41 ` Marcel Holtmann
2009-07-31 13:19 ` Maxim Levitsky
2009-07-31 13:39 ` Johannes Berg
2009-07-31 13:56 ` Maxim Levitsky
2009-07-31 14:06 ` 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=1248983225.10971.5.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.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).