OESF Portables Forum
Everything Else => Sharp Zaurus => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => 6000 - Tosa => Topic started by: thomasbernie on April 08, 2004, 02:36:38 pm
-
I\'m buying for the first one to figure out how to make Kismet play. Everything installs OK and seems to be in the right place, but no receive. I wonder how far off OZ is?
-
I'm buying for the first one to figure out how to make Kismet play. Everything installs OK and seems to be in the right place, but no receive. I wonder how far off OZ is?
On the SL-6000 it may be a ways away. I have tried 3 different versions of Kismet (2.4.6, 2.81, and kismet-2004-04-R1-arm). I have had no sucess detecting any networks. The most recent version kismet-2004-04-R1-arm just dumps (like a core dump).
Given that the SL-6000 has a newer wireless card, someone smarter than me will have to show us how..
Craig...
-
Craig,
I have tried all versions too. 3.0.1 that I have on my laptop, gives me a bus fault. 2.8.1 is installed, the server works, -qt seems ok -- it just does not hear anything. There must be a Linux guru that can figure out how the card gets recognized.
Good Luck
-
what chip set does it use?
-
what chip set does it use?
I think you are asking what 802.11b chipset? I have my Kismet set to Prism2.
I even put in my old D-Link CF card (from my SL-5500, where Kismet works) and I can't get it to work with that card either.
Thanks,
Craig...
-
I am having the same problems getting kismet to work on a 5600 with prism2. Kismet works fine with the same wireless card on a lap top running Knoppix, so I suppose the older kismet wont work with prism2 on a newer kernel (then what the 5500 had), while the latest kismet wont work with the reletively old kernel the 5600 has.
I ordered one of the last two 6000\'s amazon had in stock last week, now they have sent me an email saying its not even released yet!. I would love to run kismet on the 6000 so I hope someone figures it out by the time I get one.
-
a solution found here:
https://www.oesf.org/index.php?title=How_to...on_the_SL-6000L (https://www.oesf.org/index.php?title=How_to_run_Kismet_on_the_SL-6000L)
I have just installed Kismet on my 6000L
Thanks!
-
Are you running it on the 6000L with the internal (USB) prism2 device? Or do you have a CF wireless card?
-
I have it running on my 6000L with the built-in prism2 card. It\'s a little flakey I guess since I can\'t seem to issue any commands to it via the keyboard. But it definately scans and picks up networks.
-
The link for the libpcap0_0.7.2_arm.ipk doesn\'t work! I tried both the versions from Killfez.de and Zaurusgroup but they all gave me an error.
Help!
FW
-
The link for the libpcap0_0.7.2_arm.ipk doesn\'t work! I tried both the versions from Killfez.de and Zaurusgroup but they all gave me an error.
Help!
FW
Exactly what error? Just one of those ambigous \"there has been an error\"?
If so, try running ipkg from the command line, do this by typing `ipkg install libpcap0_0.7.2_arm.ipk`. That more often than not will give you a more descriptive error. Also, you may have the problem I had where it\'s a .ipk file and Opera will download it but put a .tar on the end.
-
Followed the instructions. Works. Yea!!
Thanks
-
My 6000L just went out of battery after playing around so much :-( I will try it again and post what the error mesage is. BTW, which feed(Killfez or Zaurusuergroup) were you able to use successfully?
Thanks
FW
-
Pretty sure I got it from killfez.
-
There has been quite a bit of discussion about how to get Kismet running on a SL-6000 in another forum. But a How-to was created and I think describes it pretty well:
http://www.zaurususergroup.com/modules.php...0the%20SL-6000L (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=How%20to%20run%20Kismet%20on%20the%20SL-6000L)
I hope this helps, I know it did for me.
Craig...
-
I followed the guide but the link for the libpcap doesn\'t work for me.
If I use the libpcap I downloaded from Killefiz I got the following error:
zcat: libpcap0_0.7.2-1_arm.ipk: not in gzip format
zcat: stdin: unexpected end of file
ipkg_install_file: ERROR unpacking control.tar.gza from libpcap0_0.7.2-1arm.ipk
Can some tell me what\'s wrong?
Thanks
FW
-
the link should work again now. Sorry, I must have erased it by accident
-
Thanks forrepairing the link. I THINK kismet work for me now: I don;t have an AP at home, kismet couldn\'t find anything but at least it\'s not giving me \"cannot connect to server\". Maybe I will go to a Starbucks tomorrow and see if I can detect any network.
FW
-
First off, hello. I was really glad to find this site and have seen some great info so far.
I just got a 6000L and am attempting to get Kismet up and running. I have followed all the instructions throughout the site including the 6000L kismet instructions guide and what is on killefiz. I am getting an error when I start kismet: "Can't connect to the server." One thing I have seen is that I don't have the version of libpcap recommended on all the install guides (I can't find an active link to libpcap0_0.7.2_arm.ipk). If anyone has some advice to share I would greatly appreciate it as well as perhaps a copy of libpcap0_0.7.2_arm.ipk.
TIA
-
I guess I deleted it from my site by accident
try
http://members.cox.net/skoorb/libpcap0_0.7.2_arm.ipk (http://members.cox.net/skoorb/libpcap0_0.7.2_arm.ipk)
-
thanks for the link skoorb. If anyone out there has had similar problems with "can't connect to server" I would appreciate some guidance on resolving the problem. I have all the right files now but am still getting the error.
Thanks
-
i guess you probably already tried the how to for this here
http://www.zaurususergroup.com/modules.php...0the%20SL-6000L (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=How%20to%20run%20Kismet%20on%20the%20SL-6000L)
-
If anyone out there has had similar problems with "can't connect to server" I would appreciate some guidance on resolving the problem. I have all the right files now but am still getting the error.
Thanks
I had this problem after the link to libstdc++ was broken.
From the how-to:
2) In terminal:
su
Copy libstdc++ to /usr/lib. Make sure the file permissions match the other libraries. Create a link to libstdc++-libc6.1-2.so.3. (ln -s libstdc++-3-libc6.1-2-2.10.0.so libstdc++-libc6.1-2.so.3)
But there may be other ways to cause this error.
-
Thanks for all the input. I am still having the same problem. If I run kismet from the term, I get the following error:
3769: Segmentation fault
Any suggestions?
Thanks
-
What version of Kismet are you trying to install? I never got 3.10 to work, but 3.0.1 worked just fine. Cacko ROM here.
-
I thought we were talking about an SL 6000 here. Maybe I should see if I can get Kismet working on mine since I just got my SD memory in today.
-
I tried 3.1.0 and 3.0.1c w/o success.
All the solutions offered were greatly appreciated, but the problem seemed to be elsewhere. So, backed out the whole install, re-downloaded everything, installed, configured, and it is now working fine.
The conclusion...a corrupted version of kismet was to blame.
What worked for me was as follows:
kismet 3.0.1c
kismet-qt 2
libpcap 0.7.2
libstdc++
http://www.zaurususergroup.com/modules.php...0the%20SL-6000L (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=How%20to%20run%20Kismet%20on%20the%20SL-6000L)
Thanks for all the help. Maybe this ordeal will assist another person who has "tried everything"
-
Hi, all
I think I have followed the howto but kismet_server tells me:
"no valid packet sourced defined"
kistmet-qt can_t connect to server.
Any hints?
klaus-peter
-
Hello,
I followed the instructions. Received no error or warning messages.
I created the war-walk connection and it works.
While connected to war-walk, I launch kismet via the icon.
It opens to the configure screen. I choose Sharp Prism2 and tap restart.
When the restart is over, it says "Can't connect to server"
I've tried other settings, but they all return the same message. Our entire facility is wired. Could it be a security setting on our wireless? Or did I botch the install some how?
I've also tried connecting via my normal "work" network profile. Then launch kismet. Same thing is returned "Can't connect to server".
Thanks,
Roger
-
While connected to war-walk, I launch kismet via the icon.
It opens to the configure screen. I choose Sharp Prism2 and tap restart.
When the restart is over, it says "Can't connect to server"
I've tried other settings, but they all return the same message. Our entire facility is wired. Could it be a security setting on our wireless? Or did I botch the install some how?
Two possibilities.
Is your "war-walk" configuration staying up and connected? - I.e. is it in ad-hoc mode? If it is then connect to that and run kismet from the command line and see what it says. Properly configured without a client talking to it - it will run and report an initial snif and then exit.
Otherwise it will most likely tell you exactly whats wrong.
-
When I choose my war-walk profile and click connect, the green light at the top of my 6000L just blinks. At the bottom of the screen I do have an icon which is green. If I tap it, it asks if I want to disconnect. I go to the terminal and do an ifconfig I get 10.1.0.2 for my inet addr. But the top light never turns to a solid green color. So I'm guessing it's not connecting. Funny thing is, when I run kismet and click on restart, then the light at the top goes to a solid green. But kismet always returns "can't connect to server"...
Here are my settings:
Config
-------
ESS-ID: any
Network Type: 802.11 Ad-Hoc
Channel: 1
WEP
-----
Disabled
TCP/IP
--------
IP Address: 10.1.0.2
Subnet Mask: 255.0.0.0
Gateway: 10.1.0.1
DNS
-----
Primary DNS: 10.1.0.1
Proxy
------
No Proxy
-
angst said:
I had this problem after the link to libstdc++ was broken.
From the how-to:
CODE
2) In terminal:
su
Copy libstdc++ to /usr/lib. Make sure the file permissions match the other libraries. Create a link to libstdc++-libc6.1-2.so.3. (ln -s libstdc++-3-libc6.1-2-2.10.0.so libstdc++-libc6.1-2.so.3)
I am new to Linux. I have been working on this topic since last night. Everything is under control except creating a link step. I assume I must first locate libstdc++-libc6.1-2.so.3. I just can't find the darn thing.
-
I got kismet working by following the instructions exactly at
linklink (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=How%20to%20run%20Kismet%20on%20the%20SL-6000L)
as a newbie user, one thing in the instruction I did not follow immediately was
to run the kismet GUI as root, which can be set by tapping the kismet icon longer.
In the config it is also set to be "root". By default it is not set I remember.
I tried to set it to "zaurus" and run but it does not work.
Hope this help
-
Does anyone else's Zaurus lock up after running Kismet for so long? I have to yank out my battery to reboot it and I can see it getting slower as kismet runs.
-
sharppda said;
I got kismet working by following the instructions exactly at.
I am glad you were successful but could you tell me from where you got the .so.3 file from? I need help with the "link" procedure. See my first post.
Thanks.
-
Here it is
file (http://zaurus.xavierxeon.de/devel/gcc/libstdc++-3-libc6.1-2-2.10.0.so)
link is also in the instruction.
-
Ok, let me try again. I already have libstdc++-3-libc6.1-2-2.10.0.so what I am looking for is libstdc++-libc6.1-2.so.3.
I hope this is now better understood. Thanks again.
-
Ok, let me try again. I already have libstdc++-3-libc6.1-2-2.10.0.so what I am looking for is libstdc++-libc6.1-2.so.3.
I hope this is now better understood. Thanks again.
OK. I see. You don't need to download libstdc++-libc6.1-2.so.3. Creating the link per the how-to (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=How%20to%20run%20Kismet%20on%20the%20SL-6000L) creates a file (kinda like a windows shortcut) named libstdc++-libc6.1-2.so.3 which actually points to libstdc++-3-libc6.1-2-2.10.0.so .
At least I think this is how it works. I'm no linux geek but I'm learning.
-
Thanks anqst, Thanks sharppda, Kismet is up and running. I told you I am a newbie. Please forgive my silly question.
-
Possibly solved.....
When I click connect for my war walk profile....and then go to terminal and su and then type kismet.....it runs...
it returns a text table type display showing networks and how long kismet has been running....interesting, it works from command line and not from icon.....
thanks everyone!
Roger
-
Don't know if you've discovered this yet - Hold your stylus on the Kismet icon for about 2 seconds. A menu will come up - select "Execute with root privilege".
Sounds like your "War-Walk" connection is working as it should BTW. The Wifi light blinks when the card is active but not associated with an AP.
-
SOLVED!
That worked. Once I checked "Run with Root privilages", the server unavaliable message went away. Now it starts without a problem!
Thanks,
Roger
-
hey i was wondering if anyone was able to get it to play sound when it finds a new net? mine hasnt been able to yet
-
Oddly enough, mine doesn't play sound either when it finds a new network....
-
a solution found here:
http://www.zaurususergroup.com/modules.php...0the%20SL-6000L (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=How%20to%20run%20Kismet%20on%20the%20SL-6000L)
I have just installed Kismet on my 6000L
Thanks!
Followed these instructions, and got it working perfectly. No sound though...
-
I got it working thanks to the HowTo. One weird thing, I use the gui on my SL5600 and it starts up my wifi card automagically, I wonder why the 6K doesn't?
I was able to start up a non-gui kismet session from the konsole and then it does play sounds.
-
Does anyone else's Zaurus lock up after running Kismet for so long? I have to yank out my battery to reboot it and I can see it getting slower as kismet runs.
I followed the instructions too and now have Kismet running.
But sadly, after finding a few networks, it just freezes up the whole Z.
I have to do a reset - the <Power> <Rec> button and reset switch on the back .
(BTW) how do we do a soft reset on the 6000L ?
I dont know why kismet is hanging up as of yet ...
-
I've gotten that Kismet freeze occasionally, but only a soft reset (Reset button on the back only) seemed to work.
-
I think I have everything set up right... I can run kismet from the terminal or with GUI without any problems, however, It doesnt pick up any APs. I have my home AP broadcasting and it doesnt see it. What is causing this? Is there a setting in the kismet.conf file that i need to change?
thanks!
-
From the how-to.
6) vi /home/root/usr/local/etc/kismet.conf to enable source=prism2,wlan0,prism2source. You may also want to turn off GPS support (unless you have one).
-
I followed the howto, but now I have a new problem: When I try to start kismet from the terminal I get a fatal error: Source 0 (prism2source): Pcap support was not compiled in.
I have a sl-6000L with the original rom installed, using the internal wireless. I have gone through the process a few times (uninstall and reinstall etc.) but this error is persistent. I assume this error is a result of the pcap ipk should I try a different version?
I appreciate your help
-
Kismet is hit or miss on my box sometimes it finds stuff and other times it does not. The other day I was running it on my 6000 & my 5600 on the way to work. The 5600 found 20+ networks and the 6000 found 1. The 6000 didn't even report finding the 5600.
-
I wonder if there's a way to increase the SL-6000L's antenna strength? I've noticed its personally not the strongest around...
-
I wonder if there's a way to increase the SL-6000L's antenna strength? I've noticed its personally not the strongest around...
Problem is that it is an internal antenna. Works fine around the house but not the best for long range.
I know there are a few folks who have taken their 6000s apart. Any ideas for a better antenna setup?
Bob Makowsky
bump+
-
Sure thing! However, bearing in mind the chassis-fit and portability of the device on the Z6K, it wouldn't look too pretty but definitely a signal-puller monster once you have this setup like what David did :
http://www.biancorama.com/zaurus-sec/zauru...enna_howto.html (http://www.biancorama.com/zaurus-sec/zaurus+kismet+antenna_howto.html)
I've ordered my set and got the same 12dBi Yagi but didn't realize that it was so HUGE! Also remember to get a second battery pack as wi-fi sucks up lotsa juice!
Have fun!
/celtron
I wonder if there's a way to increase the SL-6000L's antenna strength? I've noticed its personally not the strongest around...
Problem is that it is an internal antenna. Works fine around the house but not the best for long range.
I know there are a few folks who have taken their 6000s apart. Any ideas for a better antenna setup?
Bob Makowsky
bump+
[div align=\"right\"][a href=\"index.php?act=findpost&pid=62151\"][{POST_SNAPBACK}][/a][/div]
-
I have not tried kismet yet, but intend to shortly.
Some people have complained that, over time, kismet
will cause the 6000 to freeze. I saw a note saying
one should run "kismet -n" to prevent large log files.
I wonder if it is the case that those people who had
thier 6000 freeze did not do this, and thus the log
file got too big, causing the 6000 to freeze.
If the log file is created in the flash memory area
this seems like this could be the problem.
just a thought
-
I write the log files to the SD card and have not had any freezes since moving them there.
John
-
Really odd. All the kismet .ipks are giving me hassle when installing.
I get the messgae ".ipk says something went wrong. Sorry." when trying to install lipcap.7.2, kismet-qt and kismet 3.0.1c. to any media, interal or external. And I know it's not a bug with Add/Remove because I've installed other apps before and after.
What gives? Anyone else having this same trouble?
-
Really odd. All the kismet .ipks are giving me hassle when installing.
I never did figure out why the .ipks weren't installing. I just tapped on them repeatedly from both network feeds and the Install Files folder and after a while they suddenly installed. Forget skill and know-how. What it takes is persistence.
I had to edit the .conf file in BBEdit (copy, edit, paste, delete, rename) but now Kismet is working like it should. Found my internet sharing address on my iBook.
Thanks, everyone, for figuring all this out so all I had to do was follow directions and wrestle with my own ignorance.
One remaining question, though: Does Kismet automatically join the networks it finds, or does the user have to do that manually through the Network app?
-
Kismet only scans. There was a package someone put toghether called SLAPASS Simple Linux Access Port Associator the I think was designed to scan and then associate with a network. I tried it on my 5600 but never got it working. Have not tried it on my 6000.
-
I was able to get kismet running on the Z6K, thanks to the tutorial, but I am having the same problem as some of the other people here in that the Zaurus freezes once you close it.
Did anybody find a solution to this problem yet ?
Does anyone else's Zaurus lock up after running Kismet for so long? I have to yank out my battery to reboot it and I can see it getting slower as kismet runs.
I followed the instructions too and now have Kismet running.
But sadly, after finding a few networks, it just freezes up the whole Z.
I have to do a reset - the <Power> <Rec> button and reset switch on the back .
(BTW) how do we do a soft reset on the 6000L ?
I dont know why kismet is hanging up as of yet ...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=58279\"][{POST_SNAPBACK}][/a][/div]
-
Hi,
I have a z6kl, and I am trying to find kismet_3.0.1c-20031228_arm.ipk. So far all of the sites that I have been too, which list a link to it, are dry.
Cheers,
lek
-
enjoy !
-
enjoy !
[div align=\"right\"][a href=\"index.php?act=findpost&pid=72186\"][{POST_SNAPBACK}][/a][/div]
Thanks a lot1
Cheers,
lek
-
Hi there,
I have been trying to install the kismet_3.0.1c_20031228_arm.ipk on my z6kl, but the install is not sucessful.
The message I am getting when installing is:
ipkg_install_file: ERROR unpacking data.tar.gz from kismet_3.0.1c_20031228_arm.ipk
Thoughts, anyone?
Cheers,
lek
-
corrupt file? file from OZ? Bad download?
-
the file is identical to my local copy. so should work fine. make sure you are enough space in your internal flash for unpacking.
-
the file is identical to my local copy. so should work fine. make sure you are enough space in your internal flash for unpacking.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=72309\"][{POST_SNAPBACK}][/a][/div]
Yep that did it.
What a memory hog! I had already remove a number of programs; boy talk about reducing what I have on my Zaurus. Kesmit works fine though.
Cheers,
lek
-
Anybody try the new kismet_2005.01.R1_arm.ipk from kismetwireless? I got it to install but when I try to run it it gives me a bus error...
-
Anybody try the new kismet_2005.01.R1_arm.ipk from kismetwireless? I got it to install but when I try to run it it gives me a bus error...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73919\"][{POST_SNAPBACK}][/a][/div]
No, I haven't. I was about to thought (thanks for the update). The 2004 version of kismet also gave a bus error, so there is something wrong there.
Craig...
-
there was a post on uclx compression and bus errors on the 3000 a day or two ago. maybe this is related? I think it said kismet was uclx compressed, but that the issue with bus errors is genrally a lack of decompression space. maybe permanently uncompress the bin?
-
there was a post on uclx compression and bus errors on the 3000 a day or two ago. maybe this is related? I think it said kismet was uclx compressed, but that the issue with bus errors is genrally a lack of decompression space. maybe permanently uncompress the bin?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78123\"][{POST_SNAPBACK}][/a][/div]
Thanks for the tip. That did the trick. I uncompressed the kismet binary (and kismet-ui) using uclx -d and now the lastest kismet runs quite well!
Thanks again,
Craig...
-
Thanks for the tip. That did the trick. I uncompressed the kismet binary (and kismet-ui) using uclx -d and now the lastest kismet runs quite well!
what did you use for the "source=" line?
It would seem that there's a number of changes from the 2003 version to the 2005 version of kismet, and "prism2, wlan0, prism2source" no longer is valid.
I'm not sure if it's correct or not, but I'm using
"wlanng,wlan0,prism2source" which seems to work.
-
Thanks for the tip. That did the trick. I uncompressed the kismet binary (and kismet-ui) using uclx -d and now the lastest kismet runs quite well!
what did you use for the "source=" line?
It would seem that there's a number of changes from the 2003 version to the 2005 version of kismet, and "prism2, wlan0, prism2source" no longer is valid.
I'm not sure if it's correct or not, but I'm using
"wlanng,wlan0,prism2source" which seems to work.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83434\"][{POST_SNAPBACK}][/a][/div]
Yes, there are changes, as I also discoverd that prism2 was no longer a valid choice. I am also using "wlanng, wlan0, sniffer" for my source. (the last field, sniffer, can be any string). With this setting Kismet successfully detects my AP at home, and it caught a couple of Network probe frames (from a nearby PC) at work.
I hope this helps,
Craig...
-
ok, that takes care of one aspect. I've been trying to do it all from the console, and haven't gotten very far yet.
The first part of the problem is to get the interface up. I've discovered that I can do a:
usbctl on 1
and that'll turn it on. I'm still trying to get it to go in "mode monitor" that I keep reading about. No luck so far.
-
ok, that takes care of one aspect. I've been trying to do it all from the console, and haven't gotten very far yet.
The first part of the problem is to get the interface up. I've discovered that I can do a:
usbctl on 1
and that'll turn it on. I'm still trying to get it to go in "mode monitor" that I keep reading about. No luck so far.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83615\"][{POST_SNAPBACK}][/a][/div]
Yes, doing it all from the console is a little trickier than the GUI, but it can still be done. BTW, I have a AdHoc network setup in my Zaurus (GUI) that I just fire up before running Kismet and that works pretty well. However if you want to do it all from the console you need to do a bit more typing:
usbctl on 1
sleep 1
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
ifconfig wlan0 1.1.1.1 up
Then start kismet. After you are done with Kismet, turning off the interface is a bit easier:
usbctl off 1
I have run Kismet this way, while accessing my Zaurus via ethernet (a CF card) and it works fine, just not as portable ;-)
I hope this helps,
Craig...
-
usbctl on 1
sleep 1
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
ifconfig wlan0 1.1.1.1 up
wow. I don't think I'd ever guess the rest of it! That seems to take care of the interface.
I noticed if I left in the "cisco,gps" part in logtypes that it'd complain about cisco things, so I took that out. It works great in the kismet GUI, just have to play more to get the kismet console part going. Something about "Error opening terminal: vt100" - which I think is because it's trying to open that kind of session in my bash shell. It's getting close!
Thanks for the hints thus far.
-
It works great in the kismet GUI, just have to play more to get the kismet console part going. Something about "Error opening terminal: vt100" - which I think is because it's trying to open that kind of session in my bash shell. It's getting close!
Thanks for the hints thus far.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83734\"][{POST_SNAPBACK}][/a][/div]
Ken,
Hmm, are you starting this as root? Here's a script I have that I use to start kismet, called, not surprizingly start_kismet (in /usr/local/bin)
#!/bin/sh
export TERMINFO=/usr/share/terminfo
export TERM=linux
kismet_hopper &
sleep 2
kismet
I have been using this script for previous versions of Kismet (which is where I got the kismet_hopper part). I just added the TERM info with this version. I am using qkonsole for my terminal program, and I'll warn you that the lines drawn on the terminal (to separate the areas of the UI) don't look like lines, but I hadn't bothered me enough to seek a solution.
I suppose if you wanted you could add all the bring the interface up, and then shut it down afterwards in this script as well, just never needed to (since I use the GUI to bring up my AdHoc interface config).
I hope this helps,
Craig...
-
Hmm, are you starting this as root? Here's a script I have that I use to start kismet, called, not surprizingly start_kismet (in /usr/local/bin)
[code]
#!/bin/sh
export TERMINFO=/usr/share/terminfo
export TERM=linux
ahhhhhh! It was complaining of having to use vt100. ok, that certainly explains it then. I had looked at the TERM and it was showing vt100, so I was thinking, what did I do wrong, it has the vt100 that it's complaining about, why is it complaing that it doesn't have that. I hadn't known that it did NOT want vt100.
That solves it! Much appreciate - kismet comes right up now.
-
ahhhhhh! It was complaining of having to use vt100. ok, that certainly explains it then. I had looked at the TERM and it was showing vt100, so I was thinking, what did I do wrong, it has the vt100 that it's complaining about, why is it complaing that it doesn't have that. I hadn't known that it did NOT want vt100.
That solves it! Much appreciate - kismet comes right up now.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83855\"][{POST_SNAPBACK}][/a][/div]
Ken,
Glad to hear you are having success. Actually if you _want_ to use vt100 you can, just change 'linux' to 'vt100' in my script. I think the real complain was that it didn't know where to get the terminfo. I changed mine to vt100 just to see if it would fix the "line drawing" problem, and it didn't. But Kismet works. I switched it back to 'linux' because I like the color output (vt100 was only b&w).
Let me know if you get sound working (I lack /usr/bin/play).
Happy sniffing,
Craig...
-
Glad to hear you are having success. Actually if you _want_ to use vt100 you can, just change 'linux' to 'vt100' in my script. I think the real complain was that it didn't know where to get the terminfo. I changed mine to vt100 just to see if it would fix the "line drawing" problem, and it didn't. But Kismet works. I switched it back to 'linux' because I like the color output (vt100 was only b&w).
Let me know if you get sound working (I lack /usr/bin/play).
Happy sniffing,
Craig...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83931\"][{POST_SNAPBACK}][/a][/div]
The line drawing problem can be easily fixed by changing the simpleborders option in kismet_ui.conf to true, i.e. simpleborders=true. As for sound, the kismet_3.0.1c-20031228_arm.ipk mentioned earlier in this thread has /usr/bin/play and the various required sound files. You should be able to extract those files from the ipk. Hope this helps.
Patrick
-
This is great! For the longest time, we were forced to use the 2003 version of kismet. Now the 6K can use the latest version of kismet, and all of the issues one by one are falling away.
I looked in the 2003 kismet, and indeed play, the sound files and a number of other things were there.
-
I looked in the 2003 kismet, and indeed play, the sound files and a number of other things were there.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83949\"][{POST_SNAPBACK}][/a][/div]
It took a while, but I finally found some time to tease apart the older Kismet ipk (v 3.01) and you are right the sound player (play and sox) and wav files are there.
I created a new tar file of just the files I wanted on my linux laptop, and untarred them onto the Zaurus, and now Kismet has sound again!
Thanks to all for your help in getting this very useful utility running again on the Zaurus!
Craig...
-
Just to let you guys know there is a newer version at the kismet web site. Oh, one quick question, how the hell do you turn off e-mail notifications??
-
Thanks all for testing out the latest version of Kismet. I'm still using the 2003 version.
Just wondering if the latest version still had the problem of Kismet (console) hanging after an hour or so. On my SL 6000s, Kismet tends to hang after an hour or so of scanning for networks. (I'm using Kismet to scan wifi networks and obtain an approximate idea of my location, so I need it running hours at a time).
Any ideas if Wellenrieter would be a better solution?
-A
-
Thanks all for testing out the latest version of Kismet. I'm still using the 2003 version.
Just wondering if the latest version still had the problem of Kismet (console) hanging after an hour or so. On my SL 6000s, Kismet tends to hang after an hour or so of scanning for networks. (I'm using Kismet to scan wifi networks and obtain an approximate idea of my location, so I need it running hours at a time).
Any ideas if Wellenrieter would be a better solution?
-A
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86207\"][{POST_SNAPBACK}][/a][/div]
If you read the change file in the latest Kismet, it sounds like this problem might be solved in the most recent release.
Craig...
-
Arrgh! I've spent the last few days seeking a reliable wireless network scanner which can run on the Zaurii for hours on end (I can arrange an external battery). I'm trying to build software which can approximate my location (kinda rough indoor GPS) based on wifi access points, similar to the IBM placelab project.
- Kismet 2003
Installs cleanly, but freezes up after an hour or so. It seemed like kismet_client would die after a while, so I wrote a shell script which invoked kismet_server for 100 seconds (after network configuration), kill it, and then sleep for 2 minutes. The system freezes up after a few tries (5-7).
- Kismet 2005
Installs cleanly, thanks to Craig and Ken's instructions. Same problem though, freezes up even faster (10-15 minutes). I looked at the changelog, but wasn't sure what is exactly causing the freezeups.
- Wellenreiter II
Installs cleanly, doesn't freeze up, but scanning slows down after 5-6 minutes, ultimately coming to a halt
- iwlist wlan0 scan
This should give me a list of available networks, which is basically what I care about. However, the iwlist scan command is apparently not implemented in the SL6000 iwtools package
For all these, I'm storing my log files on a 256 MB CF card, so it isn't running out of disk space. I've been using two SL6000s with the Sharp ROM, so its not about a particular Zaurus. I'm in an area where I can see atleast 15 access points and several networks. Kismet 2005 with the same configuration (except source=) works fine on my Knoppix laptop for hours on end.
AFAIK, there are only two possible causes. Either the Zaurus/Kismet combination is running out of memory, or the network card is put into a bad state. I'm not sure what to try next to diagnose and fix the problem. Probably something to check how much memory is being used.
If someone here has Kismet / Wellenreiter working for hours on end without dying out, I would love to know how.
Sorry for the long post, but I'm looking for any ideas.
Thanks,
-Anmol
-
For all these, I'm storing my log files on a 256 MB CF card, so it isn't running out of disk space.
probably running out of space. try this. do a terminal session and then type:
df -h
check how much space is on /home
-
probably running out of space. try this. do a terminal session and then type:
df -h
Alright, fixed it! I basically ended up doing the following,
- Followed Craig's instructions (usbctl, wlanctl-ng) after every run to shutdown the wireless card
- Used a C application instead of a bash script
The error seemed to be from the driver. I was running 'free' and 'df' in my bash script, and watching out for substantially low memory or disk space.
So now I have a Zaurus application(KismetManager) that continiously scans for 802.11 access points and bluetooth devices in proximity. It fires up every 60 seconds, scans, stores networks and BTids into a log file and goes back to sleep. Its going to be part of a larger application that maps these to a BuddyList and known locations, and also records my speech and motion when interesting events occur. If only I had a SL6000 expansion sleeve, I could also take images at the 'interesting' moments. Its been running for the last 5 hours straight ;-)
Cool, thanks a lot guys. All of this stuff is open source, and although we don't have a stable release yet, I can post links to our CVS.
-Anmol
-
Can anyone post the instructions in this thread? The ZUG site has been down for a few days since getting hacked, and the Kismet step-by-step has gone with it.
-
Can anyone post the instructions in this thread? The ZUG site has been down for a few days since getting hacked, and the Kismet step-by-step has gone with it.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=90084\")
[a href=\"https://www.oesf.org/index.php?title=How_to_run_Kismet_on_the_SL-6000L]https://www.oesf.org/index.php?title=How_to...on_the_SL-6000L[/url]
-
ok, that takes care of one aspect. I've been trying to do it all from the console, and haven't gotten very far yet.
The first part of the problem is to get the interface up. I've discovered that I can do a:
usbctl on 1
and that'll turn it on. I'm still trying to get it to go in "mode monitor" that I keep reading about. No luck so far.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83615\"][{POST_SNAPBACK}][/a][/div]
Yes, doing it all from the console is a little trickier than the GUI, but it can still be done. BTW, I have a AdHoc network setup in my Zaurus (GUI) that I just fire up before running Kismet and that works pretty well. However if you want to do it all from the console you need to do a bit more typing:
usbctl on 1
sleep 1
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
ifconfig wlan0 1.1.1.1 up
Then start kismet. After you are done with Kismet, turning off the interface is a bit easier:
usbctl off 1
I have run Kismet this way, while accessing my Zaurus via ethernet (a CF card) and it works fine, just not as portable ;-)
I hope this helps,
Craig...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83687\"][{POST_SNAPBACK}][/a][/div]
Hi Craig, et al
when i start that way all is fine until i start kismet. it reports the error:
could not connect to localhost:2501 and exits.
Any hints?
Peter
-
can somebody update the howto to reflect the latest kismet (2005?) on 6000
I downloaded Kismet_2005-01-R1-1 from cacko feed, however it complains about
error while loading shared libraries:; libpcap.so.1: cannot load shared object file: No such file or directory
I installed libpcap0_0.7.2_arm.ipk, but that does not contain libpcap.so.1
besides, Kismet from the cacko feed is not uclx compressed.
I guess I'm not using the correct kismet ipk. Somebody can point me to the right place to download?
-
can somebody update the howto to reflect the latest kismet (2005?) on 6000
I downloaded Kismet_2005-01-R1-1 from cacko feed, however it complains about
error while loading shared libraries:; libpcap.so.1: cannot load shared object file: No such file or directory
I installed libpcap0_0.7.2_arm.ipk, but that does not contain libpcap.so.1
besides, Kismet from the cacko feed is not uclx compressed.
I guess I'm not using the correct kismet ipk. Somebody can point me to the right place to download?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=93400\"][{POST_SNAPBACK}][/a][/div]
Hmm, I suppose you are right that the how-to needs updating. I am surprised that your kismet is complaining about libpcap.so.1, I am running kismet_2005.04.R1_arm.ipk and I am not getting those complaints.
I am pretty sure you can just create a symlink to /usr/lib/libpcap.so.0.7.2 and it should work. As long as kismet is not uclx compressed, you should be good to go.
I hope this helps,
Craig...
-
Hi Craig, et al
when i start that way all is fine until i start kismet. it reports the error:
could not connect to localhost:2501 and exits.
Any hints?
Peter
[div align=\"right\"][a href=\"index.php?act=findpost&pid=93327\"][{POST_SNAPBACK}][/a][/div]
Sorry to take so long to get back to you. Kismet runs as a client and server app. The server runs in background on localhost port 2500.
This error means that the kismet server didn't start up for some reason. If you are running this in a terminal, check further up in the messages to see why the server didn't start (did you edit the kistmet.conf file?).
Have you ever had kismet running on this Z? You will want a line that looks like this on your kismet.conf file:
source=wlanng,wlan0,sniff
I hope this helps,
Craig...
-
Hey quick question, with the newest version it says the terminal app doesn't support color. Since I know it does, how can I get it back. An all green kismet isn't near as cool to look at as one with red and blue.
-
Hmm, I suppose you are right that the how-to needs updating. I am surprised that your kismet is complaining about libpcap.so.1, I am running kismet_2005.04.R1_arm.ipk and I am not getting those complaints.
I am pretty sure you can just create a symlink to /usr/lib/libpcap.so.0.7.2 and it should work. As long as kismet is not uclx compressed, you should be good to go.
I hope this helps,
Craig...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=93702\"][{POST_SNAPBACK}][/a][/div]
Could you post kismet_2005.04.R1_arm.ipk? I googled but can't find anywhere on the web. TIA
-
Does anyone has a package with a working configuration file for the SL-6000L? I have not remotely had any luck with any of the posted instructions?
Older packages install and run but I cant seem to get the config files tweaked quite right. New Packages seg fault for some reason.
-
Does anyone has a package with a working configuration file for the SL-6000L? I have not remotely had any luck with any of the posted instructions?
Older packages install and run but I cant seem to get the config files tweaked quite right. New Packages seg fault for some reason.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=97958\")
Bane,
I have been meaning to update the how-to for some time. The basic problem is that the new binaries (packaged in the Kismet supplied ipk) are compressed with uclx. After installing kismet, you need to decrompress with the command uclx -d <kismet_binary>.
The rest of the instructions should be correct.
You can get the uclx binary from: [a href=\"http://inter.zon.free.fr/zaurus_index.html]http://inter.zon.free.fr/zaurus_index.html[/url]
I hope this helps,
Craig...
-
Anybody get a gps to work with kismet? I have the latest and greatest kismet working. I have qpegps working with my pharos cf gps. I can start the gps in the command line and cat the info from /dev/ttyS3. For some reason I can't get kismet to use the gps data. It keeps saying no signal. Any hints would be appreciated.
-
I just installed the pakage kismet3.0.1c and libpcap0, set kismet source to wlanng_avs,wlan0,xxxx doesn't matter last entrry since's only the server's name..
everything's working.
I'm having fun with it, but I have the "timeout" problem: after few seconds I've got to connect to a wireless lan (I created a common one).
Any hint to stay connected to my service and walk free ?
Thank you all!
-
I'm having fun with it, but I have the "timeout" problem: after few seconds I've got to connect to a wireless lan (I created a common one).
Any hint to stay connected to my service and walk free ?
Thank you all!
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=113738\")
Cippo,
You will want to set up a "dummy" wireless setting which uses ad-hoc mode. The how-to is helpful:
[a href=\"https://www.oesf.org/index.php?title=How_to_run_Kismet_on_the_SL-6000L]https://www.oesf.org/index.php?title=How_to...on_the_SL-6000L[/url]
I hope this helps,
Craig...
-
WOW! Thanks a lot Craig!
I forgot to set the Ad-hoc type... I just undrestood what it means!
now I can walk free without the timeout trouble!
Thanks!
-
I just updated the howto for the latest kismet setup
6000L Kismet How To (https://www.oesf.org/index.php?title=How_to_run_Kismet_on_the_SL-6000L)
-
I've written stuff about running kismet for OpenZaurus on the 6000:
http://openzaurus.berlios.de/HowTos/6000-Comms (http://openzaurus.berlios.de/HowTos/6000-Comms)
-
Hi.
I have been tryng to install kismet with
https://www.oesf.org/index.php?title=How_to...on_the_SL-6000L (https://www.oesf.org/index.php?title=How_to_run_Kismet_on_the_SL-6000L)
but i have a problem when i get to step 7 with the ulcx i cant use it.,i dont know why but my Z dont recognize ulcx.
So i think is better to try with another version without the ulcx.
Can anyone tell me what files do i need?.
I am not sure about what kismet version and if i need the same libcap and the libstdc ,kismet qt etc.
Thanks.
-
Hello.
I installed Kismet on OpenZaurus. Where is his dump?
I installed Kismet-Qt but can't start it:
-------------
# ipkg list |grep kismet
kismet - 2005-04-R1-r0 -
kismet-qt - 2.0.0 -
# kismet_qt
kismet_qt: symbol lookup error: kismet_qt: undefined symbol: _7QString.shared_null
#
---------------------------------------
What's wrong?
-
Hi.
I have been tryng to install kismet with
https://www.oesf.org/index.php?title=How_to...on_the_SL-6000L (https://www.oesf.org/index.php?title=How_to_run_Kismet_on_the_SL-6000L)
but i have a problem when i get to step 7 with the ulcx i cant use it.,i dont know why but my Z dont recognize ulcx.
So i think is better to try with another version without the ulcx.
Can anyone tell me what files do i need?.
I am not sure about what kismet version and if i need the same libcap and the libstdc ,kismet qt etc.
Thanks.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=128217\")
Hello poor,
if you are still hanging around here and struggling to have Kismet working, this is what I did on my stock ROM SL-6000:
- I went to the "Kismet How to" page here:
[a href=\"https://www.oesf.org/index.php?title=How_to_run_Kismet_on_the_SL-6000L]https://www.oesf.org/index.php?title=How_to...on_the_SL-6000L[/url]
- Downloaded with the SL-6000 the following packages and library:
* kismet_3.0.1c-20031228
* kismet-qt_2.0.0
* libpcap0_0.7.2
* libstdc++-3-libc6.1-2-2.10.0.so
- Followed very carefully the instructions on the "How to" (only difference being that I downloaded libstdc++-3-libc6.1-2-2.10.0.so into my CF card and then from there I copied it to /usr/lib using File Manager instead of the command line)
I had Kismet running in about 15 minutes, including the time needed to download the packages and the libraries. It worked at the first attempt, not issues whatsover.
A couple of tips:
- Don't forget to run Kismet as "root" tapping and holding its icon and checking the "Execute with root privilege"
- Since you are at it, uncheck the "Display with magnified screen" box. With all the real estate of the glorious SL-6000 display there is not need to magnify. Looks much nicer in hi-rez at full blown 640x480!!
Now, I do have a couple of questions for the more "senior" users of Kismet:
- Since this set-up with the old version is working, is there any major advantage in upgrading to the latest arm package? What are the key differences?
- Is there any way to tweak the .conf files to have KismetQt diplaying more information when set to "summary"? There is plenty of unused space on the line!
- Everything seems to be working fine selecting either "Sharp- prism2" or "Sharp3x-prism2" as "Scheme" in the "Config" tab. Is one of the two best for the SL-6000?
-
Now, I do have a couple of questions for the more "senior" users of Kismet:
- Since this set-up with the old version is working, is there any major advantage in upgrading to the latest arm package? What are the key differences?
- Everything seems to be working fine selecting either "Sharp- prism2" or "Sharp3x-prism2" as "Scheme" in the "Config" tab. Is one of the two best for the SL-6000?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=144911\")
the latest versions of kismet appear to detect more encryption schemes, such as WPA, and have other tweaks... I guess the best bet is to look at the release notes on [a href=\"http://www.kismetwireless.net/]http://www.kismetwireless.net/[/url]
as to prism2/prism3 differences in driver? I'll take a wild guess and say that maybe the prism3 driver will allow kismet to do better analysis of the wireless headers?