Kismet Wireless

Kismet Forums


Posted by:beakmyn
Subject:kismet_server new-core FATAL: No tcp port given to listen for gui connections
Date:21:49:27 10/02/2006

Because I'm a masochist I cross-compiled server for my WRT, Took a whole day to do it but I finally figured it out. So, I relize grab the kismet.conf file and make the needed changes for the WRT. I think I've got it all right but when I run

#kismet_server -f /etc/kismet.conf
it starts up and tells me all about dropping privs and


8< snip
# Client/server listen config
# People allowed to connect, comma seperated IP addresses or network/mask
# blocks. Netmasks can be expressed as dotted quad (/ or as
# numbers (/24)
# Maximum number of concurrent GUI's
# Maximum backlog before we start throwing out or killing clients. The
# bigger this number, the more memory and the more power it will use.
8< snip

Doesn't listen=tcp:// tell it what port to listen on?

Reply to this message