← previous next →
Pages: [1]

Author Topic: Kismet 2005-04-r1broken On Oz 3.5.3?  (Read 6147 times)

mcdelroy

  • Newbie
  • *
  • Posts: 32
    • View Profile
Kismet 2005-04-r1broken On Oz 3.5.3?
« on: June 06, 2005, 07:55:15 pm »
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?
Logged

Pyrates

  • Full Member
  • ***
  • Posts: 198
    • View Profile
    • http://www.pipsfrank.de
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #1 on: June 07, 2005, 08:24:53 am »
You should probably describe the error you get in more detail...

Cheers
Philipp
Logged
\" ... and the Vogon will do things to you that you wish you\'d never been born, or, if you\'re a clearer minded thinker, that the Vogon had never been born.\"

mcdelroy

  • Newbie
  • *
  • Posts: 32
    • View Profile
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #2 on: June 07, 2005, 07:10:57 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.
Logged

Sniffer

  • Newbie
  • *
  • Posts: 34
    • View Profile
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #3 on: June 07, 2005, 07:22:52 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.
Logged

Pyrates

  • Full Member
  • ***
  • Posts: 198
    • View Profile
    • http://www.pipsfrank.de
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #4 on: June 08, 2005, 03:28:58 am »
Quote
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
Logged
\" ... and the Vogon will do things to you that you wish you\'d never been born, or, if you\'re a clearer minded thinker, that the Vogon had never been born.\"

cmpayc

  • Newbie
  • *
  • Posts: 27
    • View Profile
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #5 on: June 08, 2005, 04:41:03 am »
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
Logged

cmpayc

  • Newbie
  • *
  • Posts: 27
    • View Profile
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #6 on: June 08, 2005, 05:02:24 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
Logged

cvmiller

  • Full Member
  • ***
  • Posts: 242
    • View Profile
    • http://
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #7 on: June 08, 2005, 07:43:09 am »
Quote
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83274\"][{POST_SNAPBACK}][/a][/div]

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)?
Logged
SL-6000
ROM v1.12 (Sharp)
Belkin F8U1500 IR Keyboard
1 GB SD Card by SanDisk (ext2)

Pyrates

  • Full Member
  • ***
  • Posts: 198
    • View Profile
    • http://www.pipsfrank.de
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #8 on: June 08, 2005, 08:21:29 am »
Quote
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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83319\"][{POST_SNAPBACK}][/a][/div]

I think that's a question of the font your terminal is using. Change it, and see if the problem persists.

Cheers
Philipp
Logged
\" ... and the Vogon will do things to you that you wish you\'d never been born, or, if you\'re a clearer minded thinker, that the Vogon had never been born.\"

mcdelroy

  • Newbie
  • *
  • Posts: 32
    • View Profile
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #9 on: June 11, 2005, 10:14:07 am »
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.
Logged

PrOtOn

  • Jr. Member
  • **
  • Posts: 85
    • View Profile
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #10 on: June 12, 2005, 02:43:12 pm »
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?
Logged
Zaurus SL-5500
CF SanDisk 128MB(for flashing)
Symbol CF Wireless Card
512MB Kingston SD Card
OpenZaurus 3.5.3 Opie 1.2.0

lardman

  • Hero Member
  • *****
  • Posts: 4512
    • View Profile
    • http://people.bath.ac.uk/enpsgp/Zaurus/
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #11 on: June 12, 2005, 04:32:18 pm »
You not running as root by chance?


Si
Logged
C750 OZ3.5.4 (GPE, 2.6.x kernel)
SL5500 OZ3.5.4 (Opie)
Nokia 770
Serial GPS, WCF-12, Socket Ethernet & BT, Ratoc USB
WinXP, Mandriva

PrOtOn

  • Jr. Member
  • **
  • Posts: 85
    • View Profile
Kismet 2005-04-r1broken On Oz 3.5.3?
« Reply #12 on: June 12, 2005, 04:58:18 pm »
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.
Logged
Zaurus SL-5500
CF SanDisk 128MB(for flashing)
Symbol CF Wireless Card
512MB Kingston SD Card
OpenZaurus 3.5.3 Opie 1.2.0
Pages: [1]
← previous next →