From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
Cc: "'David Stevens'" <dlstevens@us.ibm.com>,
"'Netdev'" <netdev@vger.kernel.org>
Subject: Re: Multicast problem
Date: Tue, 16 Oct 2007 13:13:24 -0700 [thread overview]
Message-ID: <20071016131324.0bad17a5@freepuppy.rosehill> (raw)
In-Reply-To: <002701c81030$31908a90$04ac10ac@Jocke>
On Tue, 16 Oct 2007 22:07:35 +0200
"Joakim Tjernlund" <joakim.tjernlund@transmode.se> wrote:
> > -----Original Message-----
> > From: David Stevens [mailto:dlstevens@us.ibm.com]
> > Sent: den 16 oktober 2007 21:46
> > To: Joakim Tjernlund
> > Cc: 'Netdev'; netdev-owner@vger.kernel.org
> > Subject: RE: Multicast problem
> >
> > > dev_mcast and igmp looks:
> > > root@Challenger:/proc/net# m dev_mcast
> > > 1 eth0 1 0 01005e000001
> > > 2 eth1 1 0 01005e000001
> >
> > These are the hardware multicast addresses for
> > 224.0.0.1 (so, correct).
> >
> > > root@Challenger:/proc/net# m igmp
> > > Idx Device : Count Querier Group Users
> > Timer Reporter
> > > 1 eth0 : 1 V3
> > > E0000001 1 0:00000000 0
> > > 2 eth1 : 1 V2
> > > E0000001 1 0:00000000 0
> > > 4 lo : 0 V3
> > > E0000001 1 0:00000000 0
> >
> > ...and these are the group memberships for 224.0.0.1, so
> > also correct. This should receive and answer pings to 224.0.0.1
> > as long as you don't have ICMP set to ignore broadcasts. You should
> > not need to put the device in promiscuous mode for a ping of
> > 224.0.0.1 to work, so if you do, then you have a driver, device
> > or switch problem.
> > None of these interfaces have memberships in the OSPF groups,
> > so if you had OSPF running when you did this, it didn't join.
> >
> > +-DLS
> >
>
> OK, so from all this and earlier mail I think that the device driver don't
> receive multicast pkgs. Tomorrow I will try the real OSPF test case with
> promisc mode enabled, se if that works. If so, it means there is
> a bug in the drivers(ucc_geth.c) set_multicast_list() function.
>
> Thank you for helping me to narrow it down.
>
> Jocke
You can test multicast easily standalone with iperf:
http://dast.nlanr.net/Projects/Iperf/#multicast
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-10-16 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 16:49 Multicast problem Joakim Tjernlund
2007-10-16 17:04 ` David Stevens
2007-10-16 17:31 ` Joakim Tjernlund
2007-10-16 19:46 ` David Stevens
2007-10-16 20:07 ` Joakim Tjernlund
2007-10-16 20:13 ` Stephen Hemminger [this message]
2007-10-16 20:57 ` Joakim Tjernlund
2007-10-16 18:54 ` Joakim Tjernlund
2007-10-16 19:40 ` David Stevens
-- strict thread matches above, loose matches on Subject: below --
2007-10-16 21:15 Joakim Tjernlund
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=20071016131324.0bad17a5@freepuppy.rosehill \
--to=shemminger@linux-foundation.org \
--cc=dlstevens@us.ibm.com \
--cc=joakim.tjernlund@transmode.se \
--cc=netdev@vger.kernel.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