Kismet Wireless

Kismet Forums


Posted by:digdug9117
Subject:dragorn - problem with hosts
Date:18:50:50 15/11/2006


Can you please help me cause I have been working on this for about 2 days now and I have rebuilt Kismet from the source. I'm using Ubuntu and NIC is Netgear WPN511 Atheros AR5212 with drives madwifi-ng. Looks like you have all the answer and I have tried it all.

> I'm not able to get kismet to connect to hosts can someone please help me out.
> Server options: none
> Client options: none
> Starting server...
> Waiting for server to start before starting UI...
> Will drop privs to digdug (1000) gid 1000
> No specific sources given to be enabled, all will be enabled.
> Enabling channel hopping.
> Enabling channel splitting.
> Source 0 (madwifi): Enabling monitor mode for madwifing_g source interface wifi0 channel 6...
> NOTICE: Created Madwifi-NG VAP kis
> 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 madwifing_g source interface kis...
> Spawned channelc control process 10120
> Dropped privs to digdug (1000) gid 1000
> Allowing clients to fetch WEP keys.
> Logging networks to /home/digdug/
> Logging networks in CSV format to /home/digdug/Kismet-Nov-14-2006-11.csv
> Logging networks in XML format to /home/digdug/Kismet-Nov-14-2006-11.xml
> Logging cryptographically weak packets to /home/digdug/Kismet-Nov-14-2006-11.weak
> Logging cisco product information to /home/digdug/
> Logging gps coordinates to /home/digdug/Kismet-Nov-14-2006-11.gps
> Logging data to /home/digdug/Kismet-Nov-14-2006-11.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 gps
> Starting UI...
> GPSD cannot connect: Connection timed out
> 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
> Sending termination request to channel control child 10120...
> Waiting for channel control child 10120 to exit...
> Kismet exiting.
> FATAL: Could not connect to localhost:2501.
> [1] + Done ${BIN}/kismet_server --silent ${server}
> Kismet exited.
> my hosts files looks like this:
> localhost
> digdug-laptop
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> ff02::3 ip6-allhosts
> my hosts.allow file:
> # /etc/hosts.allow: list of hosts that are allowed to access the system.
> # See the manual pages hosts_access(5), hosts_options(5)
> # and /usr/doc/netbase/portmapper.txt.gz
> #
> # Example: ALL: LOCAL @some_netgroup
> #
> # If you're going to protect the portmapper use the name "portmap" for the
> # daemon name. Remember that you can only use the keyword "ALL" and IP
> # addresses (NOT host or domain names) for the portmapper, as well as for
> # rpc.mountd (the NFS mount daemon). See portmap(8), rpc.mountd(8) and
> # /usr/share/doc/portmap/portmapper.txt.gz for further information.
> #
> ALL:localhost

Reply to this message