All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Jouni Malinen <jouni@qca.qualcomm.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Regression caused by commit df88129
Date: Mon, 18 Feb 2013 15:01:29 +0100	[thread overview]
Message-ID: <1361196089.8555.12.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <51207925.5040702@lwfinger.net> (sfid-20130217_073124_813060_AAE5AFC8)

On Sun, 2013-02-17 at 00:31 -0600, Larry Finger wrote:
> Jouni and Johannes,
> 
> A recent pull of the wireless-testing tree caused my wireless to break. The 
> wireless devices can authenticate and associate as follows:
> 
> wlan0: authenticate with c0:3f:0e:be:2b:44
> wlan0: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded
> wlan0: send auth to c0:3f:0e:be:2b:44 (try 1/3)
> wlan0: authenticated
> wlan0: associate with c0:3f:0e:be:2b:44 (try 1/3)
> wlan0: RX AssocResp from c0:3f:0e:be:2b:44 (capab=0x411 status=0 aid=3)
> wlan0: associated
> IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> wlan0: dropped frame to c0:3f:0e:be:2b:44 (unauthorized port)
> b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 
> c0:3f:0e:be:2b:44
> b43-phy0 debug: Using hardware based encryption for keyidx: 1, mac: 
> ff:ff:ff:ff:ff:ff
> wlan0: dropped frame to c0:3f:0e:be:2b:44 (unauthorized port)
> wlan0: dropped frame to c0:3f:0e:be:2b:44 (unauthorized port)

Yeah, it's obvious that this would happen for drivers not supporting
TDLS -- will send a patch.

johannes


  parent reply	other threads:[~2013-02-18 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17  6:31 Regression caused by commit df88129 Larry Finger
2013-02-17  8:32 ` Malinen, Jouni
2013-02-17 14:41 ` Malinen, Jouni
2013-02-17 21:21   ` Larry Finger
2013-02-18 14:01 ` Johannes Berg [this message]
2013-02-18 14:02 ` [PATCH] cfg80211: fix station change if TDLS isn't supported Johannes Berg
2013-02-18 17:24   ` Larry Finger
2013-02-18 17:25     ` 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=1361196089.8555.12.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@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.