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

Interface support #99

Open
kfox1111 opened this issue Sep 18, 2019 · 4 comments
Open

Interface support #99

kfox1111 opened this issue Sep 18, 2019 · 4 comments

Comments

@kfox1111
Copy link

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.

@danderson
Copy link
Owner

danderson commented Sep 18, 2019

Edited - danderson made confused sounding noises because he wasn't looking at the project name for this bug

@kfox1111
Copy link
Author

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.

@danderson
Copy link
Owner

danderson commented Sep 18, 2019

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.

@danderson
Copy link
Owner

I've forgotten how most of pixiecore works, but two ways of doing this:

  • cmdline flag only, which gets resolved and translated into Server.Address in pixiecore.go
  • Add a Server.Interface string in pixiecore.go, and some logic to allow Address XOR Interface, and resolve appropriately to a listen addr for the socket bind.

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

No branches or pull requests

2 participants