You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: