[mythtv-users] Airplay audio only in v29

[Michael A Weber]

> On Jan 30, 2018, at 5:06 PM, Stephen Worthington <stephen_agent at jsw.gen.nz> wrote:
> 
> On Tue, 30 Jan 2018 11:41:41 -0600, you wrote:
> 
> 
>>>> I did just notice in the frontend log before I even attempted to airplay to it that there are several lines similar to my error lines:
>>>> 
>>>> Listening on TCP 0.0.0.0:5000
>>>> 2018-01-29 21:09:21.395688 I  AirPlay: Created airplay objects.
>>>> 2018-01-29 21:09:21.396331 I  Listening on TCP 0.0.0.0:5100
>>>> 2018-01-29 21:09:21.396736 E  Failed listening on TCP [::]:5000 - Error 10: Protocol type not supported
>>>> 
>>>> and now I?m thinking it?s something in the configuration of the frontend, OR there is a problem in the compilation of the frontend code (which I did not compile).
>>>> 
>>>> I?m wondering if anyone else can verify if airplay audio to a v29 frontend functions.  If so, that would confirm that it?s definitely a problem with my frontend build specifically, rather than with something in v29 code.
>>>> 
>>>> Mike
>>> 
>>> What does this command show:
>>> 
>>> netstat -lp | grep 5000
>>> 
>>> This is what I get on my combined frontend/backend box:
>>> 
>>> tcp        0      0 *:5000                  *:* LISTEN
>>> 17941/mythfrontend.
>>> tcp6       0      0 [::]:5000               [::]:* LISTEN
>>> 17941/mythfrontend.
>>> 
>>> From that error message, I would guess that you will not have the tcp6
>>> line, but may have the tcp line.
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>>> http://wiki.mythtv.org/Mailing_List_etiquette
>>> MythTV Forums: https://forum.mythtv.org
>> 
>> Stephen—
>> 
>> Exactly.  I do not have the IPv6 line.
>> 
>> tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN      7177/mythfrontend
>> 
>> 
>> I previously has an entry also for port 5100, but when I enabled audio-only airplay, listening on that port no longer occurs.  I attempted to telnet to port 5100 and the connection occurred and stayed open, and I could see the connection in the log.  However, if I try to telnet to port 5000, the connection closes rather quickly, and I get the same Binding to UDP error messages in the log.
>> 
>> If I somehow force mythfrontend to start in a “debug” mode, will I have more information in the log than I do now?  I’d like to see what is getting instantiated when it is starting up and what is happening when an airplay device attempts to connect to mythfrontend.
>> 
>> I’m now getting the feeling that this is not working for others in v29 as well, but I’m the first to discover it.
>> 
>> Thanks for your help, btw
> 
>> 
>> Mike
> 
> Do you have IPv6 working on the frontend box?  And on your network? If
> not, it might be an idea to try running with IPv6 disabled at the
> operating system level.  The thought being that the error creating the
> tcp6 socket might be inhibiting code after that from working with the
> tcp socket.  But if there is no IPv6, that may prevent the error.
> 
> Here is how to disable IPv6 if you are running Ubuntu:
> 
> https://www.linuxbabe.com/ubuntu/disable-ipv6-on-ubuntu
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

Stephen—

I do not have IPv6 running in my network, and it’s also not running on the frontend machine.  In fact, the path specified in that URL above to cat (/proc/sys/net/ipv6) doesn’t even exist on my frontend.  So, it’s not there at all.

Maybe I’ll have to take another machine and throw a mythbuntu build on it and see if I can get AirTunes to work, or if I get the same issue.  My bet is on the latter, unfortunately.

…unless someone else has v29 and uses AirTunes and find that it works.  ;)

Mike