Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

  1. #1
    Join Date
    Oct 2010
    Beans
    6

    Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

    Hi all,
    I installed kismet but i couldn't run it. Also google couldn't help me more. Here is my problem:

    myuser@mypc:~$ sudo kismet
    Launching kismet_server: //usr/bin/kismet_server
    Suid priv-dropping disabled. This may not be secure.
    No specific sources given to be enabled, all will be enabled.
    Non-RFMon VAPs will be destroyed on multi-vap interfaces (ie, madwifi-ng)
    Enabling channel hopping.
    Enabling channel splitting.
    NOTICE: Disabling channel hopping, no enabled sources are able to change channel.
    Source 0 (Intel): Enabling monitor mode for iwl3945 source interface wlan0 channel 6...
    FATAL: channel get ioctl failed 22:Invalid argument
    Done.


    * iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.

    wlan0 IEEE 802.11abg ESSIDff/any
    Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
    Retry long limit:7 RTS thrff Fragment thrff
    Power Managementff


    * lshw -C network
    *-network
    description: Wireless interface
    product: PRO/Wireless 3945ABG [Golan] Network Connection
    vendor: Intel Corporation
    physical id: 0
    bus info: pci@0000:03:00.0
    logical name: wlan0
    version: 02
    serial: 00:1b:77:8e:46:94
    width: 32 bits
    clock: 33MHz
    capabilities: bus_master cap_list ethernet physical wireless
    configuration: broadcast=yes driver=iwl3945 driverversion=2.6.35-22-generic firmware=15.32.2.9 latency=0 multicast=yes wireless=IEEE 802.11abg
    resources: irq:45 memory:edf00000-edf00fff


    * kismet.conf
    # Sources are defined as:
    # source=sourcetype,interface,name[,initialchannel]
    # Source types and required drivers are listed in the README under the
    # CAPTURE SOURCES section.
    # The initial channel is optional, if hopping is not enabled it can be used
    # to set the channel the interface listens on.
    # YOU MUST CHANGE THIS TO BE THE SOURCE YOU WANT TO USE
    source=iwl3945,wlan0,Intel


    ubuntu 10.10
    kismet 2008.05.R1


    Pls help me fix it.
    Thanks a mil.

  2. #2

    Re: Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

    Funny. I use the same card, and it was working for me under 9.04, and now I get the same issues with 9.10 ...

    I'm stumped, too. Kismet's documentation is ... well, it's not the clearest.

  3. #3
    Join Date
    Oct 2010
    Beans
    6

    Re: Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

    Thanks for your reply. We are the same.
    Somebody helps us.

  4. #4
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    21,411
    Distro
    Ubuntu 15.04 Vivid Vervet

    Re: Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

    Is the behavior improved if you do:
    Code:
    sudo ifconfig wlan0 down
    sudo iwconfig wlan0 mode monitor
    sudo kismet
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  5. #5
    Join Date
    Oct 2010
    Beans
    6

    Re: Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

    Quote Originally Posted by chili555 View Post
    Is the behavior improved if you do:
    Code:
    sudo ifconfig wlan0 down
    sudo iwconfig wlan0 mode monitor
    sudo kismet
    It's awsome. Worked like a charm.
    Thanks a mil.

  6. #6
    Join Date
    Jul 2005
    Beans
    55

    Re: Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

    I am having that exact same problem after my upgrade to 10.10 (10.04 worked perfectly) and the above trick does not work for me. Despite iwconfig showing my card in monitor mode, Kismet still throws that same error. airodump-ng works just fine, however, so something's definitely not right with Kismet. I am also using the iwl3945 driver. Any ideas?

    UPDATE: Kismet runs fine on the same machine, but with an rtl8187-based device, so it looks like this is a problem with the iwl3945.
    Last edited by pestie; November 19th, 2010 at 12:21 AM. Reason: Added more information

  7. #7
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    21,411
    Distro
    Ubuntu 15.04 Vivid Vervet

    Re: Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

    My iwl3945 works perfectly with kismet in 10.10. Would you care to troubleshoot a bit?
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  8. #8
    Join Date
    Jul 2005
    Beans
    55

    Re: Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

    Sure, I'll gladly try whatever troubleshooting you can suggest.

  9. #9
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    21,411
    Distro
    Ubuntu 15.04 Vivid Vervet

    Re: Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

    Quote Originally Posted by pestie View Post
    Sure, I'll gladly try whatever troubleshooting you can suggest.
    What does your kismet.conf sources line look like?
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  10. #10
    Join Date
    Jul 2005
    Beans
    55

    Re: Problem with kismet "FATAL: channel get ioctl failed 22:Invalid argument"

    Code:
    source=iwl3945,wlan0,intel
    It's the exact same line that used to work just fine in 10.04.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •