-
Notifications
You must be signed in to change notification settings - Fork 23
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
Allow specifying bind interfaces in addition to addresses #3
Comments
Good idea, and presumably if the interface has multiple IPs, you’d expect it to listen on each? Shouldn’t be difficult, I can probably look at it tonight or tomorrow...
… On Nov 22, 2017, at 12:03 PM, Toke Høiland-Jørgensen ***@***.***> wrote:
When deploying irtt to my testbed, I have several boxes with the same interface names but with diffent IPs assigned to each interface. It would be useful to be able to specify the interface name to -b instead of the address, since I can then just reuse the same systemd unit file.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#3>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEMYsQ7mrkSnrbkk28QGGSipbXZIppPIks5s4_9rgaJpZM4QnOIS>.
|
You can now do: The default bind address is now "%*" so people won't see that pesky warning, unless they've actively specified a bind address with an unspecified IP on a box with multiple IPs. This was a bunch of changed and new code and I only tested on a few boxes, so re-open with any problems... |
Awesome, thanks! :)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When deploying irtt to my testbed, I have several boxes with the same interface names but with diffent IPs assigned to each interface. It would be useful to be able to specify the interface name to -b instead of the address, since I can then just reuse the same systemd unit file.
The text was updated successfully, but these errors were encountered: