Help - Search - Members - Calendar
Full Version: Kismet
OESF Forums > General Forums > General Support and Discussion > Software
elremx
I installed kismet and it tells me "cant connect to the server" when I hit restart under the config page.
Amy ideas on how to make this work?

Zaurus 5500
rom 3.1
Amcicom wireless cf card


According to the kismet web site this card is supported.
harbinger1080
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:
elremx
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.
harbinger1080
QUOTE
I dont know how to tell it to execute with root privilege.


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.
Anonymous
Works great Thanks tongue.gif
elremx
sorry, forgot to sign in first

Thanks, works great
pointydog
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$




# kismet-server
kismet-server: not found
# kismet_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.
Allowing clients to fetch WEP keys.
configdir '/home/root/.kismet/' does not exist, making it.
SSID cloak file did not exist, it will be created.
IP track file did not exist, it will be created.
Logging networks to Kismet-Feb-23-2004-1.network
Logging networks in CSV format to Kismet-Feb-23-2004-1.csv
Logging networks in XML format to Kismet-Feb-23-2004-1.xml
Logging cryptographically weak packets to Kismet-Feb-23-2004-1.weak
Logging cisco product information to Kismet-Feb-23-2004-1.cisco
Logging gps coordinates to Kismet-Feb-23-2004-1.gps
Logging data to Kismet-Feb-23-2004-1.dump
Writing data files to disk every 300 seconds.
Filtering beacon packets.
Filtering PHY layer packets.
Reading AP manufacturer data and defaults from
/usr/etc/ap_manuf
Reading client manufacturer data and defaults from /usr/etc/client_manuf
Dump file format: wiretap (local code) dump
Crypt file format: airsnort (weak packet) dump
Kismet 2.8.1 (Kismet)
Source 0 (Kismet): Capturing packets from Prism/2 (DEPRECATED)
Logging data networks CSV XML weak cisco
Listening on port 2501.
Allowing connections from 127.0.0.1/255.255.255.255
Registering builtin client/server protocols...
Accepted interface connection from 127.0.0.1



I tried allowing my access point to broadcase the SSID, but no change. I get email and card lights flashing, but no networks are detected. Any ideas?
dino
Are you running as root?
stormer
make sure that your loopback device is up.
pointydog
Yes, I was running it as root.

I don't know what loopback device you mean...is it software?

THanks!

C
Anonymous
I hold down over the icon and the properties pop up. I then select run as root and click "ok". When I reopen the properties I no longer have run as root selected. Is there something I'm missing?
Anonymous
Fixed the problem by upgrading to 3.13
pointydog
where do you find 3.13, and did your other stuff still work OK?
how about all your PIMs?

I'm trying to decide what i should do, maybe upgrade too.

C
Anonymous
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

http://www.zaurususergroup.com/modules. ... it&lid=120
pointydog
Cool, thanks.
Maybe I'll try that too.
Link didn't work, but if the page is called 'modules', I'll find it!

C
ScytheBlade1
This is the only thread with an error even associated to mine....so here goes....

I have an AmbiCom WL1100C-CF wifi card. Prism2.
"Thanks for the reply. using Ambicoim WL1100C-CF . It's supposed to be prism2. "

Been here, done that. So, anyways...I've got a belkin wifi AP here, and with my winxp computer + PCI wifi card it works just fine. Strong signal, DHCP works...it just works.

Not my handheld. I use the network app to configure the AP and try to connect, but the light just blinks forever then shuts off. So, I SSH in (via cradle USB, not wifi tongue.gif) and try to bring it up manually.

CODE
# ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 00:10:7A:58:57:FB  

         BROADCAST MULTICAST  MTU:1500  Metric:1

         RX packets:0 errors:0 dropped:0 overruns:0 frame:0

         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

         collisions:0 txqueuelen:100

         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

         Interrupt:39



# iwconfig

lo        no wireless extensions.



usbd0     no wireless extensions.



eth0      no wireless extensions.



#

