Guten Abend zusammen,
in meinem X30 ist eine Aironet Cisco 11Mbit Karte. leider scheint da seit dem 2.4er Kernel keine tolle Treiberentwicklung mehr stattzufinden oder um es mit Worten uas dem Kismet-Forum zu sagen "Cisco aironet drivers are borked" :(
Nun habe ich das Teil mal aufgemacht und gesehen, dass es sich um eine stink-normale MiniPCI Karte mit 2 handelsüblichen Steckern für die beiden Antennen handelt. Meine Theorie: Die müsste ich ja eigenltich ohne weiteres einfach austauschen können - stimmt ihr mir da zu?
Wenn ja stellt sich mir die Frage: WELCHE? Mein erster Gedanke war "atheros" - damit ist ja auch der ebay markt überschwemmt mit atheros karten. gibt es da eigentlich unterschiede? die preise reichen ja von 20 - 70 €. Ich bin allerdings etwas vorsichtig, da ich von mehreren linux-Usern aus meinem Semester schon über reichlich Problemen mit den Treibern gehört habe. Die MadWifi scheinen ziemliche "seriestreuung" zu sein, oder sind die nur unfähig? Wie ist der Stand? Oder sollte ich lieber eine Prism2 Karte in Augenschein nehmen? Wo liegen die genauen Leistungsunterschiede? Packet Injection, etc?
Würde mich über Antworten freuen.
Antworten die mir vielleicht helfen miene aironet karte mit kismet ans laufen zu bekommen, sind ja natürlich auch gerne gehört ;)
danke euch!
Rain_maker
21.10.06, 19:07
Wenn es wirklich eine mini-PCI ist, dann kann ich aus eigener Erfahrung ipw2200/2100-Karten empfehlen.
Wie gut diese allerdings mit einem 2.4er harmonieren ist mir nicht bekannt, ab 2.6.8 laufen sie aber laut HP:
http://ipw2100.sourceforge.net/#kernel
Requirements
In order to use the IPW2100 driver you will need the following:
Linux (of course) with a 2.6.8+* kernel [link]. See README.ipw2100 for information on specific options required to be enabled in the kernel.
Wireless Extensions (v17) and Tools (v28) [link]
The IPW2100 driver. You can obtain the latest development snapshot below.
The IPW2100 binary firmware image. The firmware can be obtained here.
For instructions on how to build and use the driver, please see the INSTALL document.
Es gibt wohl auch Patches für den 2.4er:
Useful Links
We have put up a development mailing list to help in development.
You can frequently find people on IRC channel #ipw2100 on irc.freenode.org.
The following are links to projects, archives, and other sites that may be of use to IPW2x00 users:
Giuseppe's 2.4 backport patches: ipw2100 2.4 backpatch
Wie gut das funktioniert, keine Ahnung, vielleicht solltest Du allgemein über ein Upgrade Deiner Distribution nachdenken, es gibt ja auch schlanke Distros mit 2.6er Kerneln.
Ob der Austausch wirklich so problemlos funktioniert, kann ich Dir allerdings auch nicht sagen.
Greetz,
RM
hi und danke für die antwort ...
ok ich scheine mich undeutlich ausgedürckt zu haben. ich nutze natürlich den 2.6er kernel (aktuell 2.6.18). die letzten halbwegs (für kismet) funktionierenden treiber sind aber eben für nen 2.4er kernel und ich möchte eigentlich schon gerne den 2,6er weiternutzen ;)
Rain_maker
21.10.06, 19:26
hi und danke für die antwort ...
ok ich scheine mich undeutlich ausgedürckt zu haben.
Nope, das Mißverständnis lag auf meiner Seite
in meinem X30 ist eine Aironet Cisco 11Mbit Karte. leider scheint da seit dem 2.4er Kernel keine tolle Treiberentwicklung mehr stattzufinden
Das hab ich falsch interpretiert.
Damit kann ich meine Empfehlung nun uneingeschränkt geben und allgemein auf ipw-Karten ausdehnen (2915 und 3945 scheinen auch ganz gut zu laufen).
Ich besitze eine ipw2200 und bin sehr zufrieden, wobei ich sie allerdings nicht mit kismet o.ä. verwende.
Greetz,
RM
danke für eine dempfehlung - werde mich mal auf ebay etc. umschauen. würde mich aber noch freuen, wenn jemand noch nen statement zu atheros karten abliefern könnte. grade die funktionalität mit kismet ist mir recht wichtig.
Known supported cards: Atmel_USB, ACX100, ADMTek, Atheros, Cisco, Prism2, Orinoco, WSP100, Drone, wtapfile, pcapfile, wrt54g, ipw2100, rt2400, rt2500, rt8180, ipw2200, ipw2915, ipw3945, Broadcom 43xx
A capture source in Kismet is anything which provides packets to the Kismet
engine. Capture sources define the underlying engine needed to capture
data from the interface, how to change channel, and how to enter rfmon
mode. It is necessary to tell Kismet what specific type of card you use
because different drivers often use different methods to report information
and enter monitor mode.
Source type Cards OS Driver
--------------- ------------------- ----------- -------------------------
acx100 TI ACX100 Linux ACX100
http://acx100.sourceforge.net/
Capture interface: 'ethX'
ACX100 drivers handle the 22mbit cards branded by D-Link
and others.
admtek ADMTek Linux ADMTek
http://www.latinsud.com/adm8211/ (Patches)
http://aluminum.sourmilk.net/adm8211/ (GPL driver)
ADMTek drivers used in many consumer 802.11b cards. With
the patches above, quasi-rfmon is possible - these cards
appear to be almost entirely software controlled and
always in a rfmon-like state. This card WILL BROADCAST
while in rfmon, rendering the sniffer visible.
The fully GPL drivers are supported, in addition to the
hacks to the non-free drivers.
atmel_usb Atmel-USB Linux Berlios-Atmel
http://at76c503a.berlios.de/
Capture interface: 'wlanX'
These drivers work ONLY on USB cards (Sorry, no PCMCIA
support). Monitor mode support is limited and "faked"
by bypassing part of the firmware and parsing packets
directly, and is likely to not report all of the
frames.
This card MAY BROADCAST while in rfmon, rendering the
sniffer visible.
It appears that this card may be only formatting the
beacons as an 802.11 stream, which means you likely
will not see data frames, rendering most IDS functions,
IP discovery, and data logging unavailable.
bcm43xx Broadcom Linux Berlios-BCM43XX
http://bcm43xx.berlios.de
Capture interface: 'ethX'
*Very experimental* drivers with *experimental* Kismet
support. These reverse-engineered drivers support a
range of Broadcom based wireless cards. At the time
of this writing, they support ONLY monitor mode, normal
mode is not functional.
These drivers are in a state of high development, and
support is only added because of demand. If it doesn't
work, I wouldn't be too surprised.
cisco Aironet 340,350 Linux Kernel 2.4.10 - 2.4.19
Capture interface: 'ethX'
Standard Cisco cards in Linux. Works only with
the Linux kernel drivers, not the drivers found in
pcmcia-cs.
The drivers found on the cisco.com site can be patched
with the files from the Kismet download site to add
monitor mode with channel control, HOWEVER these drivers
are extremely buggy for normal use and work only with
the 2.4 kernel tree.
The cisco drivers currently do not enter rfmon mode
correctly, so channel control is not available. The
firmware will hop to whatever channel it feels like
hopping to, when it feels like hopping.
cisco_wifix Aironet 340,350 Linux Kernel 2.4.20+, CVS
http://sourceforge.net/projects/airo-linux/
Capture interface: 'ethX:wifiX'
Kernel 2.4.20+ and CVS drivers use ethX for normal mode
and wifiX for monitor mode. Kismet needs to know both
devices, which may not necessarily be the same number,
for example 'eth1:wifi0'.
Linux kernel 2.4.20 and 2.4.21 have highly unstable cisco
drivers and should be avoided.
The cisco drivers currently do not enter rfmon mode
correctly, so channel control is not available. The
firmware will hop to whatever channel it feels like
hopping to, when it feels like hopping.
cisco_openbsd Aironet 340,350 OpenBSD Kernel
Capture interface: 'anX'
OpenBSD cisco drivers are not fully supported currently,
but may become so. Packet capture probably will not
work correctly.
For current OpenBSD releases you should try the
radiotap_bsd_b capture source, NOT this one.
hostap Prism/2 Linux HostAP 0.4
http://hostap.epitest.fi/
Capture interface: 'wlanX'
HostAP drivers drive the Prism/2 chipset in access point
mode, but also can drive the cards in client and monitor
modes. The HostAP drivers seem to change how they go
into monitor mode fairly often, but this source should
manage to get them going.
ipw2100 Intel/Centrino Linux ipw2100-0.44+
http://ipw2100.sourceforge.net/
Capture interface: 'ethX'
The Linux IPW2100/Centrino drivers for 802.11b cards
now support rfmon, so here's support for them. They act
more or less like any other wireless interface would.
ipw2200 Intel/Centrino Linux ipw2200-1.0.4+
http://ipw2200.sourceforge.net/
Capture interface: 'ethX'
The Linux IPW2200/Centrino drivers for 802.11bg cards
support rfmon as of 1.0.4 and firmware 2.3.
Signal level reporting requires radiotap be turned on
in the makefile while compiling the driver. Noise levels
are not reported.
ipw2915 Intel/Centrino Linux ipw2200-1.0.4+
Capture interface: 'ethX'
http://ipw2200.sourceforge.net/
The Linux IPW2200/Centrino drivers for 802.11bga cards
support rfmon as of 1.0.4 and firmware 2.3.
This is the same as ipw2200 but defaults to scanning the
802.11a channel range in addition to 802.11b/g.
Signal level reporting requires radiotap be turned on
in the makefile while compiling the driver. Noise levels
are not reported.
ipw3945 Intel/Centrino Linux ipw3945
Capture interface: 'ethX'
http://ipw3945.sourceforge.net/
The Linux IPW3945/Centrino drivers for Intel Core
802.11bga cards.
ipwlivetap Intel/Centrino Linux ipw2200/3945
Capture interface: 'ethX'
http://ipw2200.sourceforge.net/
http://ipw3945.sourceforge.net/
The ipw3945 and patched ipw2200 drivers support a
special mode which allows monitor-mode style sniffing
while remaining associated. Channel hopping is not
possible, as the card is still associated to a
specific AP, but single-channel IDS and sniffing can
be accomplished. See the ipw driver mailing list
archives for information about patching your drivers.
kismet_drone n/a Any n/a
Capture interface: 'dronehost:port'
The remote drone capture source connects to a Kismet
drone and proceses the packets. Refer to the Remote
Drone section of the README for more details about how
to set up a drone.
madwifi_a Atheros Linux madwifi
http://sourceforge.net/projects/madwifi/
Capture interface: 'athX'
Capture interface: 'wifiX' (Madwifi-NG)
Madwifi drivers in 802.11a-only mode.
When using madwifi-ng, be sure all non-monitor VAPs have
been removed, otherwise madwifi will not properly report
most traffic.
madwifi_b Atheros Linux madwifi
http://sourceforge.net/projects/madwifi/
Capture interface: 'athX'
Capture interface: 'wifiX' (Madwifi-NG)
Madwifi drivers in 802.11b-only mode.
When using madwifi-ng, be sure all non-monitor VAPs have
been removed, otherwise madwifi will not properly report
most traffic.
madwifi_g Atheros Linux madwifi
http://sourceforge.net/projects/madwifi/
Capture interface: 'athX'
Capture interface: 'wifiX' (Madwifi-NG)
Madwifi drivers in 802.11g-only mode. This will,
obviously, also see 11b networks.
When using madwifi-ng, be sure all non-monitor VAPs have
been removed, otherwise madwifi will not properly report
most traffic.
madwifi_ab Atheros Linux madwifi
http://sourceforge.net/projects/madwifi/
Capture interface: 'athX'
Capture interface: 'wifiX' (Madwifi-NG)
Madwifi drivers in 802.11a and 802.11b combo mode. This
will seamlessly switch between bands during channel
hopping.
When using madwifi-ng, be sure all non-monitor VAPs have
been removed, otherwise madwifi will not properly report
most traffic.
madwifi_ag Atheros Linux madwifi
http://sourceforge.net/projects/madwifi/
Capture interface: 'athX'
Capture interface: 'wifiX' (Madwifi-NG)
Madwifi drivers in 802.11a and 802.11g combo mode. This
will seamlessly switch between bands during channel
hopping.
When using madwifi-ng, be sure all non-monitor VAPs have
been removed, otherwise madwifi will not properly report
most traffic.
madwifing_a Atheros Linux madwifi-ng
madwifing_ab Atheros Linux madwifi-ng
madwifing_ag Atheros Linux madwifi-ng
madwifing_g Atheros Linux madwifi-ng
madwifing_b Atheros Linux madwifi-ng
http://sourceforge.net/projects/madwifi/
Capture interface: 'wifiX'
*Deprecated*. Detection for madwifi-ng is built into
the standard madwifi sources. The _ng source names
have been kept to allow old configs to continue
functioning.
orinoco Lucent, Orinoco Linux Patched orinoco_cs
http://airsnort.shmoo.com/orinocoinfo.html
Capture interface: 'ethX'
The orinoco-cs drivers do not support monitor mode as-is,
but patches are on the Kismet download site for
standalone drivers, Linux 2.6 kernel drivers, and
Linux 2.6.9+ kernel drivers. These expanded patches fix
several performance issues with previous monitor mode
patches.
orinoco_14 Lucent, Orinoco Linux Orinoco 0.14+
https://savannah.nongnu.org/projects/orinoco/
Capture interface: 'ethX'
The new orinoco_cs drivers changed things subtly, but
at least they include rfmon without patching.
Patches to enable signal level reporting are available on
the kismet download site.
These drivers are NOT CURRENTLY RECCOMENDED. Once the new
Orinoco drivers have solidified, final patches for
per-packet stats will be made and this source changed.
pcapfile n/a Any n/a
Capture interface: '/path/to/file'
The pcapfile capture source feeds a stored 802.11-encap
dump file through the Kismet engine again. This can be
useful for debugging or rescanning old logs for
alert conditions. Pcapfile sources are only available
if Kismet was compiled with libpcap support.
prism2_openbsd Prism/2 OpenBSD Kernel
Capture interface: 'wiX'
Full support for Prism2 under older OpenBSD releases.
This should soon be deprecated, if possible use the
radiotap_bsd_b capture type.
prism54g PrismGT Linux prism54
http://www.prism54.org
Capture interface: 'ethX'
PrismGT 802.11g drivers supporting monitor mode.
radiotap_bsd_ab Radiotap BSD Kernel
Capture interface: various
Dual-band cards with radiotap headers.
radiotap_bsd_a Radiotap BSD Kernel
Capture interface: various
802.11a cards (or dual-band on 11a channels only) with
radiotap headers.
radiotap_bsd_b Radiotap BSD Kernel
Capture interface: various
802.11b/g cards (or dual-band on 11b channels only) with
radiotap headers.
rt2400 Ralink 2400 11b Linux rt2400-gpl
Capture interface: 'ethX'
http://rt2x00.serialmonkey.com/
Ralink 2400 802.11b cards using the serialmonkey GPL'd
rt2x00 drivers. Must use 1.2.2 beta 2 or newer drivers.
rt2500 Ralink 2500 11g Linux rt2500-gpl
Capture interface: 'ethX'
http://rt2x00.serialmonkey.com/
Ralink 2500 802.11g cards using the serialmonkey GPL'd
rt2x00 drivers. Must use 1.1.0 beta 2 or newer drivers.
rt8180 Realtek 8180 11b Linux rtl8180-sa2400
Capture interface: 'ethX'
http://rtl8180-sa2400.sourceforge.net/
Realtek 8180 based cards (there seem to be an awful lot of
them) using the GPL drivers.
viha Airport OSX viha
http://www.dopesquad.net/security/
Capture interface: 'enX'
Monitor mode support for Airport under OSX. Does not
support Airport Extreme.
vtar5k Atheros 802.11a Linux vtar5k
http://team.vantronix.net/ar5k/
vtar5k drivers handle some Atheros 802.11a cards. Chances
are you'll have better luck with madwifi drivers.
wlanng_legacy Prism/2 Linux wlan-ng 0.1.3 and earlier
http://www.linux-wlan.com/
Capture interface: 'wlanX'
Old wlan-ng drivers didn't support pcap capturing and
use a netlink socket to the kernel. These are still in
use on some embedded systems (like the Zaurus).
wlanng Prism/2 Linux wlan-ng 0.1.4 - 0.1.9
http://www.linux-wlan.com/
Capture interface: 'wlanX'
Wlan-ng prism2 drivers prior to the AVS headers.
wlanng_avs Prism/2 Linux wlan-ng 0.2.0+
http://www.linux-wlan.com/
Capture interface: 'wlanX'
Newer wlan-ng drivers support a new header type and
slightly different monitor commands to report wepped
packets.
wrt54g Linksys WRT54G Linux linksys
http://seattlewireless.net/index.cgi/LinksysWrt54g
Capture interface: 'ethX'
Capture interface: 'ethX:prismX'
Support for the drivers found in the embedded Linux
inside the Linksys WRT54G (and probably other APs using
the same firmware).
Newer firmwares (such as OpenWRT) use the prism0 device
for monitor mode data. On these firmwares, specify both
interfaces (wrt54g,eth1:prism0,foo)
wsp100 NetChem WSP100 Any n/a
http://networkchemistry.com/
Capture interface: 'host:port'
The WSP100 is an embedded device which reports 802.11
packets over UDP. The wsp100 capture source is
(generally) system agnostic, however over time it has
been less maintained than others. If you'd like to
send me patches for this, please let me know.
wtapfile n/a Any n/a
Capture interface: '/path/to/file'
Wtapfile sources are the same as pcapfile sources but
they use the Ethereal libwiretap loader. libwiretap can
automatically decompress gzipped files, etc. Wtapfile
sources are only available if Kismet was compiled with
libwiretap support.
zd1211 ZyDAS USB Linux zd1211
http://zd1211.ath.cx
Capture interface: 'wlanX'
At the time of this writing, the ZD1211 drivers have
significant data corruption while changing channel, and
often while receiving data frames. Until these problems
are addressed in the driver, it is not reccomended.
Chipsets known to NOT WORK:
Broadcom - No linux drivers, only useable with ndiswrapper or
linuxant wrappers around windows drivers.
*** UPDATE ***
See the bcm43xx source type entry. There are
experimental reverse-engineered drivers which have
monitor mode support now under Linux! If they don't
work, however, then too bad.
Airport Extreme - Really a Broadcom, with no rfmon in the OSX drivers.
*** UPDATE ***
See the bcm source for linux on ppc, it MAY work, it
may not. Currently theres no solution for OSX but
I'm looking for OSX hackers interested in redoing the
Kismet port and looking into adding more support.
Atmel - There is a hack for pseudo-monitor in USB. There is
currently no equivalent hack for PCMCIA.
HermesII - Proxim successor to the Orinoco/HermesI. No support
yet in the drivers, may be available in the future.
ndiswrapper - Anything using ndiswrapper is using WINDOWS drivers
AND CAN NOT BE USED WITH KISMET.
Quelle: http://www.kismetwireless.net/documentation.shtml
.. danke!
theoretisch ist das ja alles ganz nett, aber mich würde das mal praktisch interessieren ... wenn ich faqs und docus suche, muss ich ja nciht in nem forum posten ;)
pfu... mein Notebook hat ne IPW 3945 drinnen und unter Debian ist die Konfiguration selbiger ein absoluter Knochenjob.
Benutze debian jetzt zwar schon länger aber so wirklich 100% durchschaut habe ich linux noch nicht. Die Karte funktioniert bei mir zwar, aber erst, wenn ich, nach jedem Reboot erneut, die Treiber via "./load" Script lade. Vorher ist Funkstille und die Karte wird nichtmal wirklich erkannt. (obwohl ieee80211 und ipw3945 module geladen wurden)
cya cheza
PS: Aber ipw2200 soll ja wirklich gut funktionieren, soweit mir bekannt. Definitiv "sauberer" als die 3945 Lösung!
Powered by vBulletin® Version 4.2.5 Copyright ©2024 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.