From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jouni Malinen <j@w1.fi>,
linux-wireless@vger.kernel.org, "Guy,
Wey-Yi" <wey-yi.w.guy@intel.com>
Subject: Re: Marshaling issues w/ compat-wireless-2010-08-19
Date: Sat, 04 Sep 2010 15:45:36 -0700 [thread overview]
Message-ID: <4C82CC10.7060903@redfish-solutions.com> (raw)
In-Reply-To: <1283589824.3746.1.camel@jlt3.sipsolutions.net>
On 9/4/10 1:43 AM, Johannes Berg wrote:
> On Fri, 2010-09-03 at 14:52 -0700, Philip Prindeville wrote:
>
>> Just following up: I isolated the problem.
>>
>> I had taken the sample hostapd.conf that comes with hostapd-0.7.2 and copied it into /etc/.
>>
>> Then I enabled the following commented out fields:
>>
>> bridge=br0
>> driver=nl80211
>> ssid=my-hp-test
>> country_code=US
>> hw_mode=g
>> channel=10
>> wep_default_key=0
>> wep_key0=123456789a
>> ieee80211n=1
>>
>> but what broke it was:
>>
>> wep_key_len_broadcast=5
>> wep_key_len_unicast=5
>> wep_rekey_period=300
>>
>> if I turned off those last 3, things work again.
> Hah. I don't even know what that does. What were you trying to achieve?
> Aren't those related to dynamic WEP, but you configured static WEP?
>
> johannes
>
I was trying to test the rekeying feature, where new keys are multicast when the group membership changes.
next prev parent reply other threads:[~2010-09-04 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 1:18 Marshaling issues w/ compat-wireless-2010-08-19 Philip Prindeville
2010-08-25 8:11 ` Johannes Berg
2010-08-25 8:20 ` Johannes Berg
2010-08-25 17:23 ` Philip Prindeville
2010-08-25 18:42 ` Philip Prindeville
2010-08-25 18:44 ` Johannes Berg
2010-08-28 17:12 ` Jouni Malinen
2010-08-28 17:19 ` Philip Prindeville
2010-08-31 1:07 ` Philip Prindeville
2010-09-03 21:52 ` Philip Prindeville
2010-09-04 8:43 ` Johannes Berg
2010-09-04 22:45 ` Philip Prindeville [this message]
2010-09-14 13:04 ` 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=4C82CC10.7060903@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@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).