Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Update: As per grawity and MonkeeSage's comments, it seems my question was pointed in the wrong direction. I've updated the title and question below...

I'm currently evaluating LXC as an option for my company to safely and easily deploy several client projects to a single virtual server hosted on Rackspace. All the articles I'm reading use Bridged networking + DHCP to give each container its own IP on the local network. Unfortunately, this isn't an option on Rackspace since they do not allow a virtual machine to allocate any additional internal IP addresses.

How can I set up my own subnet that won't conflict with Rackspaces? The containers on each server must be accessible from other hosts on the Rackspace network and must be able to access the internet.

share|improve this question

migrated from Aug 30 '11 at 11:54

This question came from our site for computer enthusiasts and power users.

NAT + private address range + DHCP? – grawity Aug 29 '11 at 22:00
@grawity has the right idea, just be sure to use a different private subnet than or you'll overlap with the subnet Rackspace uses for service network. – MonkeeSage Aug 30 '11 at 14:23

I'm not sure that you can really do this in the way you're describing. If you're making up additional IPs, they have to be assigned to you by someone. If you're doing NAT (acting as a "router"), then on that "virtual segment" you can use any IPs that you want, since nobody else will see them, but I'm not sure how this virtual segment would appear.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.