mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #1189] Ability to specify which zeroconf ap address to advertise #550
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#550
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 @fplanjer on GitHub (Jul 21, 2023).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1189
I'm running raspotify in a container on an k3s cluster, which uses librespot.
The ip adress librespot binds to (the container ip) is not the ipadress that clients should connect to (the node ip adress).
The ip advertised with zeroconf is the internal container ip and clients are not able to connect to it.
I'd like to be able to specify the ip addres that should be advertised in zeroconf.
@kingosticks commented on GitHub (Jul 21, 2023):
Pretty sure there's already an option for this which is documented in the wiki but I'm also pretty sure it's broken and the code ignores the option.