-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Connect to "device" #246
Comments
Can you describe your network topology? |
@philippe44 the server is connected via Ethernet and the google home devices are connected via WiFi. Is that what you mean? |
and a bit more. What kind of router and WiFi is that? Are they on the same net or do you have subnets? Some WiFi mesh are doing IGMP snooping which seems to cause problem. If there is nothing else in the log, then it seems to indicate that either the broadcasted address of the virtual AirPlay devices is wrong or there is a firewall that prevents aircast to open a socket to listen to RTSP session requests |
Netgear R6700v3 is the router. I think all the google homes are connected to the 5g band. No mesh system, just the router. I have the 2.4ghz and 5ghz networks but no subnets beyond that. I tried running the script on my Macbook, that is connected to the 5g wifi, and this is as far the script gets
|
So its really looks like something in the router between network segments. I can't tell exactly what, look at multicast and IGMP options for R6700. BTW, it's not a script, it's a C application fully compiled :-) |
There is a |
Yes, certainly as IGMP proxying is creating issue AFAIK |
Disabling that did not seem to make a difference. Also moved one of the google homes to the 2.4ghz wifi with no change. |
So I'm running out of ideas at that point. Would need to run wireshark traces of what's happening on the machine trying to AirPlay from. If your macbook sees the virtual devices, try to capture frames between it and the Ubuntu that runs aircast. |
Would it make sense to try a different firmware on my router? Like DD-WRT or Tomato? Not sure if those would give me more flexibility |
It might - I'm sorry it's difficult to help at that point because it's obviously one of these corner cases that involves WiFi/Network config |
So I installed dd wrt on my router. Messed with some multi cast and IGMP settings. It now works when I run the aircast from my windows desktop (did not before), but I still get the same experience from the ubuntu server. |
I really don't have a lot of network knowledge. I have attached a wireshark capture. I started the capture at the point of me trying to connect to one of the google home devices from itunes on my mac and stopped the capture after itunes gave me a failed to connect dialog. Also, I did filter on a source and destination IP to try and hide some noise, I think i chose the right IPs. I had Airconnect running on the ubuntu server at the time. Is this of any help in diagnosing the problem? Thanks |
@philippe44 any other thoughts on this after the wireshark capture? Would it help if i did the same capture while running airconnect on my windows machine, where it seems to work? |
I don't think the capture contains the exchange between the two. Can you restrict packet capture between where AirConnect runs and the Controller (itunes). If they are both on your mac, you probably need to add a driver that let you capture loopback traffic. I really don't know much about MacOS unfortunately |
So I’m only using OS X to run wire shark and iTunes to try and connect to the chromecast device. Air connect is running on Ubuntu or windows. I’ll try to get a new capture |
ok, so can you filter just the host to host between Ubuntu and the OSX machines? |
i'm experiencing the same behavior as @brentluna. aircast-osx-multi running on OSX 10.14.6 john@zuzu Downloads $ ./aircast-osx-multi -d all=info
[14:10:53.802622] main:945 Starting aircast version: v0.2.25.0 (May 3 2020 @ 17:41:47)
[14:10:53.803476] main:953 no config file, using defaults
[14:10:53.803648] Start:712 Binding to 192.168.254.12
[14:10:54.403771] AddCastDevice:649 [0x108fbf300]: adding renderer (Nursery speaker)
[14:10:54.404499] AddCastDevice:649 [0x108fbfca8]: adding renderer (Bedroom speaker)
[14:10:54.405175] AddCastDevice:649 [0x108fc0650]: adding renderer (Office speaker)
[14:11:05.568077] rtsp_thread:351 got RTSP connection 10
[14:11:05.574191] rtsp_thread:351 got RTSP connection 11
[14:11:05.578566] rtsp_thread:351 got RTSP connection 12 strangely though, i have no trouble connecting to an existing Sonos device using Sonoair which is apparently uses your code under the hood. 🙏 i'm a network novice as well. i poked around in my router settings and can see that UPnP is enabled but i haven't found a way to manage IGMP proxying yet. i'm happy to do more digging if there's any information in particular that would be helpful. either way, thank you for your work on this awesome project. as i said before, i've been enjoying using Airplay with my Sonos speaker flawlessly for some time. 🎹 |
@philippe44 Sorry for the delay. I think I accurately set the source and destination IPs on this wireshark capture. Let me know if this is of any help. Thank you! |
Hey @philippe44 Sorry for pestering you on this. Wondering if you've had a chance to see if that capture I sent a few weeks ago shows anything. Thanks |
For your info: I’ve just upgraded my Marshall UX bridge to a Google Nest Audio. I’m running aircast on a Mac and my network is based on Google WiFi. On my Marshall it all worked, on the Nest Audio i’m getting identical behavior as @brentluna. Maybe it’s something to do with Google home stuff? |
Can you send a few logs? |
I'm so sorry, I totally forgot about this. The next day it all worked like a charm! No idea why, because I didn't change any settings. |
No worries |
Running on Ubuntu server aircast-x86-64. Trying to connect to google home devices from iphone.
So I run the script, and get the following output, no other output is printed after this point.
I see the devices listed under airplay, however when i select one, it shows a spinning circle for about 10 seconds and then eventaully says
Unable to connec to device device_name
.The text was updated successfully, but these errors were encountered: