Bacula and Dynamic DNS

Recently I have decided to go from [http://www.edwinh.org/flexbackup Flexbackup] (which by the way is an excellent tool),to [http://www.bacula.org bacula]. I did this for two main reasons,the first was the cross platform backup support and the second I needed a more robust backup solution for multiple computers. My network is a mix of wired and wireless systems. I had already setup Dynamic DNS using other guides on the net ([http://www.ops.ietf.org/dns/dynupd/secure-ddns-howto.html guide1],[http://dag.wieers.com/howto/bits/bind-ddns.php guide2]). My problem was that bacula really needed either static IPs (yuck) or DNS names to do backups on clients. This worked fine on wired clients,but wireless clients presented a real problem. My wireless clients first connect to the WAP54G using WPA,then to the local LAN via [http://www.openvpn.net OpenVPN]. In connecting to the WAP54G,the wireless clients pull an address from the DHCP server in the *.wireless.cfreeze.com domain. When they connect to LAN via [http://www.openvpn.net OpenVPN],the receive an address on the LAN. This is where the normal dynamic DNS setup breaks down. To get resolvable addresses for OpenVPN clients using dynamic DNS,I had to write a few scripts and use the “client-connect”and “client-disconnect”options in my [http://www.openvpn.net OpenVPN] configuration file.
The [http://www.openvpn.net OpenVPN] configuration file allows for two options to be specified. These options are “client-connect”and “client-disconnect”. These scripts are ran when a client connects or disconnects from the OpenVPN server. If you are not using the “server”mode of [http://www.openvpn.net OpenVPN],you can use the “ipchange”parameter instead.
Using the following scripts in the these parameters allow for the OpenVPN server to update my DNS server of the new addresses of clients. This then allows [http://www.bacula.org bacula] to resolve these clients for the backup process.

Posted from Fort Worth,Texas,United States.