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

[Xen-users] Dom1 can send, but not receive ?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Dom1 can send, but not receive ?
From: Oliver Jucknath <oliver@xxxxxxxxxxx>
Date: Tue, 10 Oct 2006 16:26:03 +0200
Delivery-date: Tue, 10 Oct 2006 07:25:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.5 (X11/20060719)
Hi,

I have set up my Xen 3.0.2 on a 64 bit gentoo using bridging, because I
want to have a seperate IP adress for each domU. I can send out tcp
packets from my dom1, but I don't get their reply. I can ping the dom0
from my dom1 and vice versa - no problem there. If I ping from my dom1
to an external internet adress, I can see (using tcpdump) the outgoing
packets in the dom1:eth0, the xenbr0 and the response coming back to the
xenbr0 (and my dom0:eth0), but no such packets in the dom1:eth0. If I
ping the dom1 from the outside I can see the packets received by xenbr0,
but not by the dom1:eth0. Any ideas ?

thank you very much,

Oliver

Here my /etc/xen/base config file:

kernel = "/boot/vmlinuz-xen-domU"
memory = 512
name = "base"
vcpus = 4 # make your domain a 4-way
disk = ['phy:/dev/hda5,sda1,w','phy:/dev/hda6,sda2,w']
root = "/dev/sda1 ro"
vif = [ 'bridge=xenbr0' ]

my /etc/xen/xend-config.sxp file:

(xend-relocation-server yes)
(xend-relocation-hosts-allow '^localhost$')
(network-script network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)

my dom0 network config:

config_eth0=("85.14.220.63 netmask 255.255.248.0 brd 85.14.223.255")
routes_eth0=("default via 85.14.216.1")

my dom1 network config:

config_eth0=("85.14.217.42 netmask 255.255.248.0 brd 85.14.223.255")
routes_eth0=("default via 85.14.216.1")

my .config file for the dom0 kernel | grep XEN | grep -v \#:

CONFIG_X86_64_XEN=y
CONFIG_X86_XEN_GENAPIC=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN=y
CONFIG_XEN_INTERFACE_VERSION=0x00030101
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_PASS=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_NETDEV_LOOPBACK=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DISABLE_SERIAL=y
CONFIG_XEN_SYSFS=m

my .config file for the domU kernel | grep XEN | grep -v \#:

CONFIG_X86_64_XEN=y
CONFIG_X86_XEN_GENAPIC=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN=y
CONFIG_XEN_INTERFACE_VERSION=0x00030101
CONFIG_XEN_UNPRIVILEGED_GUEST=y
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DISABLE_SERIAL=y




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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Dom1 can send, but not receive ?, Oliver Jucknath <=