Re: NetBSD in an HVM instance can't see outside world

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

rtk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:00:e8:93:9f:cd
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 192.168.1.106 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::200:e8ff:fe93:9fcd%rtk0 prefixlen 64 scopeid 0x1
nfe0: flags=8902<BROADCAST,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
        status: no carrier
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
xvif13.0: flags=8923<UP,BROADCAST,NOTRAILERS,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
        enabled=0
        address: 00:16:3d:01:00:13
        inet6 fe80::216:3dff:fe01:13%xvif13.0 prefixlen 64 scopeid 0x11
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        address: f2:0b:a4:ea:df:03
        media: Ethernet autoselect
        inet6 fe80::f00b:a4ff:feea:df03%tap0 prefixlen 64 scopeid 0x12

tap is up and running, how can I verify it's added to bridge0 (what am
I looking for)?


On Wed, Sep 3, 2008 at 10:34 AM, Manuel Bouyer 
<bouyer%antioche.eu.org@localhost> wrote:
> On Wed, Sep 03, 2008 at 10:19:46AM -0700, Michael Litchard wrote:
>> Whether I try to use dhcp or manually configure an ip, I can neither
>> ping, nor be pinged.
>>
>> Here's my config file. Could someone help me troubleshoot?
>> #============================================================================
>> # 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 = "/usr/pkg/lib/xen/boot/hvmloader"
>>
>> builder='hvm'
>>
>> # Initial memory allocation (in megabytes) for the new domain.
>> memory = 256
>>
>> # A name for your domain. All domains must have different names.
>> name = "hvm-netbsd"
>>
>> #Network interface. By default emules a realtek 8139. For a NetBSD guest you
>> # have to disable re(4) and let rtk attach to use it.
>> # ne2k_pci emulates a pci ne2000 clone; this his cpu-hungry in dom0
>> # pcnet emulates a AMD PCnet-PCI controller; but it corrupts packets with
>> # pcn(4) under NetBSD.
>> #vif = [ 'mac=00:16:3e:00:00:13, bridge=bridge0, type=ioemu, model=ne2k_pci' 
>> ]
>> #vif = [ 'mac=00:16:3e:00:00:13, bridge=bridge0, type=ioemu, model=pcnet' ]
>> vif = [ 'mac=00:16:3d:00:00:13, bridge=bridge0, type=ioemu' ]
>
> This should create a tap interface in the dom0, in addition to the usual
> xvif. Please check that the tap interface is up, and was added to bridge0
>
> --
> Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>     NetBSD: 26 ans d'experience feront toujours la difference
> --
>