Discovery Proxy Setup Problem with Mojave and HomePod #2
Comments
|
A couple of things to try. First of all, there is an issue with using “my_name discoveryproxy.home.arpa.” which is partly fixed on the master, but which hasn’t been pulled into release yet because of another change that I foolishly made at the same time that I’m not quite happy with and haven’t fixed yet.
Can you try deleting the my_name line from the config file and see if the problem goes away? This isn’t the right thing to do in all circumstances, but I think it will work in your case.
Also, are you seeing any output in the terminal window where you’re running dnssd-proxy?
Thanks, both for trying this out and for the clear and detailed bug report!
… On Jun 12, 2019, at 12:45 PM, Chris ***@***.***> wrote:
Hi,
First and foremost THANK YOU for writing the Discovery Proxy! I was waiting for a solution for different subnets for years and I couldn't believe what I was hearing in the Advances in Networking, Part 2 WWDC 2019 session. Great Work!
Unfortunately the DNS-SD Discovery Proxy does not work in my current setup.
Main router has a local network of 10.0.0.0/24
2 HomePods are connected to the 10.0.0.0/24 network
WiFi access point connected via ethernet to the 10.0.0.0/24 network creates a WiFi network 192.168.1.0/24
Mac mini 2018 with macOS Mojave 10.14.5 running the Discovery Proxy with IP 10.0.0.21
iPad running iOS 13 beta 1 is connected to the 192.168.1.0/24 network
iPad has manual DNS-Server 10.0.0.21
iPad has manual Search Domain service.home.arpa
Config of the Discovery Proxy is the following:
interface en0 service.home.arpa.
my-name discoveryproxy.home.arpa.
my-ipv4-addr 10.0.0.21
udp-port 53
tcp-port 53
tls-port 853
In the dnssd-proxy logs I can clearly see that the iPad successfully uses the Mac mini as it's DNS server. But I still can't discover the HomePods with the iPad.
Was anyone so far able to successfully setup a Discovery Proxy? Did I make any mistake? Does it not work for my setup?
Thank you for your help!
P.S: I tried to start a discussion on the Apple Developer Forums as recommended in the Readme, but my discussion is stuck with A moderator needs to approve it before it can be posted. for a quite a some time now.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#2?email_source=notifications&email_token=AA5USAJXVRJHODKL6HK4LT3P2ERZVA5CNFSM4HXLCGSKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GZDTQXQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA5USAN5325BNQIJT62RKW3P2ERZVANCNFSM4HXLCGSA>.
|
|
Hi @Abhayakara, Thank you very much for your help. I deleted the When I run afterwards When I then search for AirPlay players in the music widget of the control center, I unfortunately still don't see the HomePods. Also I do not see any logs appearing in the terminal window while I search for AirPlay devices. After some time I see the following logs, which I think are normal DNS request made from the iPad: I hope these logs help. |
|
If I run the iOS app Discovery on the iPad, I can see that the domain And indeed if I add |
|
On Jun 12, 2019, at 2:35 PM, Chris ***@***.***> wrote:
If I run the iOS app Discovery on the iPad, I can see that the domain service.home.arpa includes all the services of the other subnet. So the iPad is generally seeing them, but it is ignoring it for the AirPlay destination.
Oh, that’s interesting. This may be airplay-specific. I will see if I can reproduce this here using my Apple TV. I might not get back to you on this today, but I definitely will see if I can reproduce it and get back to you soon!
|
|
I also have an Apple TV 4 (HD) in the 10.0.0.0/24 subdomain, which does not show up in the Screen Monitoring nor Music widget either. It does, however, appear in the bonjour Discovery app. So you should be able to reproduce the issue with an Apple TV as well. In the meantime I tried an AirPrint printer and it works! With the Discovery Proxy running I can print from the 192.168.1.0/24 subnet on the printer connected to the 10.0.0.0/24 subnet. |
|
On Jun 12, 2019, at 3:50 PM, Chris ***@***.***> wrote:
In the meantime I tried an AirPlay printer and it works! With the Discovery Proxy running I can print from the 192.168.1.0/24 subnet on the printer connected to the 10.0.0.0/24 subnet.
Sweet! I would say we are on to something. :)
|
|
I know that my network setup should allow the iPad to play on the HomePod via AirPlay once we figure the Discovery Proxy out, because at the moment I am running a custom app/daemon which use To test this Please let me know if you need more information for debugging. I am happy to help. |
|
Unfortunately I have frustrating news for you. For policy reasons Apple requires AirPlay clients and servers to be within the same broadcast domain, and prohibits the use of unicast for discovering AirPlay services. I have added a note about this to the README file. |
|
That is really unfortunate. Thank you for sharing that information with me though. I hope that policy will be changed at some point. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
First and foremost THANK YOU for writing the Discovery Proxy! I was waiting for a solution for different subnets for years and I couldn't believe what I was hearing in the Advances in Networking, Part 2 WWDC 2019 session. Great Work!
Unfortunately the DNS-SD Discovery Proxy does not work in my current setup.
In the
dnssd-proxylogs I can clearly see that the iPad successfully uses the Mac mini as it's DNS server. But I still can't discover the HomePods with the iPad.Was anyone so far able to successfully setup a Discovery Proxy? Did I make any mistake? Does it not work for my setup?
Thank you for your help!
P.S: I tried to start a discussion on the Apple Developer Forums as recommended in the Readme, but my discussion is stuck with
A moderator needs to approve it before it can be posted.for a quite some time now.The text was updated successfully, but these errors were encountered: