Re: More 4965 woes

[Mike Kershaw <dragorn@kismetwireless.net>]

[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]

On Wed, Jun 18, 2008 at 11:41:10AM -0400, Mike Kershaw wrote:
> On Wed, Jun 18, 2008 at 05:28:14PM +0800, Zhu Yi wrote:
> > On Tue, 2008-06-17 at 09:24 -0400, Mike Kershaw wrote:
> > > 1 - Inability to associate to a network on 5ghz.  Same AP on 2.4ghz
> > >   works fine, scanning shows the AP fine.  Sniffing with an additional
> > >   card shows no frames at all being sent by the 4965. AP is on a
> > > channel
> > >   the 4965 should be able to talk to according to iwlist channel (logs
> > > attached)
> > 
> > >From the log, you are trying to use channel 56 which is under radar
> > detection. The card must hear from the AP first in order to send. Can
> > you try 36? 
> 
> Must hear from the AP?  Like, beacons?  If beacons aren't enough, how is
> something ever supposed to associate?
> 
> The AP is detected normally via scanning (wpa_supplicant 'scan' and
> iwlist scan) so the card is seeing beacons fine.
> 
> I'll reboot into the git kernel later today and redo the test on another
> channel.

On channel 36 things appear to work (well, as much as they do otherwise,
packet hanging still makes the device unusable).  I'm still confused as
to why the card can report it works on that channel, scan that channel,
see beacons, but then refuse to transmit.

-m

-- 
Mike Kershaw/Dragorn <dragorn@kismetwireless.net>
GPG Fingerprint: 3546 89DF 3C9D ED80 3381  A661 D7B2 8822 738B BDB1

Catapultam habeo. Nisi pecuniam omnem mihi dabis, ad caput tuum saxum 
immane mittam. 

I have a catapult. Give me all your money, or I will fling an enormous 
rock at your head

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]