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: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Tue, 5 Jan 2010 17:36:50 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 05 Jan 2010 07:37:26 -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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Tue, Jan 05, 2010 at 02:29:23PM +0100, Info - csdemmer wrote:
>    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.
> 
>    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?

Yes, the Xen domain IDs are always dynamic.

You can configure Xen to assign static vif names for each guest using 
"vifname=" option on the vif line in /etc/xen/<guest> cfgfile.

See "xm create --help_config" for more information.

Another option is to parse the guest ID from for example "xm list" and
use that in your firewall script to create the vif name.

-- Pasi


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

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