Kismet Wireless

Kismet Forums

 

Posted by:andrewjsm
Subject:Failed to set channel 52 22:invalid argument
Date:15:18:40 19/05/2006

Guys, i've gone through all the howto's and docs I could find, but can't seem to solve this problem when starting kismet for the first time. everything seems to start fine, but when the gui loads, I get a TCP error saying it can't connect to tcp:2501. I'm running FC5 with an atheros a/g card w/latest madwifi-ng drivers.

---- kismet startup output
Starting server...
Waiting for server to start before starting UI...
Will drop privs to user (500) gid 500
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (madwifi): Enabling monitor mode for madwifi_ag source interface wifi0 channel 6...
NOTICE: Created Madwifi-NG VAP kis0
WARNING: wifi0 appears to be using Madwifi-NG. Some versions of the Madwifi-NG drivers have problems in monitor mode, especially if non-monitor VAPs are active. If you experience problems, be sure to try the latest versions of Madwifi-NG and remove other VAPs
Source 0 (madwifi): Opening madwifi_ag source interface kis0...
Spawned channelc control process 2726
Dropped privs to user (500) gid 500
Allowing clients to fetch WEP keys.
WARNING: Disabling GPS logging.
Logging networks to Kismet-May-19-2006-7.network
Logging networks in CSV format to Kismet-May-19-2006-7.csv
Logging networks in XML format to Kismet-May-19-2006-7.xml
Logging cryptographically weak packets to Kismet-May-19-2006-7.weak
Logging cisco product information to Kismet-May-19-2006-7.cisco
Logging data to Kismet-May-19-2006-7.dump
Writing data files to disk every 300 seconds.
Mangling encrypted and fuzzy data packets.
Tracking probe responses and associating probe networks.
Reading AP manufacturer data and defaults from /usr/local/etc/ap_manuf
Reading client manufacturer data and defaults from /usr/local/etc/client_manuf
Using network-classifier based data encryption detection
Dump file format: wiretap (local code) dump
Crypt file format: airsnort (weak packet) dump
Kismet 2006.04.R1 (Kismet)
Logging data networks CSV XML weak cisco
Listening on port 2501.
Allowing connections from 127.0.0.1/255.255.255.255
Registering builtin client/server protocols...
Registering requested alerts...
Registering builtin timer events...
Gathering packets...
Starting UI...
Looking for startup info from localhost:2501....FATAL: Failed to set channel 52 22:Invalid argument
Terminating.
Didn't detect any Cisco Discovery Packets, unlinking cisco dump
Didn't see any weak encryption packets, unlinking weak file
Sending termination request to channel control child 2726...
Waiting for channel control child 2726 to exit...
Kismet exiting.
found.
Connected to Kismet server 2006.04.R1 on localhost:2501
Reading AP manufacturer data and defaults from /usr/local/etc/ap_manuf
Reading client manufacturer data and defaults from /usr/local/etc/client_manuf
Kismet exited.

---kismet.conf

# Version of Kismet config
version=2005.06.R1
servername=Kismet
suiduser=user
source=madwifi_ag,wifi0,madwifi
blah blah blah
.
.
# Port to serve GUI data
tcpport=2501
# People allowed to connect, comma seperated IP addresses or network/mask
# blocks. Netmasks can be expressed as dotted quad (/255.255.255.0) or as
# numbers (/24)
allowedhosts=127.0.0.1
# Address to bind to. Should be an address already configured already on
# this host, reverts to INADDR_ANY if specified incorrectly.
bindaddress=127.0.0.1
# Maximum number of concurrent GUI's
maxclients=5


Reply to this message