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

support manually assigning IPs to nodes #12

Open
volfco opened this issue Dec 10, 2019 · 7 comments
Open

support manually assigning IPs to nodes #12

volfco opened this issue Dec 10, 2019 · 7 comments
Labels
enhancement New feature or request

Comments

@volfco
Copy link

volfco commented Dec 10, 2019

Is there a way to statically assign IPs to a specific node?

@costela costela added the question Further information is requested label Dec 10, 2019
@costela
Copy link
Owner

costela commented Dec 10, 2019

Currently no. The idea is to keep the management overhead to a minimum.

Do you have a concrete use-case for which the /etc/hosts handling is not a solution?

@volfco
Copy link
Author

volfco commented Dec 10, 2019

The three I have are:

  1. All of the software I've written doesn't have support for taking hostnames- it expects an IP address

  2. Exposing the mesh network to private networks is impossible due to the need to setup static routes on the host- which you can't do when you don't know the IP address of the routing nodes.

  3. Half the environment is managed via Salt/Ansible, and half dynamic. There is no way for a host not in the mesh to talk to one that is (assuming routing is setup correctly)

@costela
Copy link
Owner

costela commented Dec 10, 2019

I don't really have an answer for 1.

As for 2 and 3: this use-case isn't currently supported and probably wouldn't work as you expect: if you're talking about routing, you're probably thinking of adding a sort of "gateway" to the mesh on the statically managed side. Even if you had static IPs, the private nodes would be able to route traffic to the mesh, but the mesh would not be able to route them back.

I suspect #8 might a more productive direction. In this case you'd just add all your private nodes to the mesh and let them talk directly to each other. Unfortunately we're not quite there yet.

@volfco
Copy link
Author

volfco commented Dec 10, 2019

2/3 can be addresses by adding a static route to every host (via configuration management)

@costela
Copy link
Owner

costela commented Dec 10, 2019

If you're already using config management to add the static route to all dynamic hosts, you could probably collect their IPs and add the outgoing routes on the static side.

But again: we're probably outside the realm of what wesher was meant to solve.

@costela costela changed the title Static IPs support manually assigning IPs to nodes Jan 10, 2020
@fniko
Copy link

fniko commented Jan 13, 2020

I would endorse the idea of static IPs. I am solving the same issue (2/3, routing traffic to another server based on subnet) and unfortunately, there is no "easy" way how to set up default gateway based on hostname.

I wanted to move from "pure" wireguard to something more complex and I thought wesher could solve this.

@costela costela added enhancement New feature or request and removed question Further information is requested labels Jan 13, 2020
@lenovouser
Copy link

I'd also really like this because we have software that search for applications running on specific internal IPs and want to specify them for each server. (We want to have the same network layout with the same hosts for different regions)

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

No branches or pull requests

4 participants