Re: Beacon v1.0-0 on FreeBSD
Ahh now that the beacons run, I have run into real problems it seems :)
I am tested some embedded-rp routers at the moment, just for background
info.
I have roughly this setup:
host A---router A----router B----host B
Host A is running the client and is the central server. Host B is also
running the client, reporting to host A. The reporting is also going
over IPv6 (I tried IPv4 and that didn't work either).
From tcpdump, I can see that host B is definitely connecting to host A
and sending things.
Now when I look at the output of host A, the Central Loss page alters
occasionally between being completely devoid of beacons, and listing
host A as a blind beacon - no mention of host B at all. Local Loss shows
host A fairly steadily. Infact, all the Central pages behave oddly and
the Local ones just show host A. If I go to Beacon Info, there are no
beacons listed there at all.
Anyone seen problems like this before? As I said, I have confirmed with
tcpdump that both machines are definitely talking via unicast at least,
so my understanding is they should show up in the matrix at this point?
Thanks,
Ras
Mitch Kutzko wrote:
> No problem at all, Ras -- Glad things are working for you now!
>
> (And it's not like I haven't done things like that, too... ;-) )
>
> Cheers!
>
> Mitch
>
> At 01:38 PM 9/17/2004 +0100, you wrote:
>
>>OK this is really rather embarassing. I had assumed IPv6 support would
>>be automagically enabled by configure - I hadn't realised I needed to
>>pass in --enable-ipv6. Now that I have, all appears to be working.
>>
>>Sorry to have wasted your time.
>>Ras
>>
>>
>>Rasmus Hansen wrote:
>>
>>
>>>Mitch Kutzko wrote:
>>>
>>>
>>>>Start with
>>>> ./beacon -d 4
>>>>
>>>>which is the highest debug level, and then watch the output. That may
>>>>help
>>>>some.
>>>
>>>
>>>I tried that, it unfortunately isn't terribly helpful:
>>>
>>>~/local/beacon/bin > ./beacon -d4
>>>Setting RTCP_PORT, PORT = 20002
>>>
>>>Getting configuration information from file "etc/beacon.conf".
>>>Opening session on default interface.
>>>Unable in initialize RTP session for this Beacon!
>>>
>>>
>>>It would appear that it is the beacon_init() call on beacon:3365 that is
>>>failing. I take it this is a function hidden somewhere in the
>>>accompanying C code? How would I go about finding out exactly what is
>>>going wrong?
>>>
>>>
>>>Ras
>>>
>>
>>
> --
> Mitch Kutzko | mitch@dast.nlanr.net | mitch@ncsa.uiuc.edu | 217-333-1199
> http://hobbes.ncsa.uiuc.edu/
>