kismet problem - 1/2 solved, new version available

[whit]

Trying to get kismet running on an 860 with an SMC2642w.

This source line almost works:

source=hostap,eth0,hostapsource

but kismet fails with:

\"FATAL: Failed to set private ioctl \'monitor\': bad address\"

I\'ve googled and searched on Kismet\'s site, but can\'t find what that\'s about. Anyone seen it?

[whit]

Looks like the version of hostap with pdaXrom somehow doesn\'t find the right monitor address.

Code: [Select]

# iwpriv

lo        no private ioctls.



eth0      Available private ioctl :

          force_reset      (8BE0) : set   0       & get   0      

          card_reset       (8BE1) : set   0       & get   0      

          set_port3        (8BE2) : set   1 int   & get   0      

          get_port3        (8BE3) : set   0       & get   1 int  

          set_preamble     (8BE4) : set   1 int   & get   0      

          get_preamble     (8BE5) : set   0       & get   1 int  

          set_ibssport     (8BE6) : set   1 int   & get   0      

          get_ibssport     (8BE7) : set   0       & get   1 int  

          monitor          (8BE8) : set   2 int   & get   0      

          dump_recs        (8BFF) : set   0       & get   0      

Anyone know what I need to do to have a version of hostap that will correctly connect with the monitor ioctl at 8BE8 on this card?

[whit]

Success!

Necessary steps in this case:

1. Set the source line in kismet.conf to orinoco (not listed as a working driver for this SMC card on the kismet site, but wtf)
2. cd to the directory of the user kismet has been configured to run as (/home/kismetuser or whoever)
3. # export TERM=xterm-color
4. # kismet

Ahhhh....

[whit]

Although (from the kismetwireless.net board):

You\'re going to run into other issues using the orinoco driver, it\'s not timed for the prism2 firmware and it\'s going to cause problems eventually.

If you edit the config file you can set an absolute path for where kismet logs to, it\'s in the troubleshooting and config sections of the readme.

The rxvt thing sounds like aterm is confused and ncurses equally so, all the termcap stuff is inside ncurses so something sounds broken in your distro.

-m


] Found by trial and error that the orinoco source works (which is not listed for this card here on kismetwireless - just hostap and wlan-ng). Then found that I had to cd to the directory of the kismet user to start it (otherwise it couldn\'t write to its dump file), and to \"export TERM=xterm-color\" before starting it (otherwise there\'s an error message about rxvt - never mind that I\'m running it in aterm).
]
] Whit

Will the next pdaXrom have this stuff straightened out?  :wink:

[whit]

Looks like we\'ve got an \"ancient\" version of kismet on the feed. See http://kismetwireless.net/Forum/General/Me...7570747.4004581

So it looks like the current version should work on Zauri. I\'ll try to install that. It lives at http://kismetwireless.net/download.shtml down the page.

Confirmed, it works! The kismet.conf file goes to /usr/local/etc rather than /usr/etc. Does this need to be changed to fit with pdaXrom standards, or should the current ipk just go up on the unstable feed as it is?