WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] xen domU ID and static routing

To: Info - csdemmer <info@xxxxxxxxxxx>
Subject: Re: [Xen-users] xen domU ID and static routing
From: Thomas Halinka <lists@xxxxxxxxx>
Date: Wed, 06 Jan 2010 14:11:58 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 06 Jan 2010 05:12:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B433EB3.5000409@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4B433EB3.5000409@xxxxxxxxxxx>
Reply-to: lists@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi csdemmer,

Am Dienstag, den 05.01.2010, 14:29 +0100 schrieb Info - csdemmer:
> Hi,
> 
> I use a EQ 4 dedicated root server by hetzner with ubuntu jaunty. I
> installed xen 3.3 with debian kernel and brought up 3 domUs.
> Now comes networking...
> Hetzner does not allow bridged networking so I have to use routed mode
> in xen. No Problem so far, but the Problem actually is:
> When I bring up a domU the routing table is created by the xen-script
> vif-routing. The network interface name for this is created
> dynamically, depending on the domU ID.

Im just assigning one ip of the subnet to dom0, that acts as router....

# cat /etc/xen/scripts/network-hetzner
---
        #!/bin/bash
        #
        # This xen-network-scripts fires up the internal and external
        bridges,
        # and finally activates routing in dom0
        #
        #
        # thohal, 14.01.09
        #
        ###### 
        
        #
        # fire up internal bridge for openqrm
        # ...
        # .... some magic secrets in here :-)
        # ...
        # fire up external bridge public access
        # xx.yy.zz.16/27
        # usable ips: xx.yy.zz.161 - xx.yy.zz.190
        
        brctl addbr xen-public
        ifconfig xen-public xx.yy.zz.65 netmask 255.255.255.224 up
        
        
        #
        # finally activate routing and let dom0 act as a router
        #
        #
        
        echo 1 > /proc/sys/net/ipv4/ip_forward
        
make it executable (chmod +x), configure it in /etc/xen/xend-config.sxp
and restart xend...


> 
> Example:
> If the domU ID is 16, the network interfaces name will be vif16.0 in
> the dom0. So I tell shorewall (iptables frontend) that it shall ACCEPT
> traffic from an to vif16.0. The next time I restart my server or just
> the domU, there's a new network interface name, that the shorewall
> firewall does not know...
> 
> As far as I know there's no way to tell a xen domU to get a static ID,
> so the network interface name would be static as well.
> Any Ideas or solutions? 

hth,

thomas

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


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

<Prev in Thread] Current Thread [Next in Thread>