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] Howto mix public and private ip-addresses?

To: Stephan Seitz <s.seitz@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Howto mix public and private ip-addresses?
From: Joerg Schoppet <joerg@xxxxxxxxxxx>
Date: Mon, 10 Dec 2007 22:48:26 +0100
Cc: XEN User - listmembers <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Dec 2007 13:49:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <475BEDFB.3040806@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <475BC166.7090500@xxxxxxxxxxx> <475BEDFB.3040806@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (X11/20071022)
Hi,

thanks for the answer. But this is for a bridged-setup. What have I to
do for a routed-setup?

Or can I configure the network, so that the public ip-addresses use
routed-setup (as of now), and the private ip-addresses use bridged-setup?


Regards

Joerg Schoppet

Stephan Seitz wrote:
> Hi,
>
> for easier use i packed our own xen deb's with an additional
> script in /etc/xen/scripts to setup more than one bridge:
>
> the entry in xend-config.sxp has to be changed from 'network-bridge'
> to the name of the wrapper script (needs to be chmod +x)
>
> ---snip---
> #!/bin/sh
> #
> # this is an example to start more than one bridge on different vif's
> #
> #
>
> XENDIR="/etc/xen/scripts"
>
> #
> # start first bridge (xenbr0) on eth0
> #
> $XENDIR/network-bridge "$@" netdev=eth0 bridge=xenbr0 vifnum=0
>
> #
> # start another bridge (xenbr1) on eth1
> #
> #$XENDIR/network-bridge "$@" netdev=eth1 bridge=xenbr1 vifnum=1
>
> #
> # start a third bridge (xenbr2) as machine internal net segment
> #
> #DUMMY="dummy0"
> #/sbin/modprobe dummy 2>/dev/null >/dev/null && \
> #    /sbin/ifconfig $DUMMY up 2>/dev/null >/dev/null && \
> #    $XENDIR/network-bridge "$@" netdev=$DUMMY bridge=xenbr2 vifnum=2
> ---snip---
>
> uncommenting the third bridge entry, a domU config line like
>
> vif = [ 'mac=gi:ve:so:me:mac,bridge=xenbr0', 
> 'mac=gi:ve:an:ot:her:mac,bridge=xenbr2 ]
>
> should give you two domU interfaces, the second one bound to a bridge on 
> dom0's dummy0
> interface.
>
> this could be used to connect the domU's together. even dom0 could use this 
> bridge
> via dummy0.
>
> one thing to note: during tests with heavy net i/o over a dummy0 bridge i 
> found dom0
> freezing, but this could have been a dom0's kernel issue.
>
> greetings
>
> Stephan
>
>
>
> Joerg Schoppet schrieb:
>   
>> Hi,
>>
>> actually I have the following setup:
>>
>> Ubuntu Gutsy with Xen 3.1
>>
>> I have one public ip-address AND a /29 subnet with public ip-addresses.
>>
>> Xen is configured as routed-setup:
>>
>> dom0: has the public ip-address and the first ip-address from the subnet.
>> each domU has an ip-address from the subnet and as gateway the first
>> ip-address from the subnet.
>>
>> Everything works!
>>
>>
>> Now I want to put a private address 192.168.1.x to each domU and to
>> dom0, so that I can bind some network-services to these ip-addresses,
>> which should only be addressable within the virtual systems.
>>
>> How can I do this?
>>
>> I've tried the following:
>> - Added a dummy-interface to dom0 with 192.168.1.10.
>> - Added e.g. 192.168.1.11 to the vif-config in the domain-config-file of
>> a domU.
>> - Added a dummy-interface to a domU with e.g. 192.168.1.11. I tried the
>> config with no gateway, with the same gateway as the "normal" interface
>> (public ip) and with the gateway 192.168.1.10
>>
>> No luck so far.
>>
>> Any tips, tricks, hints?
>>
>>
>> Regards
>>
>> Joerg Schoppet
>>
>> _______________________________________________
>> 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


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

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