From owner-freebsd-mobile Tue Feb 25 10:50:15 2003 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61E4D37B401 for ; Tue, 25 Feb 2003 10:50:13 -0800 (PST) Received: from hindenburg.eboai.org (hindenburg.eboai.org [206.183.134.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 918EA43F93 for ; Tue, 25 Feb 2003 10:50:10 -0800 (PST) (envelope-from chip@chocobo.cx) Received: by hindenburg.eboai.org (Postfix, from userid 1000) id 9911F5E3E0; Tue, 25 Feb 2003 13:50:09 -0500 (EST) Date: Tue, 25 Feb 2003 13:50:09 -0500 From: Chip Marshall To: freebsd-mobile@FreeBSD.org Subject: Kismet and FreeBSD Message-ID: <20030225185009.GA21320@chocobo.cx> Reply-To: chip@chocobo.cx Mail-Followup-To: freebsd-mobile@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw" Content-Disposition: inline X-URL: http://www.chocobo.cx/chip/ X-OS: FreeBSD 4.6-RELEASE-p2 i386 up 102 days User-Agent: Mutt/1.5.1i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This topic seems to come up from time to time in #kismet on freenode.net, without really getting anywhere. Basically, there are a number of people who would like to use Kismet, a wireless network sniffer (www.kismetwireless.net), under FreeBSD. Currently it works with the wireless drivers of Linux and OpenBSD. The Kismet code compiles and runs under FreeBSD, but when actually trying to gather data, it comes up with a lot of junk from FreeBSD's wi driver. dragorn, the author of Kismet, has this to say on the subject: the problem is that the fbsd drivers a) don't report the right link type and b) don't seem to report packets consistently when in rfmon I can find all the bits of the beacon frames, I don't think i had a dump with many other management frames in it, but the data frames appear completely hosed if they can either fix that, or explain that all the data is in there and I'm just not looking in the right place I'll change kismet if needs be to accomodate their drivers, but as they stand now I can't identify the fragments of the packe= t at all Theres a header on the management frames, that's OK, I can ignore that, and theres a hunk of crap in the middle of the frame= for no good reason, but I can work around that, too but the data frames are just all shot to hell Is there anyone out there who is fairly familiar with the wi driver and willing to hop on IRC to try and get this worked out? --=20 Chip Marshall http://www.chocobo.cx/chip/ GCM/CS d+(-) s+:++ a21>? C++ UB++++$ P+++$ L- E--- W++ N@ o K- w O M+ V-- PS+ PE Y+ PGP++ t+@ R@ tv@ b++@ DI++++ D+(-) G++ e>++ h>++ r-- y? --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+W7rh8vyTVl6qbdQRAoYPAJkBU+e0OL44FHXSmkbyj79KXW97dwCfdmnM TZ/jBZRNeH1G3h1Bw/1vLaI= =zmcB -----END PGP SIGNATURE----- --wac7ysb48OaltWcw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message