Date: Tue, 28 Oct 2008 22:37:58 -0700 From: Bakul Shah <bakul@bitblocks.com> To: "Marc G. Fournier" <freebsd@hub.org> Cc: freebsd-net@freebsd.org Subject: Re: Problem with Bridging ... and bge devices under FreeBSD 7.x? Message-ID: <20081029053758.C638C5B46@mail.bitblocks.com> In-Reply-To: Your message of "Wed, 29 Oct 2008 01:38:38 -0300." <7762927ECAFF08B969F9E5A0@ganymede.hub.org> References: <E2674DE9A502AD6C5FA5E5DF@ganymede.hub.org> <20081029041428.DC80C5B46@mail.bitblocks.com> <7762927ECAFF08B969F9E5A0@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 29 Oct 2008 01:38:38 -0300 "Marc G. Fournier" <freebsd@hub.org> wrote:
>
> I only have one VM running on one server ...
Ok.
Here are some debugging suggestions.
- /etc/sysctl.conf should have the following;
net.link.tap.user_open=1
net.link.tap.up_on_open=1
run sysctl manually to set these.
- if you are running qemu as user foo (and not root) you will need
own tap0 foo:foo
in /etc/devfs.conf and do /etc/rc.d/devfs restart.
- start qemu with -monitor stdio as this will give you a
command line interface to qemu. Now you can type
info network
to see what qemu sees. You should see something like
VLAN 0 devices:
tap: ifname=tap0 setup_script=/usr/local/etc/qemu-ifup
rtl8139 pci macaddr=52:54:00:d2:56:03
- I no longer remember if qemu-ifup is needed but without it
you may need to manually bring up tap0.
- tcpdump on tap0 to see if ping packets (sent from the VM)
get through. Next tcpdump on bridge0. Next tcpdump on bge0.
I'd still like to see the topology and ip addresses on
various interfaces.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081029053758.C638C5B46>