[Cyberduck-trac] [Cyberduck] #6038: Using DataCenter Internal IP for CloudServer <-> CloudFiles transfer

[Cyberduck]

#6038: Using DataCenter Internal IP for CloudServer <-> CloudFiles transfer
----------------------------+---------------------------------------
    Reporter:  samsen       |      Owner:  dkocher
        Type:  enhancement  |     Status:  new
    Priority:  normal       |  Milestone:
   Component:  cloudfiles   |    Version:  4.0.2
    Severity:  normal       |   Keywords:  Internal IP Data Transfer
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.

-- 
Ticket URL: <http://trac.cyberduck.ch/ticket/6038>
Cyberduck <http://cyberduck.ch>
Open source FTP, SFTP, WebDAV, Cloud Files, Google Docs & Amazon S3 Browser for Mac & Windows.