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 3.1 networking questions

To: Florian Engelmann <mailinglists@xxxxxxxx>
Subject: Re: [Xen-users] Xen 3.1 networking questions
From: Stephan Seitz <s.seitz@xxxxxxxxxxxx>
Date: Thu, 15 Nov 2007 13:15:41 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 15 Nov 2007 04:16:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <473C2CCE.1030303@xxxxxxxx>
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>
Organization: netz-haut e.K.
References: <473BEFC3.3030901@xxxxxxxx> <473C1C4B.2080404@xxxxxxxx> <473C2CCE.1030303@xxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (X11/20071022)
Florian Engelmann schrieb:
> Ok at the moment I use NAT and i can connect to the internet, but I
> always have to change the router. Xen starts a new vifx.0 interface
> which is my domUs router. The IP changes every time. How to fix that???
> 
> here are my configs:
> xend-config.sxp (dhcp does not work anyway):
> (network-script 'network-nat dhcp=yes')
> (vif-script vif-nat)

> domU.cfg:
> vif  = [ 'ip=10.0.0.100' ]
> ip = '10.0.0.100'
> netmask = '255.0.0.0'
> gateway = '10.0.0.1'

You should define a mac adress at your vif line like
vif = [ 'mac=00:16:3E:52:8E:37' ]
This prevents NIC reassigning.

I assume, the ip, netmask and gateway parameter are deprecated, but i'm not
really sure about that.
I've never tried dhcp, but in former Xen Version (2.x) there has been
dhcp = 'dhcp'
available in the domU's cfg.



> /etc/network/interfaces
> auto eth0
> #iface eth0 inet dhcp
> iface eth0 inet static
> address 10.0.0.100
> #gateway 10.0.0.254
> netmask 255.0.0.0
> 
> 
> the gateway is then set by xen to 10.0.0.1 but i have to change it with:
> route del default gw 10.0.0.1
> and
> route add default gw 10.0.x.xxx
> 
> while 10.0.x.xxx is the ip of dom0s vifx.0
> 
> strange....
> 
> 
> 
> Florian Engelmann schrieb:
>> I just found this guide:
>> http://de.xen-forum.net/viewtopic.php?t=479&highlight=1und1
>>
>> But it is not working for me. I searched now 2 days but there is no
>> real documentation of networking in xen 3.1 out there. I would like to
>> enable NAT networking and dhcp on the privates LAN side. But I don't
>> know how to setup xen-NAT at all and how to enable xen-dhcp. Isn't
>> there any documentation? Is xen open source still in development or
>> stopped it after citrix bought xensource?
>>
>> Florian Engelmann schrieb:
>>> Hi,
>>> after hours of testing my last hope is the mailinglist. I have got a
>>> root server (www.1und1.com) and I just installed debian etch amd64 on
>>> it. I maanged to compile xen 3.1 from source and also my 1st HVM
>>> virtual guest is running fine (Windows 2003). But 1und1 uses a
>>> absolut strange network setup I have never seen before and I do not
>>> understand why it is working at all!?!
>>> These are the settings the root Sever is getting with DHCP (and they
>>> are working...):
>>>
>>> ifconfig:
>>> eth0      Link encap:Ethernet  HWaddr 00:19:99:0D:CD:05
>>>          inet addr:87.106.189.xxx  Bcast:87.106.189.203 
>>> Mask:255.255.255.255
>>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>          RX packets:15579 errors:0 dropped:0 overruns:0 frame:0
>>>          TX packets:15257 errors:0 dropped:0 overruns:0 carrier:0
>>>          collisions:0 txqueuelen:1000
>>>          RX bytes:1026640 (1002.5 KiB)  TX bytes:5709824 (5.4 MiB)
>>>          Interrupt:16 Base address:0x6000
>>>
>>> route -n:
>>> Kernel IP routing table
>>> Destination     Gateway         Genmask         Flags Metric Ref   
>>> Use Iface
>>> 10.255.255.1    0.0.0.0         255.255.255.255 UH    0      0       
>>> 0 eth0
>>> 10.0.0.0        0.0.0.0         255.0.0.0       U     0      0       
>>> 0 eth0
>>> 0.0.0.0         10.255.255.1    0.0.0.0         UG    0      0       
>>> 0 eth0
>>>
>>> the route is also set with dhcp but after updating from sarge to etch
>>> i had to use a trick to set the route because dhcp3 did no more use
>>> the modified (by 1und1) dhcp script.
>>>
>>> So this is my /etc/network/interfaces:
>>> auto lo eth0
>>> iface lo inet loopback
>>>
>>> iface eth0 inet dhcp
>>>       up ip route add 10.255.255.1/32 dev eth0
>>>       up ip route add default via 10.255.255.1
>>>
>>> auto eth0:0
>>> iface eth0:0 inet static
>>>       address 87.106.189.xxx
>>>       netmask 255.255.255.255
>>>       broadcast 87.106.189.xxx
>>>
>>> # xxx = always the same number (yes ip and broadcast are equal...)
>>>
>>> I am abolute no network specialist but I never thought a netmask of
>>> 255.255.255.255 is valid and a client can communicate without a
>>> reachable gateway... but it works...
>>>
>>> I installed my 1st HVM guest and tried to setup networking. Bridging
>>> does not work because windows does not allow those strange network
>>> settings, so I think NAT would be the solution, wouldn't it? But I
>>> did not find any documentation about how to setup NAT with Xen 3.1.
>>> What IP do I have to setup at my dom0?
>>> Can I use eth0:x to set it up?
>>> Do I have to add any IP settings to my guest config:
>>> vif = [ 'type=ioemu, bridge=xenbr0' ] ?
>>> Should I use DHCP on the private LAN or static IPs?
>>> Can I use a 192.168.x.x network or do I have to use 10.x.x.x (I red
>>> about it)?
>>> Do you have any good links about NAT and Xen 3.1?
>>>
>>> Many thanks for your help!
>>> Greetings Florian
>>>
>>> _______________________________________________
>>> 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


-- 
Stephan Seitz
Senior System Administrator

*netz-haut* e.K.
multimediale kommunikation

zweierweg 22
97074 würzburg

fon: +49 931 2876247
fax: +49 931 2876248

web: www.netz-haut.de <http://www.netz-haut.de/>

registriergericht: amtsgericht würzburg, hra 5054

Attachment: s_seitz.vcf
Description: Vcard

Attachment: signature.asc
Description: OpenPGP digital signature

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