Currently the DHCP leases funciton of Webmin works locally with the dchp.leases file and the dhcpd.conf (for configuration and static hosts), could our local Webmin server connect internally via ssh to other linux servers to read and modify these files in order to be able to list and configure their DHCP?
These could be done in 2 ways:
1 - Using a webmin cluster:
- Advantage: No need to store their passwords(in case that we share the same user/password in all the cluster)
- Disadvantage: We need to install webmin in all the other remote DHCP servers.
2 -Connect to the remote DHCP servers via SSH:
- Advantage: No need to install webmin on them.
- Note(to Confirm): If we create an root user in the remote DHCP servers with the same password than our current webmin administrator, then we don't need to store passwords in our Webmin.
That's the reason I would sugest the 2nd way. Let me know your feedback about it.
By the way, is there any already implemented webmin module that connects internally trought ssh to another sever(no webmin) to view or modify any configuration?
On 06/Mar/2008 23:35 Ivan Garcia wrote ..Hi everybody, is it possible centralize the crontab management and DHCP leases for many servers using only one Webmin server? Does the cluster allow to do this? Do we need to install Webmin in all the remote servers or webmin will connect internally trought SSH and manage Cron and DHCP?
If it's not implemented, can you give us an example of something similar already done in Webmin?
Webmin does have a Cluster Cron Jobs module that can run commands on multiple systems, although they do all need to have webmin installed.
What do you want to do with a DHCP cluster though? Are you looking for a way to have multiple redundant servers with the same configs .. and if so, is that even possible without them stepping on each others' toes due to differences in the lease files?
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Forwarded by the Webmin development list at email@example.com
To remove yourself from this list, go to