All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andres E. Rodriguez Lazo" <andreserl@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu Multicast Implementation
Date: Thu, 23 Apr 2009 00:30:51 -0500	[thread overview]
Message-ID: <543f83c70904222230o3156bb5r37d5a213570cd523@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]

Hello Qemu Developers.

Here at work we're implementing qemu mcast networking while using
avahi-autoipd to obtain network address. The implementation of qemu
networking is the following:

*-net nic,vlan=1,macaddr=52:54:00:12:34:01,model=virtio -net
socket,vlan=1,mcast=230.0.0.1:1234*

So, while running avahi-autoipd we get his messages:
*
[root@localhost ~]# avahi-autoipd eth1*
*Found user 'avahi-autoipd' (UID 499) and group 'avahi-autoipd' (GID 499).
Successfully called chroot().
Successfully dropped root privileges.
Starting with address 169.254.2.176
Callout BIND, address 169.254.2.176 on interface eth1
Received conflicting normal ARP packet.
Callout CONFLICT, address 169.254.2.176 on interface eth1
Trying address 169.254.189.32
Callout BIND, address 169.254.189.32 on interface eth1
Received conflicting normal ARP packet.*

After sniffing ARP packets, we've realized that we're getting ARP packets
back, which screws with autoipd. I think this is due to the mcast
implementation not doing RPF. Is your mcast implementation supposed to do
RPF?? If it is, we've got ourselves a bug.

Thanks for your help,

Look forward to hear from you.


-- 
Andres E. Rodriguez Lazo (4nDr3s - RoAkSoAx)
Ubuntu Counter Project - User # 17582

[-- Attachment #2: Type: text/html, Size: 1461 bytes --]

                 reply	other threads:[~2009-04-23  5:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=543f83c70904222230o3156bb5r37d5a213570cd523@mail.gmail.com \
    --to=andreserl@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.