qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Hoare <jeffhoare@xtra.co.nz>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] multicast and the eepro100 driver
Date: Wed, 11 Jul 2007 20:52:41 +1200	[thread overview]
Message-ID: <46949A59.8070104@xtra.co.nz> (raw)

Hi,

I have been using a recent snapshot version of QEMU (5th July, 2007)
which has the eepro100 Ethernet driver, in order to set up a couple of
routing engines (one each in a separate QEMU VM). While I have basic
connectivity between each engine (including telnet between each) it
seems that the RIP/OSPF routing updates do not pass between them (I have
let to try a TCP based one). These are multicast UDP packets, which seem
to be output the FXP0 interface (see tcpdump below) and I can even see
them on the TAP0 interface, but they don't appear to be received by the
other VM. The two VM are connected using VDE (with different values for
HDA & macaddresses). Does the emulated Ethernet driver receive multicast
udp packets? I assumed that the virtual switch is forwarding the packets
since they are received by the TAP0 interface.

Anyway any information or light that could be shed would be appreciated.

Regards jeff

Use VDE to start QEMU---
vdeq /usr/local/bin/qemu -no-kqemu  -hda
/home/jhoare/qemu/images/juniper01.img -net
nic,vlan=0,macaddr=52:54:00:12:34:56,model=i82559er -net
nic,vlan=1,macaddr=52:54:00:12:34:57,model=i82559er -localtime
-nographic -m 96 -net vde

output from vde_switch---
vde: port/allprint
0000 DATA END WITH '.'
Port 0001 untagged_vlan=0000 ACTIVE - Unnamed Allocatable
  -- endpoint ID 0006 module tuntap      : tap0
Port 0002 untagged_vlan=0000 ACTIVE - Unnamed Allocatable
  -- endpoint ID 0007 module unix prog   : vdeqemu user=root PID=5311 
SOCK=/var/run/vde.ctl.05311-00000
Port 0003 untagged_vlan=0000 ACTIVE - Unnamed Allocatable
  -- endpoint ID 0009 module unix prog   : vdeqemu user=root PID=5327 
SOCK=/var/run/vde.ctl.05327-00000


freebsd FXP0 Interface---
root@junos01% tcpdump -i fxp0
verbose output suppressed, use <detail> or <extensive> for full protocol
decode
Listening on fxp0, capture size 96 bytes

19:32:08.503194 Out IP 192.168.254.1.router > 224.0.0.9.router: RIPv2,
Response, length: 64
19:32:08.905539 Out IP 192.168.254.1 > 224.0.0.5: OSPFv2, Hello, length: 44
19:32:18.328338 Out IP 192.168.254.1 > 224.0.0.5: OSPFv2, Hello, length: 44

TAP0 Interface (also connected to vde switch)---
listening on tap0, link-type EN10MB (Ethernet), capture size 96 bytes
19:54:19.087172 IP 192.168.254.1 > OSPF-ALL.MCAST.NET: OSPFv2, Hello,
length: 44
19:54:43.394726 IP 192.168.254.1 > OSPF-ALL.MCAST.NET: OSPFv2, Hello,
length: 44

             reply	other threads:[~2007-07-11 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11  8:52 Jeff Hoare [this message]
2007-07-11 17:11 ` [Qemu-devel] multicast and the eepro100 driver Stefan Weil
2007-12-18 14:44   ` [Qemu-devel] " Bjørn Mork
  -- strict thread matches above, loose matches on Subject: below --
2007-07-12  3:26 [Qemu-devel] " Nicolas Guilbaud

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46949A59.8070104@xtra.co.nz \
    --to=jeffhoare@xtra.co.nz \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).