i dont beleive that backuppc gets the IP from the login on the web interface, though i could be wrong.
as for the dyndns, that would work as long as the PC ran the dyndns service to report IP whenever it hooks up. good idea.
> maybe set a rediculously large timeout for backuppc and set the rsync
> option --timeout and see if rsync manages it better. i think that
> rsync's --timeout option looks for activity not just completion so it
> wont timeout on a large file while backuppc looks just for activity
> across the ssh link, which is quiet -q so large files eaily reach that
> im not sure what removing the -q will do to your backups but it might
> see that verbosity as part of a file stream and corrupt the files.
> anyone else have a clue on this?
> i cant try this out, i have some clients use a VPN over public networks
> but i dont do backups over these links because backuppc cannot find
> these client via netbios and their IP address changes every time the
> I need some way for a client to broadcast it's IP address to backuppc
> but im not sure how to do that. maybe setup a WINS server or something.
Doesn't this work if the client logs into the web interface and clicks
the 'start backup' link? I thought that was supposed to pick up the
client IP address if it isn't in DNS. The other approach is to have the
VPN hand out fixed addresses to each client and put the names in DNS.