snapcast icon indicating copy to clipboard operation
snapcast copied to clipboard

Hostname/DNS support for TCP client stream sources

Open Omar007 opened this issue 1 year ago • 0 comments

Is your feature request related to a problem? Please describe. In a (dual-stack) setup without fixed addresses, having to code in a fixed IP for tcp client mode stream sources requires a manual configuration change every time the address or stack of a client changes.

Describe the solution you'd like Allow the tcp client mode stream source configuration to take a hostname instead of just a fixed IP address.

Describe alternatives you've considered I do not have any alternatives in mind. Other than what you would basically have to do now (lay out static IP addresses everywhere and hard-code addresses in the configuration) I do not see an alternative here.

Additional context For the TCP stream sources the address also needs to be hard-coded for the server mode sources atm. However, this feature request is scoped to just the client mode stream source. It does not make sense to have this on the server mode imo but if this is a generic codepath or something I also don't see why support would need to explicitly be avoided there either.

What would be especially good for the server mode stream sources though, would be to bind to all interfaces (if it doesn't support so already).

Omar007 avatar Mar 24 '23 21:03 Omar007