 Kismet 2005-04-r1broken On Oz 3.5.3? |
  |
 Jun 6 2005, 03:55 PM
Post
#1
|
|
|
Group: Members Posts: 32 Joined: 30-May 05 Member No.: 7,236  |
I am getting error opening UI linux. I've installed ncurses-terminfo. I've tried the export term and terminfo fix. Is this a known issue? What do I try next?
|
 |
 
|
|
Jun 7 2005, 04:24 AM
Post
#2
|
|
 Group: Members Posts: 198 Joined: 17-January 04 Member No.: 1,475 |
You should probably describe the error you get in more detail...
Cheers Philipp |
|
|
|
|
Jun 7 2005, 03:10 PM
Post
#3
|
|
|
Group: Members Posts: 32 Joined: 30-May 05 Member No.: 7,236 |
Kismet 2005-04-r1broken under OZ 3.5.3 when starting kismet from a command prompt I recieve "error opening terminal linux". The it says killing server. I installed ncurses and ncurses-terminfo from the 3.5.3 feed. I added the following lines to the kismet file, "export TERMINFO=/usr/share/terminfo" and "export TERM=linux. I also issued the export TERMINFO /usr/share/terminfo command and added export TERMINFO=/usr/share/terminfo to /etc/profile. My wlan card is an Ambicom supported by Kismet. Thanks for your help.
|
|
|
|
|
Jun 7 2005, 03:22 PM
Post
#4
|
|
 Group: Members Posts: 34 Joined: 17-September 04 Member No.: 4,618 |
Kismet works fine on my collie, did you add the appropriate 'source' to your kismet.conf file?
Maybe you should uninstall everything and follow Iron Geek's method which i've had no problems with. |
|
|
|
|
Jun 7 2005, 11:28 PM
Post
#5
|
|
|
Group: Members Posts: 198 Joined: 17-January 04 Member No.: 1,475 |
QUOTE(mcdelroy @ Jun 7 2005, 03:10 PM) Kismet 2005-04-r1broken under OZ 3.5.3 when starting kismet from a command prompt I recieve "error opening terminal linux". The it says killing server. I installed ncurses and ncurses-terminfo from the 3.5.3 feed. I added the following lines to the kismet file, "export TERMINFO=/usr/share/terminfo" and "export TERM=linux. I also issued the export TERMINFO /usr/share/terminfo command and added export TERMINFO=/usr/share/terminfo to /etc/profile. My wlan card is an Ambicom supported by Kismet. Thanks for your help. Sorry to tell you, but I can't help, never used WLAN or Kismet myself. Just wanted to point out that you're more likely to get help if you include more details. Good luck! Cheers Philipp |
|
|
|
|
Jun 8 2005, 12:41 AM
Post
#6
|
|
|
Group: Members Posts: 27 Joined: 10-January 05 Member No.: 6,173 |
just for info,
this version of kismet works fine on cacko 1.22a for me, just set TERMINFO environment variable, edit kismet.conf to set the source, start kismet and have fun. i could not bring the previous version of kismet to run in my configuration, but this one works great. best regards cmpayc |
|
|
|
|
Jun 8 2005, 01:02 AM
Post
#7
|
|
|
Group: Members Posts: 27 Joined: 10-January 05 Member No.: 6,173 |
but,
if i set export TERM=linux, kismet-UI uses colors, but does not display the window-borders properly (uses somethig like ? for border-chars). Any idea? best regards cmpayc |
|
|
|
|
Jun 8 2005, 03:43 AM
Post
#8
|
|
|
Group: Members Posts: 242 Joined: 31-March 04 Member No.: 2,592 |
QUOTE(Sniffer @ Jun 7 2005, 03:22 PM) Kismet works fine on my collie, did you add the appropriate 'source' to your kismet.conf file? Maybe you should uninstall everything and follow Iron Geek's method which i've had no problems with.  Thanks for the tip. Although I am off topic here (I am running stock Sharp ROM), uncompressing the binaries (with uclx -d) got rid of my BUS errors. Then it was only a matter of following the instructions from irongeek. So I am happy to say that I now have the most recent version of Kismet (2005-04-R1) running on my SL-6000! Thanks to all, Craig... PS anyone have a cli based wav file player (i.e. /usr/bin/play)? |
|
|
|
|
Jun 8 2005, 04:21 AM
Post
#9
|
|
|
Group: Members Posts: 198 Joined: 17-January 04 Member No.: 1,475 |
QUOTE(cmpayc @ Jun 8 2005, 01:02 AM) but, if i set export TERM=linux, kismet-UI uses colors, but does not display the window-borders properly (uses somethig like ? for border-chars). Any idea? best regards cmpayc I think that's a question of the font your terminal is using. Change it, and see if the problem persists. Cheers Philipp |
|
|
|
|
Jun 11 2005, 06:14 AM
Post
#10
|
|
|
Group: Members Posts: 32 Joined: 30-May 05 Member No.: 7,236 |
Solved:
I used the instructions at http://www.irongeek.com/i.php?submenu=zaur...s/generalosinfo to successfully get kismet up on oz 3.5.3. Appartently it only works if you install all ncurses and kismet files to ram rather then an sd card with ipkg-links. Thanks for your help. I just needed to know that it was possible to get it working with 3.5.3. |
|
|
|
|
Jun 12 2005, 10:43 AM
Post
#11
|
|
|
Group: Members Posts: 85 Joined: 5-May 05 Member No.: 7,080 |
I installed Kismet and followed Irongeed tips. However everytime I run Kismet on console I get the error: "Permission Denied".
Any one know what is going on? |
|
|
|
|
Jun 12 2005, 12:32 PM
Post
#12
|
|
|
Group: Members Posts: 4,515 Joined: 25-October 03 From: Bath, UK Member No.: 464 |
You not running as root by chance?
Si |
|
|
|
|
Jun 12 2005, 12:58 PM
Post
#13
|
|
|
Group: Members Posts: 85 Joined: 5-May 05 Member No.: 7,080 |
I am.
I was trying to run kismet using ssh (putty) from my desktop. So I gotta be root to be running ssh. Also, I tried "su" and it come back with same output "root". I even tried run from console(my zaurus) and got the same message. On Kismet script where says: QUOTE user: enter_user_here Do I have to change anything in there? I didn't change it because I didn't see in anywhere something saying to change it. |
|
|
|
|
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:
|
Lo-Fi Version | Time is now: 19th June 2013 - 07:04 AM |