Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hostname/DNS support for TCP client stream sources #1119

Open
Omar007 opened this issue Mar 24, 2023 · 0 comments
Open

Hostname/DNS support for TCP client stream sources #1119

Omar007 opened this issue Mar 24, 2023 · 0 comments

Comments

@Omar007
Copy link

Omar007 commented Mar 24, 2023

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant