Raspberry Pi: Kismet ( ‏قسمة‎ ) installieren unter Debian (jessie)

Wie wird Kismet auf dem Raspberry Pi installiert? Zuerst mal eine Mindmap als Überblick zu Kismet:

kismet

Kismet wird wie folgt installiert, nachdem das System upgedated wurde:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install kismet

Check der Version mit

Ergebnis:

kismet:armhf/jessie 2013.03.R1b-3 uptodate

Seit 2013 gibt es auch keine neue Version: Latest Kismet release is Kismet-2013-03-R1b.

Dazu noch eine Mindmap mit den Abhängigkeiten von Kismet auf dem Raspberry Pi:
kismet

Nun noch ein paar Einstellungen. Die /etc/kismet/kismet.conf um folgende Einträge ergänzen (WLAN-Stick anpassen wenn nicht rt2800usb):

Das Programm starten und bedienen mit:

Frage: Starten des Servers mit:YES und dann START bestätigen und mit der TAB Taste zu “Close Console Window” gehen und schließen. Ergebnis nach ein paar Minuten mit 12 gefundenen Netzwerken:
kismet

Wenn es zu solch einer Fehlermeldung kommt:

dann vor dem starten von kismet folgende Befehle ausführen:

Mit iwconfig kann geschaut werden ob ein wlan0mon und wlan0 vorhanden sind.

In den oben eingestellen Verzeichnis /home/pi/kismet sind eine Menge log Files im Text und XML Format zu finden.

In diesen Log-Dateien kann nun z.B. nach der SSID gesucht werden:

Oder welches Tool verwendet ihr zum auswerten?

(Besucher 1.687 und 1 Heute)

