<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 29, 2018, at 10:16 PM, Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz" class="">stephen_agent@jsw.gen.nz</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Mon, 29 Jan 2018 21:25:16 -0600, you wrote:<br class=""><br class=""><blockquote type="cite" class=""><br class=""><blockquote type="cite" class="">On Jan 29, 2018, at 6:34 PM, Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz" class="">stephen_agent@jsw.gen.nz</a>> wrote:<br class=""><br class="">On Mon, 29 Jan 2018 11:18:59 -0600, you wrote:<br class=""><br class=""><br class=""><blockquote type="cite" class="">Stephen?<br class=""><br class="">Hmmm. Does this setting also tell Mythfrontend how to behave? I have a separate frontend from the backend, and my case is for the frontend machine. I don?t run a frontend on the backend machine.<br class=""><br class="">Best,<br class="">Mike<br class=""></blockquote><br class="">Good question - I do not know the answer. If they both use the same<br class="">code to bind IP addresses, then that setting would probably apply. It<br class="">is at mythtv-setup > General > Host Address Backend Setup > Allow<br class="">Connections from all Subnets. Given its placement in the settings,<br class="">that would suggest that it only applies to backends, but the only way<br class="">to know for sure is to try it.<br class="">_______________________________________________<br class="">mythtv-users mailing list<br class=""><a href="mailto:mythtv-users@mythtv.org" class="">mythtv-users@mythtv.org</a><br class="">http://lists.mythtv.org/mailman/listinfo/mythtv-users<br class="">http://wiki.mythtv.org/Mailing_List_etiquette<br class="">MythTV Forums: https://forum.mythtv.org<br class=""></blockquote><br class="">Well, we can chart that one up to not being the problem. I suspected it wouldnt by the nature of the setting label as well as the helper text, which reads Allow this backend to receive connections from any IP address on the internet. NOT recommended for most users. Use this only if you have secure IPv4 and IPv6 firewalls. That tells me that built into mythbackend is the restriction to not accept connections from devices on any subnet except the x.y.z.0 subnet on which the backend resides. Also, all my frontend machines are on the same subnet as the backend and any machine trying to airplay to a frontend, so thats definitely not it.<br class=""><br class="">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:<br class=""><br class="">Listening on TCP 0.0.0.0:5000<br class="">2018-01-29 21:09:21.395688 I AirPlay: Created airplay objects.<br class="">2018-01-29 21:09:21.396331 I Listening on TCP 0.0.0.0:5100<br class="">2018-01-29 21:09:21.396736 E Failed listening on TCP [::]:5000 - Error 10: Protocol type not supported<br class=""><br class="">and now Im thinking its something in the configuration of the frontend, OR there is a problem in the compilation of the frontend code (which I did not compile).<br class=""><br class="">Im wondering if anyone else can verify if airplay audio to a v29 frontend functions. If so, that would confirm that its definitely a problem with my frontend build specifically, rather than with something in v29 code.<br class=""><br class="">Mike<br class=""></blockquote><br class="">What does this command show:<br class=""><br class="">netstat -lp | grep 5000<br class=""><br class="">This is what I get on my combined frontend/backend box:<br class=""><br class="">tcp 0 0 *:5000 *:* LISTEN<br class="">17941/mythfrontend.<br class="">tcp6 0 0 [::]:5000 [::]:* LISTEN<br class="">17941/mythfrontend.<br class=""><br class="">From that error message, I would guess that you will not have the tcp6<br class="">line, but may have the tcp line.<br class="">_______________________________________________<br class="">mythtv-users mailing list<br class=""><a href="mailto:mythtv-users@mythtv.org" class="">mythtv-users@mythtv.org</a><br class="">http://lists.mythtv.org/mailman/listinfo/mythtv-users<br class="">http://wiki.mythtv.org/Mailing_List_etiquette<br class="">MythTV Forums: https://forum.mythtv.org<br class=""></div></div></blockquote></div><br class=""><div class="">Stephen—</div><div class=""><br class=""></div><div class="">Exactly. I do not have the IPv6 line.</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 7177/mythfrontend</span></div></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">Thanks for your help, btw…</div><div class=""><br class=""></div><div class="">Mike</div><div class=""><br class=""></div></body></html>