mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #56] Discovery mode interferes with system DNS configuration #44
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#44
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/56
Tuesday Apr 25, 2017 at 11:02 GMT
Originally opened as https://github.com/plietar/librespot/issues/178
Hi, I can't launch librespot because of dns resolve failure. Below is the error msg.
update: backtrace with debug info.
I have dnscrypt and dnsmasq set up. dnsmasq binds to 127.0.0.1:53, which queries dnscrypt in case the address is not known. I have noticed that, when launching librespot,
I can't resolve any address (system-wide).
It seems like all the dns resolves are intercepted by librespot. Is this normal? And is there a way to fix this?
@sashahilton00 commented on GitHub (Jan 29, 2018):
Tuesday Apr 25, 2017 at 11:09 GMT
librespot uses mDNS for zeroconf authentication by default. This may interfere with unusual DNS setups.
Can you run librespot with
--disable-discovery?@sashahilton00 commented on GitHub (Jan 29, 2018):
Tuesday Apr 25, 2017 at 15:43 GMT
With this option it doesn't interfere with the DNS setups, but I could't login either. This is the backtrace with librespot built with debug info. I guess the dns issue is solved. I can close this thread and open a new one if you prefer that. It's possibly related to #167
@sashahilton00 commented on GitHub (Jan 29, 2018):
Tuesday Apr 25, 2017 at 15:55 GMT
No, I'd prefer keeping this issue open. librespot shouldn't interfere with the system's DNS configuration, so this is still a bug.
Moving to #167 for the authentication failure issue.
@sashahilton00 commented on GitHub (Jan 29, 2018):
Monday Jun 26, 2017 at 10:48 GMT
This looks a bit like the issue I'm experiencing: https://github.com/shanemeagher/service.librespot/issues/3
Doesn't resolve as well, no custom DNS setup btw, just libreelec out of the box and Openwrt on the router (gets results from provider DNS and Google as backup).
@sashahilton00 commented on GitHub (Jan 29, 2018):
Saturday Aug 26, 2017 at 17:04 GMT
I use avahi daemon (zerconf) for several services. Whenever I want to use librespot I have to stop that daemon, which runs on port 5353, first. Does librespot has its own zeroconf functionality which interferes with avahi?
@sashahilton00 commented on GitHub (Jan 29, 2018):
Wednesday Sep 06, 2017 at 02:06 GMT
@dowhiletrue yes, librespot has mdns / zeroconf built-in. Pull Request #246 allows librespot to be built to use an existing avahi install which should avoid this conflict.
Until this is merged, setting
disallow-other-stacks=noin avahi-daemon.conf, should allow both to co-exist.@ComlOnline commented on GitHub (Jan 29, 2018):
See #13 for continued discussions