Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Iphone 6+ cannot find shairport-sync #15

Closed
ericwongcm opened this issue Nov 3, 2014 · 24 comments
Closed

Iphone 6+ cannot find shairport-sync #15

ericwongcm opened this issue Nov 3, 2014 · 24 comments

Comments

@ericwongcm
Copy link

Do you have any idea why Iphone 6+ running iOS 8.0.2 cannot find shairport-sync using airplay?
Iphone 6 probably have the same problem.

Strangely, Iphone 5S and 4S, also running iOS 8 can find shairport-sync without any problems..
Latest windows version of Itune also works fine with shairport-sync without any problems..
@mikebrady
Copy link
Owner

I'm away right now, but I had been using an iPhone 6 and a 5 with 8.0.2 with no problems. It'll be a week before I can recheck.

@ericwongcm
Copy link
Author

No problem...

@mikebrady
Copy link
Owner

There is something weird there using Attitude Adjustment compiled on the Ubuntu 12.04 host alright, from an iPhone 6 running 8.1. I'm checking it out.

@mikebrady
Copy link
Owner

I found a bug that was expressed clearly in "your" setup that would occasionally make shairport-sync become unresponsive and maybe disappear after one play. Could you try 2.1.9 and see if it helps? Certainly it has fixed the weirdness I observed earlier.

@mikebrady
Copy link
Owner

Seems to be a wider issue: https://discussions.apple.com/thread/6541631?start=0&tstart=0

@mikebrady
Copy link
Owner

Does 8.1.1 fix it?

@ericwongcm
Copy link
Author

IOS 8.1.1 and Shairport-sync 2.1.10 doesn't really fix the problem yet..

It seems like some IOS device still have trouble finding Shairport-sync while others doesn't... Still not sure why.. it is puzzling at the moment. The discovery problem seems to be not IOS version and not specific IOS device related. I have tested this on other people's IOS device and get contradicting results, e.g. Shairport-sync can be found in one Iphone 6 plus but not another unit which is also running the same IOS 8.1.1 OS.

Going to compare if this is related to the use of polarssl and openssl.
Will report back if I make any useful observations.

@mikebrady
Copy link
Owner

Thanks. There is quite a bit of chatter about problems that might be associated with Bonjour (i.e. zero configuration networking). Let's keep looking, but I suspect this problem may be symptomatic of a larger (Apple-wide) issue.

@soulchild
Copy link

Don't know if this is related, but I just wanted to chime in and say that I'm having weird problems with shairport(-sync) as well which started with iOS 8.

My devices are able to find, connect and play via shairport just fine, but with iOS 8 everything became highly unstable. If the device goes into lock-mode the stream is disrupted a couple of seconds or minutes later. My iPhone 4s can stream for hours (with lock-mode disabled) whereas an iPhone 5S and iPhone 6 stops playing after an indefinite time even with lock-mode disabled and I have to reconnect to shairport.

It's just a gut feeling but because many people report no problems with iOS 8 while others do and both have similar set ups (iOS devices and shairport/-sync), I can't help but think that this is some sort of network issue. Is it possible that the underlying networking became more susceptible to bad conditions? I bet it has got something to do with iOS 8 introducing peer-to-peer airplay ...

By the way: iTunes 12.0.1(.26) on Yosemite streams for hours to shairport with no problems at all.

P.S. I'm running shairport on a Raspberry Pi (so far I've used Volumio and Pi MusicBox which come with shairport and shairport-sync respectively).

@mikebrady
Copy link
Owner

Thanks for your report. Just to clarify, am I right in thinking that you're describing issues and behaviours that apply both to shairport and to shairport-sync? What would be interesting is to see if there are similar problems with Airport Express devices...

There seem to be lots of issues around iOS 8, and there's got to be some logical reason for them, whether it's peer-to-peer or Continuity or something else. Let's hope they iron out the bugs soon.

@soulchild
Copy link

Yes, both airplay implementations show very similar behavior. Unfortunately, I don't own an Airport express. I've only heard that Airplay continues to work just fine with the Apple TV, but I suppose that received an OS update as well coinciding with the release of iOS 8.

@Ponyboy47
Copy link

I have an Airport Express, shairport 1.0 on a raspberry pi and just barely set up a different raspberry pi with Shairport-Sync 2.1.1
My iPhone 5S find and plays to the Airport Express and Shairport 1.0 just fine, but it cannot find the Shairport-Sync, however, my Macbook Pro playing from iTunes connects to and plays just fine to all 3 devices

