You can't "share" an IP with your server. If your dom0 has an IP assigned by the ISP for you to access it to manage, you cannot assign that IP to any other domU on the system. IPs must always be unique. With bridging, each domU must have an IP that the network connected to the bridge can see. So, if your dom0 eth0 has an IP address and you set up a bridge for the domUs to access and want them to communicate with the dom0 and on the same network as the dom0, they need to be on the same subnet and have the same subnet mask. The other option is to do some sort of NAT setup using the dom0 IP address and iptables (e.g. on a Linux-based dom0) so that your domUs use NAT to see the outside world. In this setup you can use port forwarding on the dom0 to forward certain services into the domUs, but each port can only forward to a single domU.
-Nick
>>> On 2008/06/20 at 16:41, Rudi Ahlers <Rudi@xxxxxxxxxxx> wrote:
Hi all I wonder if someone can give me some suggestions, from experience on this. We have 4 IP's per server, and I'd like to use them wisely. dom0 won't really be used, other than accessing / managing / monitoring domU's. So, is it wise to share the main IP of the server with a domU ? And from what I understand, this is bridging, right? I need to access the domU directly from the internet, via the IP that our ISP has assigned to us. -- Kind Regards Rudi Ahlers CEO, SoftDux Web: http://www.SoftDux.comCheck out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
|