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@lists.xensource.com
http://lists.xensource.com/xen-users
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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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'' /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@lists.xensource.com >> http://lists.xensource.com/xen-users > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Also NAT and HVM seems to be broken/not working: http://www.nabble.com/Re%3A-nat-does-not-work-with-hvm-tf3645589.html#a10181512 So no chance to start a windows HVM on my root server :( 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'' > > /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@lists.xensource.com >>> http://lists.xensource.com/xen-users >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com >>> http://lists.xensource.com/xen-users >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Florian Engelmann wrote:> 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???Don''t use "ip=", use "mac=" and either use DHCP or set the IP address in the operating systemm itself. You can also hardcode the vif instance, and I recommend this for network monitoring reasons. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, how to hardcode a vif interface? Nico Kadel-Garcia schrieb:> Florian Engelmann wrote: >> 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??? > Don''t use "ip=", use "mac=" and either use DHCP or set the IP address > in the operating systemm itself. You can also hardcode the vif > instance, and I recommend this for network monitoring reasons. > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Florian Engelmann wrote:> Hi, > how to hardcode a vif interface? > > Nico Kadel-Garcia schrieb: >> Florian Engelmann wrote: >>> 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??? >> Don''t use "ip=", use "mac=" and either use DHCP or set the IP address >> in the operating systemm itself. You can also hardcode the vif >> instance, and I recommend this for network monitoring reasons.It should be in your documentation. You use something like: vif=[ ''vifname=xen.(whatever), mac=00:16:3E:01:(whichever), '' ] _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Nov 15, 2007 at 02:43:50PM +0000, Nico Kadel-Garcia wrote:> Florian Engelmann wrote: > >how to hardcode a vif interface? > > > >Nico Kadel-Garcia schrieb: > >>Florian Engelmann wrote: > >>>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??? > >>Don''t use "ip=", use "mac=" and either use DHCP or set the IP address > >>in the operating systemm itself. You can also hardcode the vif > >>instance, and I recommend this for network monitoring reasons. > It should be in your documentation. You use something like: > > vif=[ ''vifname=xen.(whatever), mac=00:16:3E:01:(whichever), '' ]I think I remember that I also needed the ip=10.0.1.1 argument. Not to initialise the network in the domU (I do this via ifconfig, route) but the get the IP address of the dom0 (=gateway) in the 10.x.x.x network. Specifying ip=10.0.1.1 seems to ensures that dom0 gets the address 10.0.1.128 whereas it otherwise could get 10.0.2.128 or whatever and makes it impossible to use a not dhcp setup with routing. At least this is what I vague remember ... Jens _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jens Seidel wrote:> On Thu, Nov 15, 2007 at 02:43:50PM +0000, Nico Kadel-Garcia wrote: > >> Florian Engelmann wrote: >> >>> how to hardcode a vif interface? >>> >>> Nico Kadel-Garcia schrieb: >>> >>>> Florian Engelmann wrote: >>>> >>>>> 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??? >>>>> >>>> Don''t use "ip=", use "mac=" and either use DHCP or set the IP address >>>> in the operating systemm itself. You can also hardcode the vif >>>> instance, and I recommend this for network monitoring reasons. >>>> >> It should be in your documentation. You use something like: >> >> vif=[ ''vifname=xen.(whatever), mac=00:16:3E:01:(whichever), '' ] >> > > I think I remember that I also needed the ip=10.0.1.1 argument. Not to > initialise the network in the domU (I do this via ifconfig, route) but > the get the IP address of the dom0 (=gateway) in the 10.x.x.x network. > > Specifying ip=10.0.1.1 seems to ensures that dom0 gets the address > 10.0.1.128 whereas it otherwise could get 10.0.2.128 or whatever and > makes it impossible to use a not dhcp setup with routing. > > At least this is what I vague remember ... > > Jens >This is definitely not the case. I recently built about 40 Xen guest domains with the MAC address and vifnames hardcoded, and all other network setttings done by the guest OS. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nico Kadel-Garcia schrieb:> Florian Engelmann wrote: >> Hi, >> how to hardcode a vif interface? >> >> Nico Kadel-Garcia schrieb: >>> Florian Engelmann wrote: >>>> 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??? >>> Don''t use "ip=", use "mac=" and either use DHCP or set the IP >>> address in the operating systemm itself. You can also hardcode the >>> vif instance, and I recommend this for network monitoring reasons. > It should be in your documentation. You use something like: > > vif=[ ''vifname=xen.(whatever), mac=00:16:3E:01:(whichever), '' ] > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersOk, one even more stupid question - my documentation was not build because of latex was missing... is there any documentation in the internet? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Florian Engelmann wrote:> Nico Kadel-Garcia schrieb: >> Florian Engelmann wrote: >>> Hi, >>> how to hardcode a vif interface? >>> >>> Nico Kadel-Garcia schrieb: >>>> Florian Engelmann wrote: >>>>> 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??? >>>> Don''t use "ip=", use "mac=" and either use DHCP or set the IP >>>> address in the operating systemm itself. You can also hardcode the >>>> vif instance, and I recommend this for network monitoring reasons. >> It should be in your documentation. You use something like: >> >> vif=[ ''vifname=xen.(whatever), mac=00:16:3E:01:(whichever), '' ] >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > > Ok, one even more stupid question - my documentation was not build > because of latex was missing... is there any documentation in the > internet?Ahh. That''s part of why I like installing packages, rather than building from source without compelling reasons. Any reason not to install LaTeX? Or the tetex software bundle that contains it? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users