Open stonier opened 10 years ago
Looking at dns servers to handle this. Particularly dynamic dns servers. That way every computer has a name, and even if the ip changes underneath, the rest of the system keeps resolving the ip from the same name.
These apparently can also do split nameserving. i.e. other computers get the external ip, while the local computer itself gets 127.0.0.1.
Bind and dnsmasq are commonly setup to do dynamic dns serving. However all the tutorials involve bind + dhcp servers. When the dhcp server dishes out an ip, it notifies and updates bind directly.
We don't have control over the dhcp server to configure it like this.
Surely though, other people are in the same situation? We are effectively looking for dyndns on the lan.
This seems to be a simple web-authenticated methodology for achieving DDNS: http://andrwe.org/linux/own-ddns
I might give it a shot.
This is an action in the wireless disconnection policies.
This is to handle the case when clients go down and get provisioned with a new ip. It also makes the ROS_IP configuration far easier.