Kismet Forums
| Posted by: | dragorn |
|---|---|
| Subject: | kismet_server new-core FATAL: No tcp port given to listen for gui connections |
| Date: | 00:43:59 12/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
You must have something bunk in your config file, or you're not telling it the proper file that you edited.
listen=tcp://127.0.0.1:2501
allowedhosts=127.0.0.1
# Maximum number of concurrent GUI's
maxclients=5
# Maximum backlog before we start throwing out or killing clients. The
# bigger this number, the more memory and the more power it will use.
maxbacklog=5000
is my config file and its fine.
-m
- kismet_server new-core FATAL: No tcp port given to listen for gui connections - beakmyn 21:49:27 10/02/2006
- kismet_server new-core FATAL: No tcp port given to listen for gui connections - dragorn 00:43:59 12/02/2006
- kismet_server new-core FATAL: No tcp port given to listen for gui connections - beakmyn 17:48:06 12/02/2006
- kismet_server new-core FATAL: No tcp port given to listen for gui connections - dragorn 18:54:02 12/02/2006
- kismet_server new-core FATAL: No tcp port given to listen for gui connections - beakmyn 14:29:45 13/02/2006