[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Routed Network with Xen



On Mon, Feb 13, 2012 at 1:26 PM, Simon Hobson <linux@xxxxxxxxxxxxxxxx> wrote:
Rakesh Chawda wrote:

Also, I have hit a new issue. Inspite of the NAT setup, the outgoing IP of all the DomUs can be seen as the main Dom0 IP, and not the individual IPs assigned to the domUs.

Please try to trim excess quoted material !

The fact that everything appears to come from one IP is a function of the NAT - not "inspite of it". Unless you take measures to do something different, then the default for most NAT setups is that all traffic will use one IP.

But at this point, could I suggest a step back for a moment. I'm struggling to understand your network setup, so perhaps you could describe in detail what you get from your ISP - it would help in trying to suggest how to get your networking going.

--
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

Thanks for the answer.

I solved the problem of outgoing IP, by removing one particular rule:

iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

Now, the outgoing IP is as required (additional static IPs).

Below are the details of the setup as required, please suggest as required:

Main Server IP: 1.1.1.5 (eg.)
Gateway for Main IP: 1.1.1.1
Additional IP: 1.1.2.1/28 (Different Subnet)
Gateway for additional IPs: not required, as they are "statically bound to MAC address --stated by DC"

The additional IPs to be used only on Dom0 to avoid different MAC addr. Hence, xen bridge network is out of question. I have added these IPs using alias adapters eth0:1, eth0:2, etc.

So, I am using xen routed network scripts, where virbr0 gets 192.168.122.1 IP, and becomes the gateway for the DomUs. The DomUs now have IPs in the range of 192.168.122.0/24.

The setup requirement is that the DomUs should be accessible with the additional static IPs, so I took the path of NAT.
This setup is working now, but I doubt about the performance, as it was previously stated that this will utilize more resources. So, please please suggest other options.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.