bsd-airtools is a package that provides a complete toolset for
wireless 802.11b auditing. Namely, it currently contains a bsd-based
wep cracking application, called dweputils. It also contains a curses
based ap detection application similar to netstumbler (dstumbler) that
can be used to detect wireless access points and connected nodes, view
signal to noise graphs, and interactively scroll through scanned ap's
and view statistics for each. It also includes a couple other tools to
provide a complete toolset for making use of all 14 of the prism2
debug modes as well as do basic analysis of the hardware-based
link-layer protocols provided by prism2's monitor debug mode.
WWW: http://www.dachb0den.com/projects/bsd-airtools.html
Say hello to the new "net-mgmt" category. There are probably more
ports that belong here than the ones I have identified and moved in
this, first, pass.
Approved in principle by: marcus
Let there be a working dstumbler on -CURRENT!
# uname -a
FreeBSD localhost 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Nov 17 15:08:10 PST
2003 sean@localhost:/usr/obj/usr/src/sys/POSDELLAPTOP i386
# dmesg -a | grep wi0
wi0: <NETGEAR MA401 Wireless PC Card> at port 0x100-0x13f irq 11 function 0 \
config 1 on pccard0
wi0: 802.11 address: 00:30:ab:11:f6:88
wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163 rev.A
wi0: Intersil Firmware: Primary (0.3.0), Station (0.8.3)
wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
# dstumbler wi0 -o
[dstumbler fires up and works beautifully]
Pointed out by: Eugene <eugene3@web.de>
In an attempt to get dstumbler functioning on -CURRENT, I'm committing a few
patches that have been sent in thus far. dstumbler now reports the APs, but
isn't able to monitor them on my Netgear 401, however, others have reported
success so I'm committing them. Please keep me posted if things are or aren't
working. I no longer have a -STABLE box to test these on and haven't tested
this with sam's monitoring mode changes from last night, so, things may be
working correctly now, and/or -STABLE may be broken. In either case, please
let me know.
Submitted by: sam, bms
Correct ports that were abusing the FORBIDDEN variable and replace with
either IGNORE or BROKEN.
Since there seems to be some confusion, for the record:
BROKEN is reserved for ports that don't work. This will prevent
users from installing the port, but please note that
ports marked as BROKEN will still be built by bento
IGNORE is reserved for ports that should not be built for one
reason or another (including bento). Users and bento
will not build ports marked as IGNORE.
FORBIDDEN is reserved for security breakages only!!! Only mark a
port as FORBIDDEN if there is a security issue with the
port at the time.
Reviewed by: kris (portmgr)