(Note that I have to do the 'ifconfig eth0' because otherwise it won't show, because the device is not up.)

Now, I know the wireless extensions don't appear until I bring the interface up, but...

CODE
# ifconfig eth0 up

SIOCSIFFLAGS: No such device


"No such device".

*tries to connect through the tray applet, and while the light is blinking, brings the interface up*

*gasp*
CODE
# ifconfig eth0 up

#


No error! But the stupid script dies a moment later, and bring the interface down. I try to kill the process while it's running, but as soon as I do, the interface goes down. Either that, or I manage to nab all of the processes that it runs in time, and it stays 'up'. However, it's still lacking wireless extensions. If I try it anyways...
CODE
# iwconfig eth0 essid "Brantley"

Error for wireless request "Set ESSID" (8B1A) :

   SET failed on device eth0; Function not implemented.


I have run the format time and time again. It never connects. I can't bring it up, except by the GUI applet, which also brings it down by itself shortly without connecting. I can bring it down, but not up. I can only bring it down after the GUI brought it up and I killed reams of scripts, but even then it's completly dead.

I AM NOT A HAPPY PERSON.

To answer a few questions now....
A) All commands were executed as root
cool.gif I'm running the latest version of the special kernel and ROM (SL-5600)
C) I know it's not a problem with the AP
D) PLEASE reply here, even if it's a "I have no clue", so at least I don't go wondering if anyone ever read this.
E) I'm 4 feet away from the AP. The only thing inbetween the zaurus/wifi card and the AP is air and probably several hundred dang-near invisible pieces of dust.
powered_by_penguins
I'm having similair problems with a symbol spectrum24 card on a sl5500 (sharp rom 3.10). My prob is that it "can't connect to server", but from what i've read it's because 3.10 has problems with run as root so i'm guna upgrade my rom to 3.13 (when my cf card arrives sad.gif )
Only prob with that is, every time i try to restore from a backup... it crashes and i end up hard resetting. oh well, windows makes me do full reinstalls, why not my z as well.

ScytheBlade1 - I can't personally help you, but I've seen LOTS of signatures on here that say the owner uses an ambicom card, so I reckon your best bet is to start pm'ing people till somebody gives you some info that you don't know. As ambicom cards are meant to work straight out of the box, i'm sure you won't have any problems in finding someone here who says "oh, i just did this.....". Good luck with getting it sorted out (I know how much of a bitch it is to have something that should work, not work).
Qman
I also use a AmbiCom wifi card (Model WL1100C-CF) and just installed kismet 2.8.1 and it works. The only problems that I've encountered is that in oder to connect to your network after use you must shut down Kismet and eject and re-insert the card.

BTW what version of kismet are you guys using 2.8.1 or 3.0.1?



HTH
Qman...
Inuyasha
You can find it here, now that the Sharp DevNet is back up.

http://community.zaurus.com/projects/sl5500uss/
tz
I am using a very recent kismet-devel branch (with my own patches for gzipped output files and to fix a problem with Cisco and Socket/spectrum24 cards for best signal).
mikedivincent
I upgraded to 3.13, have placed an X in the "execute with root provilege (not secure) and have the same issue "can't connect to the server". DOes anyone have any hints to make it work. I am using a Netgear MA701 CF 802.11b card - not sure if that is supported - I don't see it listed as a good card or a bad card.
sdjf
Sometimes ""can't connect to the server" messages happen when my Z doesn't have enough free memory to connect properly. I just wrote a long post at tyrannozaurus describing what I do about that.

http://www.tyrannozaurus.com/?q=node/544

I need plenty of free buffer space or tkcMail says it can't connect to server.

Maybe kismet also needs plenty of buffer space?

And I've found a simple trick to clear buffer space, just hunt for a file that doesn't exist, wink.gif as follows:

bash# find / -name xxxxxx

HTH smile.gif
sdjf
speculatrix
I think Kismet must be a memory hog... if I leave it running on my drive home which takes in Cambridge Science Park, I get about four pages full of wireless networks, of which a third are in the village where I live. Kismet slows to a crawl and is almost unusable at that point - trying to scroll through the list is so slow as to be unusable.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.