Cyberduck Mountain Duck CLI

#6038 closed enhancement (thirdparty)

Using DataCenter Internal IP for CloudServer <-> CloudFiles transfer

Reported by: samsen Owned by: dkocher
Priority: normal Milestone:
Component: cloudfiles Version: 4.0.2
Severity: normal Keywords: Internal IP Data Transfer
Cc: Architecture: Intel
Platform: Windows 7


When logged in, via Microsoft Remote Desktop to our Rackspace Windows 2008 R2 CloudServers, on which CyberDuck has been installed, we incur bandwidth charges when transferring between CloudServers and CloudFiles using Cyberduck, because the transfers are performed using the external IP.

When specifying the account name and password (API Key) for the Cloudfiles account, it would be good if there was an option to enter in the internal IP address that RackSpaceCloud provides, for the Cyberduck instances on those servers. And it would be awesome, if Cyberduck could be enhanced, so that data transfers between CloudServers and CloudFiles in the same data center could take place via that given internal IP. This would eliminate unnecessary bandwidth charges.

Change History (3)

comment:1 Changed on Jun 27, 2011 at 5:48:38 AM by dkocher

Isn't it feasible that you configure your DNS or hosts file accordingly?

comment:2 Changed on Jun 27, 2011 at 12:29:35 PM by samsen

You would have to explain what you mean by this.

The only parameters we have for telling Cyberduck which CloudFiles account to use, is the account name and the API key. Using that, you must somehow get the IP that you use to perform any transfers. The internal IPs that Rackspace for within data center transfers starts with "10." I am not a sophisticated enough user to understand how I would be able to redirect Cyberduck to use the internal IP without somehow affecting other apps.

If are interested in adding this enhancement, if you don't already have your own account with RackSpace, we would be happy to give you access to one of our cloud servers, so you see if setting a DNS entry or Hostname would work.

comment:3 Changed on Jun 29, 2011 at 6:11:48 AM by dkocher

  • Resolution set to thirdparty
  • Status changed from new to closed

What I mean is that internally from a CloudServer, the URI to your CloudFiles container such as should resolve to its internal address. This is a configuration issue on the server. Can you please contact Rackspace support about this and let me know here afterwards if the aren't able to resolve this.

Note: See TracTickets for help on using tickets.