[mythtv-users] .25, bonjour, and airplay

[Raymond Wagner]

On 4/16/2012 12:20, Gabe Rubin wrote:
> On Mon, Apr 16, 2012 at 9:15 AM, Raymond Wagner<raymond at wagnerrp.com>  wrote:
>> On 4/16/2012 12:11, Gabe Rubin wrote:
>>> On Mon, Apr 16, 2012 at 5:37 AM, Jean-Yves Avenard<jyavenard at gmail.com>
>>>   wrote:
>>>> On 16 April 2012 20:30, O&M Ugarcina<mo.ucina at gmail.com>    wrote:
>>>>
>>>>> I tried running my frontend with airplay today and got no streaming , my
>>>>> frontend log is as follows :
>>>>>
>>>>> 2012-04-16 20:23:34.025243 I [14169/14186] RAOPDevice serverpool.cpp:306
>>>>> (listen) - Listening on TCP 127.0.0.1:5000
>>>>> 2012-04-16 20:23:34.025321 I [14169/14186] RAOPDevice serverpool.cpp:306
>>>>> (listen) - Listening on TCP [0:0:0:0:0:0:0:1]:5000
>>>>> 2012-04-16 20:23:34.025330 I [14169/14186] RAOPDevice
>>>>> mythraopdevice.cpp:137
>>>>> (Start) - RAOP Device: Listening for connections on port 5000
>>>>>
>>>>> I have a combined BEFE machine , all my connectivity between the two was
>>>>> via
>>>>> loopback interface . What config do we need to set to get the
>>>>> appropriate
>>>>> address to be advertised ?
>>>> First of all. Is your backend/frontend have a local network card
>>>> configured ? (e.g. not just localhost)
>>>>
>>>> Set your backend to listen to the local address (not localhost).
>>>>
>>>> Mythfrontend will then start to listen to the local address too
>>> Can you explain this a little more because I think I am in the same
>>>
>>> situation.  My router assigns my combined FE/BE the address of
>>> 128.1.1.101.  All entries in the database are to localhost.  I know
>>> enough to know that this is probably not how things should be set up
>>> as I believe I am getting the same output as Mo in the console (not in
>>> front of the machine right now).  I am hoping its not too complicated
>>> a fix.
>> If the host the frontend is running on is configured with an IP address, it
>> will listen only on that IP address and localhost.  If the IP address is not
>> configured, it will listen on any private network address currently defined
>> on the system.  A recent commit by Jean-Yves altered the AirPlay servers to
>> always listen on all available addresses, rather than only those the user
>> specified for that host, as a quick work-around to this issue.
>>
> I guess I am really needing basic steps here.  How exaclty do I
> configure my frontend with an IP address?

The same way you configure the backend with an IP address.  However, as 
mentioned, this only serves to limit which addresses the frontend will 
listen on.  Your specific case is only a problem because you are 
limiting the frontend to only listening on localhost, by telling the 
backend on the same host to only listen there.  Also as mentioned, this 
is no longer an issue due to a recent commit to master, which should get 
backported to 0.25 in the near term.