- 註冊時間
- 2003-3-4
- 線上時間
- 2146 小時
- 閱讀權限
- 200
- 積分
- 1308
- 主題
- 31
- 精華
- 1
- 文章
- 430
TA的每日心情 | 郁悶 2020-5-27 17:14 |
---|
簽到天數: 1 天 連續簽到: 1 天 [LV.1]初來乍到 - 文章
- 430
|
最近在考慮要不要買C760,一方面想買新玩具但又覺得手上的NX-70V還沒有完全發揮威力
剛剛逛到一半發現居然有 wireless lan sniffer 的軟體,還是GPL License,真是殺手級應用
http://www.killefiz.de/zaurus/showdetail.php?app=226
但是只提到support 下面 6種卡,看一看CF的只有第二種的PRISM/2 比較有可能買的到
不知道有沒有人已經用過可以分享一下心得?
SUPPORTED CARD TYPES
1.CISCO
Cards: Aironet 340, Aironet 350
Notes: Cisco cards use an internal firmware channel hopper. kismet_hopper is not needed, and with all current drivers, user-controlled channel hopping is not possible.
'cisco': Linux kernel 2.4.10 through 2.4.19
Capture interface: ethX
Notes: Built-in Linux kernel drivers for the aironet cards (airo and airo_cs). These are, currently, the most reliable drivers to use.
'cisco_cvs': Linux kernel 2.4.20, sourceforge.net CVS driver release
Capture interface: wifiX
Notes: The new drivers use the interface ethX for normal operation and wifiX for raw packet capturing. The interface for Kismet should be set to wifiX. These drivers have a history of locking up under high loads and when entering/leaving rfmon mode.
'cisco_bsd': BSD 'an' drivers
Capture interface: anX
Notes: The 'an' drivers do not report the linktype or packets reliably under most BSD versions. Performance may be varied.
2.PRISM/2
Cards: Prism/2 based PCMCIA, PCI, PLX, Compact Flash, and USB cards by a variety of manufacturers, including Linksys, D-Link, Zoom, Demarctech, Microsoft, and many others.
Notes: Prism/2 users should use kismet_hopper to channel hop. WARNING: The 22mbit cards made by manufacturers such as D-Link (labeled as 650+ among others) are NOT Prism/2 based. They use a proprietary TI chipset, which is currently NOT supported by any drivers in Linux or BSD, and cannot be used. Additionally, recent PCI cards by Linksys and others use a Broadcom chipset instead of Prism/2, which is not supported.
'prism2': Wlan-ng 0.1.14 and higher.
Capture interface: wlanX
Notes: Recent wlan-ng development drivers report PHY (physical layer) packets such as data-ack and request-to-send. Logging of these can be controlled with the 'phylog' option.
'prism2_legacy': Legacy wlan-ng drivers (0.1.13 and earlier)
Capture interface: wlanX
Notes: All users able to do so should upgrade their wlan-ng drivers to a newer version. For those forced to use the older drivers, prism2_legacy uses the linux-netlink-socket capture interface.
'prism2_hostap': hostap
Capture interface: wlanX
Notes: The hostap drivers appear to frequently change the commands used to place them into monitor mode. When in doubt, consult the hostap documentation.
'prism2_bsd': BSD Prism/2 drivers
Notes: OpenBSD 3.2 has Prism/2 drivers which correctly report the link type and packets. Other BSD versions have, at best, mixed results.
3.ORINOCO
Cards: Lucent orinoco based cards such as the WaveLAN series and by some reports Airport.
Notes: Apple Airport cards are reported to also work with these drivers with some effort. kismet_hopper handles channel hopping. Currently, no BSD drivers exist which are capable of doing rfmon mode.
'orinoco': Patched Linux orinoco drivers
Capture interface: ethX
Notes: Drivers must be patched with the rfmon patches at http://airsnort.shmoo.com. Unpatched drivers will not work in rfmon mode.
4.WSP100
Device: WSP100 Remote Sniffer from Network Chemistry
Notes: The WSP100 remote sensor is a SNMP-controlled embedded device that reports packets via a UDP stream. This should work on ANY platform including Win32 (cygwin), Max OS X, Linux, BSD, and anywhere else you can get Kismet to compile. kismet_hopper will configure the wsp100 firmware for internal channel hopping.
'wsp100': Kismet UDP handler
Capture interface: host:port
Notes: The capture interface specifies the address of the wsp100 unit and the port to send the UDP packet stream to.
5.WTAPFILE
Notes: The wtapfile replay ability is primarily useful for debugging, however it can also be used to recreate csv/xml/etc files from a saved dump.
'wtapfile': Kismet wtapfile handler
Capture interface: file
Notes: The capture interface specifies the path to the dump file. Dumps can be in any format wtaplib understands, which includes files created by Kismet, Ethereal, TCPdump, and others. Files can be gzip compressed. File replaying can be slowed down using the '-M' command line option. -M100 is typical.
6.AR5K
Notes: 802.11a doesn't include the channel in the beacon packets. Workarounds will be put into place for this in the future.
'ar5k': vt_ar5k Linux 802.11a drivers
Capture interface: wlanX
Notes: The vt_ar5k drivers require the Linux wireless-tools version 25 or higher. Older versions will not be able to put the cards into monitor mode. |
|