Date: Thu, 9 Aug 2007 13:14:53 -0400 From: "Zane C.B." <v.velox@vvelox.net> To: "Sean C. Farley" <scf@FreeBSD.org> Cc: freebsd-emulation@FreeBSD.org Subject: Re: odd qemu issue and networking Message-ID: <20070809131453.30f90327@vixen42> In-Reply-To: <20070809115520.F68855@thor.farley.org> References: <20070809112123.08d3b09a@vixen42> <20070809124038.3756a407@vixen42> <20070809115520.F68855@thor.farley.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 9 Aug 2007 11:57:11 -0500 (CDT) "Sean C. Farley" <scf@FreeBSD.org> wrote: > On Thu, 9 Aug 2007, Zane C.B. wrote: > > > On Thu, 9 Aug 2007 11:21:23 -0400 > > "Zane C.B." <vvelox@vvelox.net> wrote: > > *snip* > > > Slightly fixed... used ifname=tap0 instead... except it kept > > bitching about not being able to open the device and was trying > > to use tap4 for some unknown reason... Thus I did a little test. > > I ran it as root. To my surprise this worked, since the user I > > was running it under had write priveledges to tap0. I have a > > group named devTAPaccess and a devfs rule setup to allow for > > members of that group to write to any tap device. The user I was > > running it under is a member of this group. > > > > Is there something I am missing there? > > Do you have these set: > net.link.tap.up_on_open=1 > net.link.tap.user_open=1 Thanks. I am now using the last one.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070809131453.30f90327>