[Prism54-devel] [Bug 40] New: airsnort and kismet both seeing false AP's

[bugzilla-daemon@mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=40

           Summary: airsnort and kismet both seeing false AP's
           Product: prim54
           Version: 1.0.2.2
          Platform: other
        OS/Version: Linux 2.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Device Driver
        AssignedTo: prism54-devel@prism54.org
        ReportedBy: djben@djben.org


Airsnort and Kismet both see garbled and false access point information.
I'm using the 0.2.3c release of Airsnort and I've used the kismet stable 
release 3.0.1 along with several development snapshots (most recently grabbed 
one from 1-17-04). I have used kismet in generic mode along with setting it 
specifically for the prism54 drivers (a feature added in the development branch 
recently).

I've used two prism54 drivers, one from about two weeks ago and one I 
downloaded yesterday (1-19-04). I'm using Suse 9.0 with kernel 2.4.21-144-
default. The card I'm using is a Netgear WG511, and its being used on an old 
dell CPiA366ST laptop. 

Both Kismet and Airsnort both see incorrect access point information, the 
longer they run the more false access point information is seen. They do see 
actual access points, but the number of false information they see ends up 
making them difficult to use as they have at times seen several hundred access 
points when in reality only two may have actually been valid AP's.

If there is any more information I could present which would help out please 
let me know, I'd even go as far as to let a developer remote into the machine 
to snoop around if that would be useful. I can be found as djben in #prism and 
#prism54-devel on freenode at the moment, irc being the preferred method of 
contact over e-mail.

------- Additional Comments From mcgrof@ruslug.rutgers.edu  2004-01-26 05:33 -------
Are the number of access points you see the same when you use iwpriv eth1 scanning ?

------- Additional Comments From Jens.Maurer@gmx.net  2004-01-26 22:29 -------
I get the same problem in "monitor" mode here. "iwlist ... scan" in "managed"
mode shows correct information.

The information in "mointor" mode appears to be completely garbled.  It appears
that frame CRCs are not checked, and those frames should really be thrown away.
 Unfortunately, the card doesn't appear to deliver the frame CRC, at least not
at the end of the frame so that we could check the CRC in our RX path.

Ideas, anyone?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.