-
Notifications
You must be signed in to change notification settings - Fork 181
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
Interface support #99
Comments
Edited - danderson made confused sounding noises because he wasn't looking at the project name for this bug |
Oh. sorry. Was looking at the pixiecore code and forgot there were other pieces. a -i to pixiecore as an alternate option to -l. I need to bind it to a particular network, but the ip's vary per host. |
Oh, er. Sorry, I'm just massively confused and thought that this was a bug for MetalLB, my other side-project. Oops. Yeah, an interface selector sounds reasonable. I'm vaguely surprised it's not already there. |
I've forgotten how most of pixiecore works, but two ways of doing this:
|
It would be nice if you could specify which interface to bind to rather then which ip address. This would make it easier to manage within a cluster.
The text was updated successfully, but these errors were encountered: