Am Freitag, den 12.12.2008, 23:07 +0000 schrieb Daniel T Chen:
> Is this symptom still reproducible in 8.10 or 9.04?
>
> ** Changed in: kismet (Ubuntu)
> Status: New => Incomplete
The problem was, that the kismet_server binds per default to
"127.0.0.1". On the other hand, kismet_client connects to
"localhost" (/etc/kismet/kismet.conf: "host=localhost:2501"), which for
some reason wasn't set to "127.0.0.1" in my /etc/hosts.
I don't think, that this is an Bug of the Ubuntu/Debian package. (But
there may be one in Kismet: it shouldn't segfault even if some hostname
doesn't resolve ;-)
Sincerely
David
--
kismet_client cannot connect to kismet_server
https://bugs.launchpad.net/bugs/216920
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
