|
From: Michael G. <mg...@ee...> - 2002-10-10 15:34:45
|
Hiya Richard. Which version of Peep are you trying? If you're
currently using the 0.5.x CVS, I suggest you hold off because we're
still working on the client libraries (and I think the current CVS is
broken and will be fixed this weekend). 0.4.x definitely works and I
suggest starting there for now.
There are two tools which should help you play around with your
installation: Try using peck and keytest. I particularly like keytest
because it allows me to interact with the server directly. Be aware
that you'll only start hearing sound once you're clients begin sending
events.
If you need more help debugging, I suggest doing a:
./configure --enable-debug=4
and then run your clients with a --debug=9. That'll show you what
both client and server think their doing and help get you up and
running. Please let us know if that doesn't help get you up and
running.
As for the traffic_monitor client, that particular client was contributed
by a user (Pedram). But I think Collin Starkweather might be able to best
help you out on this one.
Regards,
-- Mike
On Wed, Oct 09 @ 14:15, Richard Rowell wrote:
> I pulled down peep (and the sound files) and did the configure/make/make
> install bit on peep and it seems to have went OK. When I nmap localhost i
> see that the UDP port 2001 is now open for business, and peepd indicates
> that it is loading sounds as it starts.
>
> I also pulled down the traffic_monitor client and modified peep.conf per
> it's instructions. I run it and it does after a bit (30 seconds or more)
> with a message like this:
> [Wed Oct 9 14:10:53 2002] 192.168.1.131.58666 > tc -
> Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at
> /usr/lib/perl/5.8.0/Socket.pm line 201, <TCPDUMP> line 1.
>
> I never hear a peep out of my speakers in any case. I'm not sure if I
> have one problem or more. Here come the questions:
>
> Should peepd produce sound as soon as I start it?
>
> (if not)Is there any way to manually make it produce a sound just so I
> know that it is working?
>
> Any ideas on why traffic_monitor is dying (yes I have tcpdump installed)?
--
Michael Gilfix
mg...@ee...
For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html
|