| Posted by: | sachax |
|---|
| Subject: | kismet->wi-scan converters posted here |
|---|
| Date: | 21:31:35 05/08/2002 |
|---|
ermmm, uhhh...jokes on me... Next time: VALIDATE ALL YOUR F&*$ng data fields...Ohh I had c0nv3r9s program working for the wardrive, but overlooked two little details:
The way he parses the fields by counting semicolons had my longitude field putting up either signal strength or noise....OOOOF
lower case ad-hocs were not translated to the appropriate number by the scoring script (Pete's)....OOOOF
sforce: 0
damn damn damn..
Ohh well, we had a freaking blast anyway... Got to put some faces with some names. Thanks for explaining the Sat setup blackwave...
Overall we found 200 wireless chatting systems, and once I ripped out the ones flagged "data" which were most of the netstumblers in the competition, we found 151 WAPS, with over 40 in a default config. I also expected to get a huge bang for heading up to Summerlin, among all the pricey homes were many, many Linksys default WAPS.
I hope to see the raw data which was used to judge, Would like to see how we fared, knowing the fixes I know now.
Also would like to see if anybody tried some creative methods of using the kismet data fields of the other stumblers as access points in their compilations...I have some MAC's that I'm lookin forward to checking.
Great Time!
> I use the kismet-devel tree, and found c0nv3r9's program was choking on some issues with added semicolons in the gps file.
>
> I edited this line:
>
> if ( fieldCounter == 29 ) to 31 and recompiled...
>
> Works fine, did notice that some of the Yes/No's didn't convert for WEP, but overall now I can use my kismet data for the wardrive...
>
> > Currently:
> > - c0nv3r9's cpp program
> > - Medic's VB script
> > http://www.securitytribe.com/wardrive.html
> >
> > Also Shipley's WarDriving Judging script, and mailing list.
> >
> > -=BW=-
Reply to this message
