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
servers within a network with static ip might be overwritten? #864
Comments
One possibility is to specify an IP range for nodes autoconfiguration (with the /16/17 notation) and another for DHCP leaving out a range available for the static IPs. lime-packages/packages/lime-docs/files/www/docs/lime-example.txt Lines 33 to 35 in 2b7226a
|
Thanks @ilario for your response. Yes indeed, you can. I would like to (and feel would be positive for the process):
Also, I am interested in ways to approach this that don't require to reflash the whole mesh with a new set of configurations, or if needed to create the necessary changes in order for this not to be required, as it is something that belongs to the runtime of the network, and it happens in relation with a different layer, so it should expect not to be hardwired on the firmware.... right? eager to hear the rest here... |
If I got this right, I think this may somehow tackle number 2 as it does not need to be configured in the whole mesh manually: At the node in which you have your pi / computer that needs a fixed ip connected add the following:
From d632acc By using copy_asset at lime-node, the configuration will be persisted through upgrades making maintenance easier. |
Thanks for this @germanferrero ! |
Im trying the suggestion by German, and I'm getting the following error when running lime-config after the changes:
the files were edited like this:
/etc/config/lime-node:
|
Hi Bruno! I think that the problem is that UCI does not support the middle |
Even after years this is still useful, se need to confirm this work and document it. |
While having a conversation with @tbdinesh this issue came about:
this made me think how we manage the computers that are fixed in our networks.
One way of approaching this is to add the fixed ip and host to /etc/hosts, but you would have to maintain it yourself.
The other way is by not configuring it at all... i think that when the dhcp does a lease, it asks if that ip has been used (so it doesn't step onto anyone else)... but not sure if it happens on all interfaces (so bat0 is also included, ie the whole mesh), or not...
Anyway, I believe this should be a typical usecase that we should consider.
The text was updated successfully, but these errors were encountered: