From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lxrsc-0003j0-St for qemu-devel@nongnu.org; Sat, 25 Apr 2009 20:05:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lxrsc-0003ie-4j for qemu-devel@nongnu.org; Sat, 25 Apr 2009 20:05:58 -0400 Received: from [199.232.76.173] (port=41702 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lxrsb-0003ib-Qj for qemu-devel@nongnu.org; Sat, 25 Apr 2009 20:05:57 -0400 Received: from qw-out-1920.google.com ([74.125.92.147]:63485) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lxrsb-0002On-8R for qemu-devel@nongnu.org; Sat, 25 Apr 2009 20:05:57 -0400 Received: by qw-out-1920.google.com with SMTP id 4so1211244qwk.4 for ; Sat, 25 Apr 2009 17:05:56 -0700 (PDT) MIME-Version: 1.0 Date: Sat, 25 Apr 2009 19:05:56 -0500 Message-ID: <543f83c70904251705p2b963ddbye632a4ea5419e3eb@mail.gmail.com> From: "Andres E. Rodriguez Lazo" Content-Type: multipart/alternative; boundary=0015175cd54e6be661046869fed3 Subject: [Qemu-devel] Qemu Multicast Bug?? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --0015175cd54e6be661046869fed3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 --0015175cd54e6be661046869fed3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit 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
--0015175cd54e6be661046869fed3--