@mikebrady
Copy link
Owner

What version of Shairport Sync is it? (Just enter "shairport-sync -V" on the command line.)
[Edit] I think the network code is practically identical in shairport and shairport-sync – I haven't done much to it. If you're feeling curious, could you run Bonjour Browser on the Mac and list here the output for shairport and for shairport-sync? In particular, the IP numbers and port numbers advertised would be interesting...

@Ponyboy47
Copy link

Shairport version is 2.1.15-openssl-Avahi-ALSA
And today it seems to appear on all my devices..NO clue why today it shows up but not yesterday...

The output from Bonjour Browser:


Pool Speakers (Shairport v1.0)
  10.0.1.4:5002
Jake's Room (Shairport-Sync v2.1.15)
  10.0.1.7:5000
AppleTV
  10.0.1.30:5000
  (also it has some weird address) -> fe80::1ca3:9123:3d45:364e%en0
Airport Express
  10.0.1.20:5000
  (also has a weird address) -> fe80::4ad7:5ff:feee:5b14%en0
  (in addition to another IP address?) -> 169.254.236.55

Would you be interested in the Txt Record as well for each of them? I don't know what any of the data in the text record is..

@mikebrady
Copy link
Owner

Thanks for that. The weird addresses beginning with FE80: are automatically-assigned local IPv6 ip addresses and the 169.254... address is a self-assigned IPv4 address. They are all good. I can't see anything unusual there, TBH. There's no need for the TXT records thanks. Let's hope it stays stable – if not, see if there is any pattern to it.

@mikebrady
Copy link
Owner

Just wondering if some of this is similar to #29 ?

@mikebrady
Copy link
Owner

Oops – didn't mean to close the issue.

@mikebrady mikebrady reopened this Jan 5, 2015
@senthor
Copy link

senthor commented Mar 16, 2015

One question to all of you: What other Apple hardware do you have on the network? I used to have similar problems since upgrading to Yosemite while using an AirPort Express as router. There seem to be problems with distributing multicast packets (for Apple TV and AirPorts), as I suddenly was unable to find shairport, the AirPort Express AirPlay, and my Mac started changing names every few hours (always "[Name] n+1").
Solution was to remove the AirPort Express and use other (non-Apple) networking hardware.

@soulchild
Copy link

I only have a couple of iPhones/iPads and a Yosemite Macbook Pro on the network. No Apple Airport stuff. But I have the feeling that some lower level networking issues are at play here as well.

I had a DD-WRT Linksys WRT54GS and was very happy with it. Then came iOS 8 with which (presumably) the airplay connection dropping started. Everything went downhill after an upgrade of my internet connection, because my ISP forced me to use a new combined and utter crap cablemodem/router combination (Technicolor TC7200U) which totally broke mDNS, thus Airplay stopped working completely. It turned out that with WMM enabled, the router just wouldn't route multicast DNS between WiFi and LAN, so my devices wouldn't even see shairport. How silly is that? I switched to a Netgear Nighthawk R7000 and Airplay has been MUCH MORE reliable since then, but I do get the occasional connection drops.

@ghost
Copy link

ghost commented Apr 29, 2015

Hi, I used to have a lot of problems with iPad Air, having to re-connect to wifi all the time to get Airplay to show up. I bought Raspberry Pi 2 right after the release and upgraded to the last version of Shairport Sync. I have not had any problems with Airplay since...

@mikebrady
Copy link
Owner

Thanks for the report. I've noticed a gradual improvement over the last few months, but I'm not sure what's causing it.

@soulchild
Copy link

I guess under the hood changes in the Airplay implementation of the various minor iOS revisions since iOS 8.0 ... ;-)

@mikebrady mikebrady mentioned this issue May 5, 2015
Closed
@mikebrady
Copy link
Owner

This looks interesting: http://arstechnica.com/apple/2015/05/new-os-x-beta-dumps-discoveryd-restores-mdnsresponder-to-fix-dns-bugs/. I wonder if it's related to the problems reported here.

@mikebrady mikebrady mentioned this issue Jul 14, 2015
Closed
@mikebrady
Copy link
Owner

This seems to be entirely fixed by OS 10.10.4 and later and iOS 9. Closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@soulchild @Ponyboy47 @mikebrady @ericwongcm @senthor