prism2 card (was: Re: Bat digest, Vol 1 #128 - 2 msgs)

Yes, a D-Link DWL-650:
wi0 at pcmcia0 function 0 "D, Link DWL-650 11Mbps WLAN Card, Version 01.02" port 0xa000/64
wi0: PRISM 2.5 ISL3873, Firmware 1.0.7 (primary), 1.3.5 (station), address 00:05:XX:XX:XX:XX
(from dmesg as detailed in my original post)

I haven't had a chance to get the current version by CVS
yet (was the server down in the last day or so?)
or play around with prism2ctl.

Ciao
 --Louis  <[email protected]>

On Thu, 25 Jul 2002 [email protected] wrote:

> Send Bat mailing list submissions to
> 	[email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.dachb0den.com/mailman/listinfo/bat
> or, via email, send a message with subject or body 'help' to
> 	[email protected]
>
> You can reach the person managing the list at
> 	[email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Bat digest..."
>
>
> Today's Topics:
>
>    1. Re: Bat digest, Vol 1 #126 - 2 msgs (Tom Hensel)
>    2. weakksa.c and wi_dat_len (Mathieu Perrin)
>
> --__--__--
>
> Message: 1
> Date: Tue, 23 Jul 2002 10:58:50 +0000
> From: Tom Hensel <[email protected]>
> To: [email protected]
> Subject: [BAT] Re: Bat digest, Vol 1 #126 - 2 msgs
> Reply-To: [email protected]
>
> hi,
>
> >> 2) I can't seem to detect a simple WLAN consisting of two
> >>PCs in Ad-Hoc mode, with 40-bit WEP. The dstumbler screen
> >>stays blank. Yes, I understand that dstumbler relies on AP
> >>broadcasts and Station discovery requests, but should it not
> >>see some sort of activity?  (tcpdump works)
>
> you are using a prism2-based card, aren't you?
>
> bye,
> TOM
>
>
> --__--__--
>
> Message: 2
> Date: Thu, 25 Jul 2002 14:14:01 +0200
> From: Mathieu Perrin <[email protected]>
> To: [email protected]
> Subject: [BAT] weakksa.c and wi_dat_len
> Reply-To: [email protected]
>
> Hi,
>
> -----------
> Platform where dwepcrack is run = FreeBSD 4.6
> bsd-airtools v0.2
> -----------
>
> Our problem was that we couldn't find the wepkey, even when we had 7 or
> 8 millions packets ( using FMS attack ).
>
> While trying to find why we always have too few weak packets, we found
> that  dwepcrack used only 3000 or 4000 packets ( from a dumpfile of
> 400 000 packets ), and found only 200 weaks IVS.
>
> So we investigated into weakksa.c, and found an average value of
> wi_h->wi_dat_len of about 50000, while you reject all packets with
> wi_dat_len greater than 2304 ( MAX_PKT_SIZE ).
>
> We are very surprised by this value of 50000. We collected traffic from
> a ftp transfer between an AP and a FreeBSD client ( prism2 ) with a
> tcpdump running on a linux ( cisco card ).
>
> So here are our thougths :
>
> 	- incorrect casting of the output of pcap_next() in struct wi_h
> 	  ( wi_h = (struct wi_rx_frame *)pkt; )
>
> 	- maybe our dumps are flawed ( althought ethereal can read them
> 	  )
>
> 	- maybe we are totally nuts.... :)
>
>
> Thanks for your help,
>
>
> 			Mathieu
>
>
> --
> 		BOFH excuse: temporary routing anomoly
>
>
>
>
>
>
>
>
>
> --__--__--
>
> _______________________________________________
> Bat mailing list
> [email protected]
> http://lists.dachb0den.com/mailman/listinfo/bat
>
>
> End of Bat Digest
>