On Wed, Mar 28, 2012 at 10:44 AM, Michael Coffman
<michael.coffman AT avagotech DOT com> wrote:
> Our company has been mucking around with DHCP and DDNS configuration to
> support users migrating from a remote login to wireless to hardwired  ( I
> have not control or authority into this environment).
>
> The end result is that backuppc for very mobile users seems to be
> perpetually broken.   As their laptop moves around it gets multiple IPs
> associated with it and the forward-reverse lookups don't always work.    We
> have even had the case of a users laptop getting the IP that had previously
> belong to another system and the IP had not been flushed from DDNS cleanly -
> end result was laptop A backed up into the location form laptop B.    Has
> anyone else had to deal with this?   Any creative ideas for preventing this
> previous issue or for dealing with ever changing system names?    I believe
> that the right answer is to fix our DHCP/DNS/DDNS environment, but I dont'
> think that's going to happen.   I am about ready to bail on backuppc for our
> highly mobile users :(    Not sure what I expect from the list, just kind of
> grasping at straws at this point.

It is probably overkill for this case, but one possibility that also
works if you need to tunnel through firewalls is to set up VPN
accounts that assign fixed IPs per login.  OpenVPN can be set up this
way, and could run on the same server as backuppc.  Then you can use
the ClientAliasName to point to the VPN IP address.

-- 
   Les Mikesell
     lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/