10 Antworten auf „Raspberry Pi: Kismet ( ‏قسمة‎ ) installieren unter Debian (jessie)“

  1. Ich suche einen WLAN-USB-Stick für den Raspberry Pi 2 (jessi), der von Kismet unterstützt wird. Ich habe schon viel recherchiert und mehrere gekauft.
    Ich habe bisher keinen gefunden. Kann es sein, dass kismet keinen neueren Chips mehr unterstützt. Bzw. könnt Ihr mir vielleicht helfen?

      1. Ich habe 2 wlan-Sticks ausprobiert. Beide funktionieren problemlos um eine wlan-Verbindung herzustellen, nur kismet funktioniert damit nicht:
        1) Edimax EW-7612UAN V2
        2) BIGtec 150Mbit nano USB
        Kismet kann die capture source nicht erkennen. Morgen kann ich die genauen Fehlermeldungen liefern.

        1. Ich habe das jetzt mit dem BIGtec 150Mbit nano USB probiert. Wie es scheint hat der einen Realtek R8188EU Chipsatz und keinen Ralink.
          Welche ncsource-Definition sollte ich denn für diesen Stick in der kismet.conf hinterlegen? Der rt2800usb funktioniert auch nicht.

          Folgende Ausgaben erhalte ich:

          dmesg:
          [ 3.053202] usb 1-1.4: new high-speed USB device number 4 using dwc_otg
          [ 3.209885] usb 1-1.4: New USB device found, idVendor=0bda, idProduct=8179
          [ 3.209898] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
          [ 3.209907] usb 1-1.4: Product: 802.11n NIC
          [ 3.209916] usb 1-1.4: Manufacturer: Realtek
          [ 3.209925] usb 1-1.4: SerialNumber: 7CDD90A7F619

          iwconfig:
          wlan0 unassociated Nickname:””
          Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated
          Sensitivity:0/0
          Retry:off RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

          lsusb:
          Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp.

          ifconfig:
          eth0 Link encap:Ethernet HWaddr b8:27:eb:de:de:bb
          inet addr:192.168.178.40 Bcast:192.168.178.255 Mask:255.255.255.0
          inet6 addr: fe80::49e3:c0d:f5cd:e82a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2038 errors:0 dropped:13 overruns:0 frame:0
          TX packets:1441 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:208310 (203.4 KiB) TX bytes:534925 (522.3 KiB)

          lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:1367 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1367 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:185729 (181.3 KiB) TX bytes:185729 (181.3 KiB)

          wlan0 Link encap:Ethernet HWaddr 7c:dd:90:a7:f6:19
          inet addr:192.168.178.46 Bcast:192.168.178.255 Mask:255.255.255.0
          inet6 addr: fe80::c8d7:d3ef:dd0e:811a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2893 errors:0 dropped:481 overruns:0 frame:0
          TX packets:582 errors:0 dropped:2 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:462443 (451.6 KiB) TX bytes:130341 (127.2 KiB)

          kismet-Fehlermeldungen wenn in der kismet.conf: ncsource=wlan0:type=rt8180 definiert ist
          [SERVER] ERROR: Detected the following processes that appear to be using the interface
          [SERVER] wlan0, which can cause problems with Kismet by changing the
          [SERVER] configuration of the network device: wpa_supplicant dhclient. If
          [SERVER] Kismet stops running or stops capturing packets, try killing one (or
          [SERVER] all) of these processes or stopping the network for this interface.
          [SERVER] ERROR: Detected the following processes that appear to be using the interface
          [SERVER] wlan0, which can cause problems with Kismet by changing the
          [SERVER] configuration of the network device: wpa_supplicant dhclient. If
          [SERVER] Kismet stops running or stops capturing packets, try killing one (or
          [SERVER] all) of these processes or stopping the network for this interface.
          [SERVER] ERROR: Source ‘wlan0’ doesn’t have mac80211 support, disabling VAP creation of
          [SERVER] default monitor mode VAP
          [SERVER] ERROR: mode set ioctl failed 22:Invalid argument
          [SERVER] ERROR: Failed to set monitor mode on interface ‘wlan0’, even after bringing
          [SERVER] interface into a down state. This usually means your drivers either do
          [SERVER] not report monitor mode, use a different mechanism than Kismet expected
          [SERVER] to configure monitor mode, or that the user which started Kismet does
          [SERVER] not have permission to change the driver mode. Make sure you have the
          [SERVER] required version and have applied any patches needed to your drivers,
          [SERVER] and that you have configured the proper source type for Kismet. See the
          [SERVER] troubleshooting section of the Kismet README for more information.
          [SERVER] ERROR: mode set ioctl failed 22:Invalid argument
          [SERVER] ERROR: Failed to set monitor mode on interface ‘wlan0’, even after bringing
          [SERVER] interface into a down state. This usually means your drivers either do
          [SERVER] not report monitor mode, use a different mechanism than Kismet expected
          [SERVER] to configure monitor mode, or that the user which started Kismet does
          [SERVER] not have permission to change the driver mode. Make sure you have the

          1. Der WLAN-Stick funktioniert auch alleine (LAN-Kabel entfernt). Ich komme dann mit putty über WLAN auf den pi.

            dmesg liefert dann folgendes:
            [ 5.816434] r8188eu: module is from the staging directory, the quality is unknown, you have been warned.
            [ 5.833438] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_UNKNOWN_CUT(10)_1T1R_RomVer(0)
            [ 5.876956] usbcore: registered new interface driver r8188eu
            [ 12.457424] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
            [ 13.273777] cfg80211: Calling CRDA to update world regulatory domain
            [ 13.983464] MAC Address = 7c:dd:90:a7:f6:19
            [ 13.986785] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
            [ 13.986875] cfg80211: World regulatory domain updated:
            [ 13.986892] cfg80211: DFS Master region: unset
            [ 13.986904] cfg80211: (start_freq – end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
            [ 13.986922] cfg80211: (2402000 KHz – 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
            [ 13.986938] cfg80211: (2457000 KHz – 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
            [ 13.986954] cfg80211: (2474000 KHz – 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
            [ 13.986973] cfg80211: (5170000 KHz – 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
            [ 13.986991] cfg80211: (5250000 KHz – 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
            [ 13.987008] cfg80211: (5490000 KHz – 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
            [ 13.987024] cfg80211: (5735000 KHz – 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
            [ 13.987040] cfg80211: (57240000 KHz – 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
            [ 16.080637] R8188EU: ERROR assoc success
            [ 16.080863] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
            [ 17.917093] smsc95xx 1-1.1:1.0 eth0: hardware isn’t capable of remote wakeup
            [ 17.917347] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

  2. Ich habe jetzt gemäß folgendem Link: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=62371 eine neue Firmware für den Chip geladen.

    Jetzt sieht dmesg besser aus:
    [ 3.053202] usb 1-1.4: new high-speed USB device number 4 using dwc_otg
    [ 3.209885] usb 1-1.4: New USB device found, idVendor=0bda, idProduct=8179
    [ 3.209898] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 3.209907] usb 1-1.4: Product: 802.11n NIC
    [ 3.209916] usb 1-1.4: Manufacturer: Realtek
    [ 3.209925] usb 1-1.4: SerialNumber: 7CDD90A7F619

    [ 5.460817] cfg80211: Calling CRDA to update world regulatory domain
    [ 5.570004] RTL871X: module init start
    [ 5.570047] RTL871X: rtl8188eu v4.3.0.8_13968.20150417
    [ 5.570060] RTL871X: build time: Nov 13 2015 22:24:22
    [ 5.575747] bFWReady == _FALSE call reset 8051…
    [ 5.588341] random: nonblocking pool is initialized
    [ 5.613655] RTL871X: rtw_ndev_init(wlan0)
    [ 5.615936] usbcore: registered new interface driver rtl8188eu
    [ 5.615957] RTL871X: module init ret=0
    [ 5.830711] cfg80211: World regulatory domain updated:
    [ 5.830744] cfg80211: DFS Master region: unset
    [ 5.830757] cfg80211: (start_freq – end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    [ 5.830775] cfg80211: (2402000 KHz – 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 5.830791] cfg80211: (2457000 KHz – 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 5.830807] cfg80211: (2474000 KHz – 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
    [ 5.830825] cfg80211: (5170000 KHz – 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
    [ 5.830843] cfg80211: (5250000 KHz – 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
    [ 5.830860] cfg80211: (5490000 KHz – 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    [ 5.830876] cfg80211: (5735000 KHz – 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
    [ 5.830892] cfg80211: (57240000 KHz – 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
    [ 6.753699] ==> rtl8188e_iol_efuse_patch
    [ 7.067441] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 9.443199] RTL871X: nolinked power save enter
    [ 9.793691] ==> rtl8188e_iol_efuse_patch
    [ 10.129526] RTL871X: nolinked power save leave
    [ 10.129897] RTL871X: rtw_set_802_11_connect(wlan0) fw_state=0x00000008
    [ 10.175306] RTL871X: start auth
    [ 10.178109] RTL871X: auth success, start assoc
    [ 10.188476] RTL871X: rtw_cfg80211_indicate_connect(wlan0) BSS not found !!
    [ 10.188522] RTL871X: assoc success
    [ 10.188669] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 10.188951] cfg80211: Calling CRDA for country: DE
    [ 10.190346] RTL871X: recv eapol packet
    [ 10.198478] RTL871X: send eapol packet
    [ 10.207407] RsvdPageNum: 8
    [ 10.212023] cfg80211: Regulatory domain changed to country: DE
    [ 10.212051] cfg80211: DFS Master region: ETSI
    [ 10.212064] cfg80211: (start_freq – end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    [ 10.212082] cfg80211: (2400000 KHz – 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 10.212101] cfg80211: (5150000 KHz – 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (N/A)
    [ 10.212119] cfg80211: (5250000 KHz – 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
    [ 10.212136] cfg80211: (5470000 KHz – 5725000 KHz @ 160000 KHz), (N/A, 2698 mBm), (0 s)
    [ 10.212152] cfg80211: (57000000 KHz – 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
    [ 11.190680] RTL871X: recv eapol packet
    [ 11.191336] RTL871X: send eapol packet
    [ 11.196450] RTL871X: recv eapol packet
    [ 11.196872] RTL871X: send eapol packet
    [ 11.197298] RTL871X: set pairwise key camid:4, addr:24:65:11:e2:ea:3e, kid:0, type:TKIP
    [ 11.203212] RTL871X: recv eapol packet
    [ 11.204138] RTL871X: send eapol packet
    [ 11.206068] RTL871X: set group key camid:5, addr:24:65:11:e2:ea:3e, kid:1, type:TKIP

    Kismet liefert jetzt folgende Fehler:
    [SERVER] ERROR: Detected the following processes that appear to be using the interface
    [SERVER] wlan0, which can cause problems with Kismet by changing the
    [SERVER] configuration of the network device: wpa_supplicant dhclient. If
    [SERVER] Kismet stops running or stops capturing packets, try killing one (or
    [SERVER] all) of these processes or stopping the network for this interface.
    [SERVER] ERROR: Detected the following processes that appear to be using the interface
    [SERVER] wlan0, which can cause problems with Kismet by changing the
    [SERVER] configuration of the network device: wpa_supplicant dhclient. If
    [SERVER] Kismet stops running or stops capturing packets, try killing one (or
    [SERVER] all) of these processes or stopping the network for this interface.
    [SERVER] ERROR: Source ‘wlan0’: channel get ioctl failed 22:Invalid argument
    [SERVER] ERROR: Packet source ‘wlan0’ failed to set channel 1: mac80211_setchannel()
    [SERVER] could not set channel 1/2412 on interface ‘wlan0mon’ err -10
    [SERVER] ERROR: Packet source ‘wlan0’ failed to set channel 5: mac80211_setchannel()
    [SERVER] could not set channel 5/2432 on interface ‘wlan0mon’ err -10
    [SERVER] ERROR: Packet source ‘wlan0’ failed to set channel 9: mac80211_setchannel()
    [SERVER] could not set channel 9/2452 on interface ‘wlan0mon’ err -10
    [SERVER] ERROR: Packet source ‘wlan0’ failed to set channel 13: mac80211_setchannel()
    [SERVER] could not set channel 13/2472 on interface ‘wlan0mon’ err -10
    [SERVER] ERROR: Packet source ‘wlan0’ failed to set channel 2: mac80211_setchannel()
    [SERVER] could not set channel 2/2417 on interface ‘wlan0mon’ err -10
    [SERVER] ERROR: Packet source ‘wlan0’ failed to set channel 6: mac80211_setchannel()
    [SERVER] could not set channel 6/2437 on interface ‘wlan0mon’ err -10
    [SERVER] ERROR: Packet source ‘wlan0’ failed to set channel 10: mac80211_setchannel()
    [SERVER] could not set channel 10/2457 on interface ‘wlan0mon’ err -10
    [SERVER] ERROR: Packet source ‘wlan0’ failed to set channel 3: mac80211_setchannel()
    [SERVER] could not set channel 3/2422 on interface ‘wlan0mon’ err -10

    1. Habe jetzt auch folgende Befehle ausgeführt:
      sudo pkill wpa_cli
      sudo pkill ifplugd
      sudo pkill wpa_supplicant

      Die Fehler in kismet bleiben jedoch dieselben.
      iwconfig liefert:
      wlan0mon IEEE 802.11bgn Mode:Monitor Tx-Power=12 dBm
      Retry short limit:7 RTS thr:off Fragment thr:off
      Power Management:off

      wlan0 unassociated Nickname:””
      Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated
      Sensitivity:0/0
      Retry:off RTS thr:off Fragment thr:off
      Power Management:off
      Link Quality:0 Signal level:0 Noise level:0
      Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
      Tx excessive retries:0 Invalid misc:0 Missed beacon:0

      1. Wenn ich Realtek als Source-Name in der kismet.conf angebe, liefert kismet folgenden Fehler:

        [SERVER] ERROR: Didn’t understand driver ‘rtl8188eu’ for interface ‘wlan0’, but it looks
        [SERVER] like a mac80211 device so Kismet will use the generic options for it.
        [SERVER] Please post on the Kismet forum or stop by the IRC channel and report
        [SERVER] what driver it was.
        [SERVER] ERROR: Source ‘Realtek’: channel get ioctl failed 22:Invalid argument
        [SERVER] ERROR: Packet source ‘Realtek’ failed to set channel 1: mac80211_setchannel()
        [SERVER] could not set channel 1/2412 on interface ‘wlan0mon’ err -10

        1. Vielleicht sagen Sie mir einfach einen WLAN-USB-Stick, den ich z.B. bei amazon aktuell kaufen kann und der mit dem pi 2 jessi unter kismet läuft.
          Das wäre, glaube ich, einfacher.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.