I want to submit a fact that occurred with me and I want to share with you to see how to avoid lost connection with the Nethserver instance…
For exemple.
I configure the network with a static IP address( i.e. 192.168.200.1 ) and configure a DHCP server to distribute a range of IP (192.168.200.100 to 192.168.200.254 )
Now, I go to change the static IP address for 192.168.2.1… If I go to the configuration / network module and edit the ip configuration, I will lost the connection because the DHCP server will continue to distribute the older IP range.
You will tell me it’s easy to change the client IP address temporary to reconnect to the Nethserver instance, but If the client is a WIFI client, and the AP point is in the DHCP range… The connection is really lost.
I will make the suggestion when there`s a DHCP server attach on a static IP address. When a static IP address is change, to check the DHCP server to eventually change the IP range too.
sorry but this is, IMHO, not a NS issue…
no appliance (pinters, AP and so on ) should be on dhcp, 'cause such a setup is prone to many troubles
moreover, changing lan addressing range is not a thing you do frequently… in a production environment, almost never
delegating all the “smartness” to NS is not smart, 'cause this approach will lead to less control
almost any other product dhcp server capable out there behave in the same way than NS… and the reason is that some things can not be delegated, but they depends on “smartness” of the guy sitting between keyboard and chair
So, I make the suggestion when there`s a DHCP server attach on a static IP address. When a static IP address is change, to check the DHCP server to eventually allow to change the IP range too.
and/or put an advertisement that the change will affect the DHCP server and allow to change the DHCP server before apply change… To make things smarter
Todat, with my electrical provider… I had an system injury, one of my NIC was fried.
With lot of chance, it was only the NIC daugther board than fry, the two NIC in the motherboard still okay.
But I had to change configuration… And lost the connection with the NethServer instance due to the DHCP server that was not change at the same time the IP configuration is.