- I've been playing with this lately, with some success.
- First, "kismet" on the command line just fails miserably. Always has on Hiro. But I see it's running "kismet.sh".
- Second, "kismet.sh" fails miserably. Don't remember the exact error, but it's using some weirdo qcop thing to spawn "k.sh" in its own command shell. Wierd.
- Third, "k.sh" does what speculatrix says. Won't run kismet_client. I'm interested in running kismet_qt, anyway, 'cause I'm not familiar with either one of them. (snicker)
- Fourth, Kismet QT always runs, but it never does start the server, so it's well night useless. It's always done that on Hiro, too. I've done some of the wierdo WiFi config things that are floating around here, but they're spotty at best.
- So, says I, I'll play. I copy "k.sh" to "k_qt.sh" and remove the client launch part, so it just runs the server and pauses the script. Then I launch Kismet QT ... bingo! Works perfectly first time.
- Then I think I'll just tweak "k_qt.sh" and have it launch kismet_qt instead of kismet_client. Then I can point the icon to that and all will be well in GUI Kismet Land.
- Not so fast. For reasons I haven't determined, it will never launch the server until I first connect to my WiFi, then disconnect. After that, "k_qt.sh" has to be called twice ... first time it fails to launch the server, and the second time it works ... every single time. Wierdness.
- I'm playing with cardctl to see if there's isn't something I can do to put things into a consistent state each time the script runs, so it'll launch reliably. But I think this deal with a script is more promising than anything else I've done with Hiro. It's been a pretty strange road, so far...
