Re: More 4965 woes

[Mike Kershaw <dragorn@kismetwireless.net>]

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

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.

> > 3 - Making a monitor mode vap causes a deadlock.  No logs, because the
> >   system locks hard, no caps lock LED, no sysreq.  Monitoring with
> >   tcpdump works for about 3 seconds, then boom.
> 
> Did you create the monitor interface via 'iw' or 'iwconfig mode
> monitor'?

In this test, 'iw'.  I got about 3 seconds of packets from different
channels while trying to associate on 56 (I assume because the card was
doing a scan) and then the system locked.

-m

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

Bus Error at 008BE426 while reading byte from DEADBEEF in User data space


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