Re: kismet 3.0.1c and openbsd 3.3

[Vazquez Javier <j.vazquez@nzz.ch>]

Vazquez Javier wrote:

>Looks as if "Failed to set up UI server: TcpServer bind() failed:
Permission
>denied" is the main problem here. What kind of permissions do I need to let
>kismet "bind" itself correctly?
>
I've no idea what kismet is, but:
1) you should no need any permission if you're root.

i know...that's what i was thinking too. :)

2) I would check that there is no other daemon bound on the same port
   when you start kismet (netstat -na | grep tcp  | grep LISTEN)

nope...nothing else listening on that port

anyway...i just restarted my machine and tried again. now i get a completely
different error-message:

kismet-output:

<snip>
sh: prism2ctl: not found
FATAL: capture child 23748 packet buffer empty and flagged as diseased,
exiting
</snip>

kismet_server-output (if i only start kismet_server):

<snip>
FATAL: pcapsource failed executing shell command: prism2ctl wi0 -f 1
>/dev/null
FATAL: pcapsource failed executing shell command: prism2ctl wi0 -f 1
>/dev/null
FATAL: capture child 23748 packet buffer empty and flagged as diseased,
exiting
</snip>

i checked "/root/.profile" and "/usr/local/sbin" is part of PATH
('prism2ctl' is in "/usr/local/sbin"). but a 'which prism2ctl' in sh or in
bash shows me: "prism2ctl: Command not found."

'ls -l /usr/local/sbin/prism2ctl' gives me:

-r-xr-xr-x	1 root wheel 12288 Aut 31 20:58 /usr/local/sbin/prism2ctl

...any idea?

cheers
javier