From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karl Hiramoto Date: Mon, 06 Apr 2009 11:35:20 +0200 Subject: [ath9k-devel] ath9kl multiple ssid AP In-Reply-To: <1238783295.7153.12.camel@jm-desktop> References: <49D3A893.8080901@hiramoto.org> <1238610612.17750.2.camel@jm-desktop> <49D4CD01.303@hiramoto.org> <1238691478.30212.8.camel@jm-desktop> <49D5CC89.4000104@hiramoto.org> <49D5F4E0.9020003@hiramoto.org> <1238783295.7153.12.camel@jm-desktop> Message-ID: <49D9CCD8.7010607@hiramoto.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Jouni Malinen wrote: > On Fri, 2009-04-03 at 04:37 -0700, Karl Hiramoto wrote: > > >> Another case. two WEP APs essid 1 works but essid2 does not (no >> traffic flow). an iwlist wlan0 on another machine shows the two >> AP's with WEP. Windows shows the WEP APs. >> > > Static WEP keys were not configured for secondary BSSes. This is now > fixed in hostap.git. > > Please also note that this is likely a combination that ath9k does not > currently handle automatically, so you may have to use software crypto > (nohwcrypt=1 module parameter) as a workaround for the time being. This > will eventually be handled automatically, so that the driver can revert > to software encryption/decryption when needed. > > - Jouni > > > Thanks for all the fixes Journi, All of these cases seem to be working now. What other cases is software encryption needed? Before setting nohwcrypt=1, I was receiving the message in wireless-testing/drivers/net/wireless/ath9k/hw.c:2997: "received PCI FATAL interrupt\n"); -- Karl