[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                     |    Resolution:
 Keywords:  Internal IP Data Transfer  |  Architecture:  Intel
 Platform:  Windows 7                  |
---------------------------------------+------------------------

Comment (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.

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