Kismet Wireless

Kismet Forums


Posted by:00
Subject:What means: "Failed to set up UI server: TcpServer bind() failed: Cannot assign requested address " ?
Date:13:46:03 17/09/2007

kismet is always exiting right after I started it. It even closes my wlan-connection to the internet sometimes when it exists.

cat /etc/network/interfaces
#auto lo
#iface lo inet loopback

cat /etc/kismet/kismet.conf | grep source=
# source=sourcetype,interface,name[,initialchannel]

lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID: wegeditiert...
Mode:Managed Frequency:2.437 GHz Access Point: 00:15:0C:72:4D:FD
Bit Rate:54 Mb/s Tx-Power:15 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=68/100 Signal level=-63 dBm Noise level=-64 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:159 Missed beacon:0

sudo kismet
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Suid priv-dropping disabled. This may not be secure.
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (Intel): Enabling monitor mode for ipw3945 source interface eth1 channel 6...
Source 0 (Intel): Opening ipw3945 source interface eth1...
Allowing clients to fetch WEP keys.
WARNING: Disabling GPS logging.
Logging networks to /var/log/kismet/
Logging networks in CSV format to /var/log/kismet/Kismet-Sep-17-2007-1.csv
Logging networks in XML format to /var/log/kismet/Kismet-Sep-17-2007-1.xml
Logging cryptographically weak packets to /var/log/kismet/Kismet-Sep-17-2007-1.weak
Logging cisco product information to /var/log/kismet/
Logging data to /var/log/kismet/Kismet-Sep-17-2007-1.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 //etc/kismet/ap_manuf
Reading client manufacturer data and defaults from //etc/kismet/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
Failed to set up UI server: TcpServer bind() failed: Cannot assign requested address
Didn't detect any networks, unlinking network list.
Didn't detect any networks, unlinking CSV network list.
Didn't detect any networks, unlinking XML network list.
Didn't detect any Cisco Discovery Packets, unlinking cisco dump
Didn't capture any packets, unlinking dump file
Didn't see any weak encryption packets, unlinking weak file
WARNING: Sometimes cards don't always come out of monitor mode
cleanly. If your card is not fully working, you may need to
restart or reconfigure it for normal operation.
Kismet exiting.
[1] + Done ${BIN}/kismet_server --silent ${server}

Does someone know what goes wrong with my kismet?


Reply to this message