trouble debugging xen networking problem.

[Michael Litchard <michael%schmong.org@localhost>]

I can't ping from or to one of my domUs. Could someone help me
troubleshoot this?

This is the relevant information

briarpatch# /sbin/ifconfig -a
xennet0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
        enabled=0
        address: 00:16:3e:54:3a:f4
        inet 10.0.0.2 netmask 0xfffffff5 broadcast 10.0.0.10
        inet6 fe80::216:3eff:fe54:3af4%xennet0 prefixlen 64 scopeid 0x1
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2

rtk0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST>
mtu 1500
        address: 00:00:e8:93:9f:cd
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::200:e8ff:fe93:9fcd%rtk0 prefixlen 64 scopeid 0x1
nfe0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        
capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
        enabled=0
        address: 00:1e:8c:a4:1b:fd
        media: Ethernet autoselect (none)
        status: no carrier
        inet 10.0.0.1 netmask 0xfffffff5 broadcast 10.0.0.11
        inet6 fe80::21e:8cff:fea4:1bfd%nfe0 prefixlen 64 scopeid 0x2
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
bridge0: flags=41<UP,RUNNING> mtu 1500
bridge1: flags=41<UP,RUNNING> mtu 1500
xvif1.0: flags=8963<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,SIMPLEX,MULTICAST>
mtu 1500
        capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
        enabled=0
        address: 00:16:3e:55:3a:f4
        inet6 fe80::216:3eff:fe55:3af4%xvif1.0 prefixlen 64 scopeid 0x6

/usr/pkg/etc/xen/honeypot

#  -*- mode: python; -*-
#============================================================================
# Python configuration setup for 'xm create'.
# This script sets the parameters used when a domain is created using
'xm create'.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#============================================================================

#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/sys/xen/diskfiles/domU6/netbsd-XEN3_DOMU.gz"
#kernel = "/usr/pkg/xen3-kernel/domU1/netbsd-INSTALL_XEN3_DOMU.gz"

# Initial memory allocation (in megabytes) for the new domain.
memory = 384

# A name for your domain. All domains must have different names.
name = "honeypot"

#----------------------------------------------------------------------------
# network configuration.
# The mac address is optionnal, it will use a random one if not specified.
# The mac address is optionnal, it will use a random one if not specified.
# By default we create a bridged configuration; when a vif is created
# the script /usr/pkg/etc/xen/scripts/vif-bridge is called to connect
# the bridge to the designated bridge (the bridge should already be up)
#vif = [ '', bridge=bridge0' ]
vif = [ 'bridge=bridge1,ip=10.0.0.3 netmask 255.255.254,model=ne2k_pci' ]

#it's possible to use a different script when the vif is created;
# for example to use a routed setup instead of bridged:
#vif = [ 'mac=00:16:3c:00:00:11, ip=10.0.0.1 netmask 255.255.255.0,
script=vif-ip' ]

#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
# For NetBSD guest DEV doesn't matter, so we can just use increasing numbers
# here. For linux guests you have to use a linux device name (e.g. hda1)
# or the corresponding device number (e.g 0x301 for hda1)

disk = [ 'file:/sys/xen/diskfiles/domU6/honeypot.img,0x1,w' ]
#disk = ['phy:/dev/wd0i,0x1,w']

#----------------------------------------------------------------------------
# Boot parameters (e.g. -s, -a, ...)
extra = ""

#============================================================================


The one thing I did try was to start a working vm, and compare the
output ifconfig -a.
I didn't see anything different or wrong.

Any ideas on how to proceed?


Michael Litchard