RE: [Xen-users] NAT with static ip configuration doesn't work

["Dustin Henning" <Dustin.Henning@xxxxxxxxxxx>]

        With Zhi trying to run Xen 3.3.0, he won't be using native support
in any operating system.  Is there any reason it would really matter whether
or not there is native dom0 support for the kernel included with the OS once
one compiles their own Xen and xen-kernel anyway?  I would offer
troubleshooting suggestions, but I have no experience with nat on Xen.
        Dustin

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Franz Von Hahn
Sent: Wednesday, October 22, 2008 17:13
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: AW: [Xen-users] NAT with static ip configuration doesn't work

hey!

please note, that fedora 9 doesn't have native support for running F9 as
Dom0. i use centos 5.2 as dom0. it doesn't have support for the newest
hardware but it works very stable. if you want to use Fedora, please use
Fedora 8 (!) as Dom0, as it has native support for Dom0.

greets,

franz von hahn





----- Ursprüngliche Mail ----
Von: Zhi Wang <zwangf@xxxxxxxxx>
An: xen-users@xxxxxxxxxxxxxxxxxxx
Gesendet: Mittwoch, den 22. Oktober 2008, 22:35:33 Uhr
Betreff: [Xen-users] NAT with static ip configuration doesn't work

Hi, All
I have a very basic configuration as this:
Dom0 is based on Fedora core 9. Xen 3.3.0 built from source code. Dom0 is a
standard build of 2.6.18.8-xen. 
I have only one physical NIC connected to the Internet. The DomU is a ubuntu
server 8.04 HVM. I did the 
following steps to setup NAT network for my domU. 
1. change /etc/xen/xend-config.sxp to use NAT:
          (network-script network-nat)    
          (vif-script    vif-nat)

2. the configuration file for domU is as
          vif = [ 'mac=00:16:xx:xx:xx:xx, ip=10.0.0.1']

When I create the domU, the scripts will bring up two extra interfaces:
vif3.0 and tap3.0. 
That is, now I have four interface: eth0, lo, vif3.0 and tap3.0. Eth0 is
connecting to the Internet.
Everything looks ok, but I can't ping the domU from dom0. Neither can I ping
the dom0 
form domU.

>From a quick tcpdump, it seems that the virtual NIC in domU is actually
connected to 
Tap3.0. Nothing shows up in vif3.0. If I bring down vif3.0 and configure the
tap3.0 with
the router address, everything works just fine. 

I am just wondering if I have done anything wrong. Supposedly the official
release of XEN
should be able to work under such a simple configuration. Thanks

Best regards,
Zhi


      


_______________________________________________
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