odd qemu issue and networking

[Zane C.B.]

On Thu, 9 Aug 2007 11:21:23 -0400
"Zane C.B." <vvelox at vvelox.net> wrote:

> qemu -hda trixbox.img -net nic -net tap,fd=/dev/tap0
> 
> Results on garbage being printed out when ever any network IO takes
> place.
> 
> nve0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
> mtu 1500 inet 192.168.15.2 netmask 0xffffff00 broadcast 192.168.2.2
>         inet 192.168.15.4 netmask 0xffffffff broadcast 192.168.15.4
>         inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
>         ether 00:30:18:a0:22:97
>         media: Ethernet autoselect (100baseTX
> <full-duplex,flag0,flag1>) status: active
> tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
> mtu 1500 ether 00:bd:38:5b:14:00
> bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         ether 7a:fb:12:be:28:87
>         id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
>         maxage 20 holdcnt 6 proto stp maxaddr 100 timeout 1200
>         root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0
>         member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
>         member: nve0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>

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?