mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #887] allow binding to LAN address instead of 0.0.0.0 for zeroconf #440
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#440
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 @ayushnix on GitHub (Nov 23, 2021).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/887
It seems like librespot binds to all interfaces (0.0.0.0) by default for zeroconf discovery.
Pardon my ignorance but does it need to bind to all interfaces for zeroconf discovery? Would it be possible to bind it to the assigned LAN address (such as 192.168.1.2) and still have the Spotify Discovery feature (which is what zeroconf is used for?) work as expected? If yes, can we get an option to change the address to which librespot binds to for zeroconf?
I've raised a similar issue in the spotifyd repository as well.
@roderickvd commented on GitHub (Nov 23, 2021):
Duplicate of #486.