i've had that problem too... it seems to be kismet's one and only complaint, and is not really indicative of what the problem is. if you've changed the location of the log file, for instance, and the location you specified is not valid, you will get the "can't connect to server" problem.

also, i'm not sure what kind of card you're using (prism2 or other) but have you tried setting the card type to either of those? at one point, i had to tell kismet i was running OpenZaurus, hit restart, and then switch back to SharpROM for it to work correctly. try running kismet_server from the command line (su to root first)... if that works, set the properties for kismet to "execute with root privilege." you can also try overwriting all the files with a new install of kismet "ipkg install -force-overwrite <package>" and then run it with a virgin kismet.conf file to see if it works.

and, you have installed both kismet and kismet_qt, right?

i have done all of these things, and one of them always works, while none of them always works... follow? :shock:

Thanks for the reply. using Ambicoim WL1100C-CF . It's supposed to be prism2.

tried runnig from the command like. It says access denied.
I have both kismet and kismet_qt installed
tried running with it set to openzaurus to and switched it bacl. No luck
also tried a reinstall. still no luck. I dont know how to tell it to execute with root privilege. I'm new to zaurus and Linux.

just hold the stylus on the icon for kismet for a few seconds to bring up the properties, and check the box to run with root privilege. also, if you go into the console and type "su" and then your zaurus passcode as your password you can try running "kismet_server" and see if that works.

Group: Members
Posts: 28
Joined: 13-February 04
From: New York
Member No.: 1,855

Hi.
I've followed the above, and I was getting the same 'can't connect to server error.
I then ran kismet_server from the # prompt, and now it *looks* like something is happeneing, but it still doesn't find anything. I have an access point right here.
I have the laterst Sharp ROM (3.1) and a Symbol spectrum 24 wireless ethernet card.
I have tried mounting and unmounting the card, and also tried all the setting for different cards in the config menu of the kismet GIU.

Below is what printed to the console after I started kismet from the prompt, and below that is what happened when i entered the command kismet_server from root:
bash-2.05$ kismet
Server options: none
Client options: none
Starting server...
Suid priv-dropping disabled. This may not be secure.
No enable sources specified, all sources will be enabled.
Source 0 (Kismet): Using prism2 to capture packets.
FATAL: Source 0 (Kismet): Prism2 open bind() failed. (Operation not permitted)
Starting UI...
NOTICE: configdir '/home/root/.kismet/' does not exist, making it.
FATAL: Could not make configdir: Permission denied
Killing server...
kill: 11743: No such process
wait: No such job: %-
Terminating...
Done. Run kismet_unmonitor or eject and re-insert your card (or restart your
pcmcia services) to return your card to normal operation.
bash-2.05$ kismet
Server options: none
Client options: none
Starting server...
Suid priv-dropping disabled. This may not be secure.
No enable sources specified, all sources will be enabled.
Source 0 (Kismet): Using prism2 to capture packets.
FATAL: Source 0 (Kismet): Prism2 open bind() failed. (Operation not permitted)
Starting UI...
NOTICE: configdir '/home/root/.kismet/' does not exist, making it.
FATAL: Could not make configdir: Permission denied
Killing server...
kill: 11792: No such process
wait: No such job: %-
Terminating...
Done. Run kismet_unmonitor or eject and re-insert your card (or restart your
pcmcia services) to return your card to normal operation.
bash-2.05$ kismet_unmonitor
Using /usr/etc/kismet.conf sources...
Disabling monitor mode for a prism2 card on eth0
SIOCSIFFLAGS: Permission denied
SIOCSIFFLAGS: Permission denied
wlanctl-ng: No such device
You will likely need to restart your PCMCIA services to reconfigure your card
for the correct channel and SSID.
bash-2.05$ kismet
Server options: none
Client options: none
Starting server...
Suid priv-dropping disabled. This may not be secure.
No enable sources specified, all sources will be enabled.
Source 0 (Kismet): Using prism2 to capture packets.
FATAL: Source 0 (Kismet): Prism2 open bind() failed. (Operation not permitted)
Starting UI...
NOTICE: configdir '/home/root/.kismet/' does not exist, making it.
FATAL: Could not make configdir: Permission denied
Killing server...
kill: 12077: No such process
wait: No such job: %-
Terminating...
Done. Run kismet_unmonitor or eject and re-insert your card (or restart your
pcmcia services) to return your card to normal operation.
bash-2.05$

I upgraded from 3.1 to 3.13 with no problems at all with any apps. Just did a backup, upgraded ROM and then restored. Now I just set the "run with root" option on all my apps I was having problems running after upgrading to 3.1. The link below should get you to the 3.13 Sharp ROM