Date: Mon, 24 Aug 2009 08:59:01 -0700 From: Bakul Shah <bakul@bitblocks.com> To: martinko <gamato@users.sf.net> Cc: freebsd-emulation@freebsd.org Subject: Re: Automagic bridged networking with QEMU (tap) Message-ID: <20090824155902.0C9675B30@mail.bitblocks.com> In-Reply-To: Your message of "Mon, 24 Aug 2009 09:34:39 %2B0200." <h6tfqf$kb0$1@ger.gmane.org> References: <200908232215.n7NMFqkK007704@triton8.kn-bremen.de> <20090823233419.790325B2E@mail.bitblocks.com> <h6tfqf$kb0$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 24 Aug 2009 09:34:39 +0200 martinko <gamato@users.sf.net> wrote: > > I was thinking of using autobridge but eventually decided not to because: > - Putting an interface into bridge has certain drawbacks like disabling > checksum offloading. So I'd prefer not to bridge until I have to. > - I'm not sure whether it's generally acceptable to autobridge all tap* > devices. I might be OK with it now but I may not in the future and/or > other users may have different uses of tap* devices. > > Problem with your devfs.conf is that it's static and thus the solution > is sort of halfway between not using autobridging at all (precreating a > few tap? devices and bridging them in rc.conf, like I found in many > examples on the internet). Again, it may be OK for you and me but I was > trying to find a more general solution. There is no one solution that works for all. In any case we have to touch too many files and things like devfs.conf and devfs.rules are confusing so what would be most useful is a "wizard" script that asks some questions and modifies appropriate files to configure qemu. > Also, I'm not sure how is it possible that it works for you at all. I > tried "perm tap* 0660" but it did not work and then I learned > devfs.conf is only good for interfaces available at boot. It works fine for me. I think you have to use specific tap devices and not tap*. If you want the same behavior for additional tap devices created at run time, devfs.conf won't do.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090824155902.0C9675B30>