Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using DataCenter Internal IP for CloudServer <-> CloudFiles transfer #6038

Closed
cyberduck opened this issue Jun 26, 2011 · 3 comments
Closed

Using DataCenter Internal IP for CloudServer <-> CloudFiles transfer #6038

cyberduck opened this issue Jun 26, 2011 · 3 comments
Assignees
@dkocher
Labels
cloudfiles Rackspace CloudFiles enhancement thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

a998853 created the issue

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.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

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

@cyberduck
Copy link
Collaborator Author

a998853 commented

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.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

What I mean is that internally from a CloudServer, the URI to your CloudFiles container such as storage101.dfw1.clouddrive.com 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.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
cloudfiles Rackspace CloudFiles enhancement thirdparty Issue caused by third party
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck