From: David Dillow <dave@thedillows.org>
To: David Stevens <dlstevens@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, Jeff Garzik <jgarzik@pobox.com>,
Netdev <netdev@oss.sgi.com>, Roger Luethi <rl@hellgate.ch>
Subject: Re: [0/3] mc_filter on big-endian arch
Date: 12 Jun 2004 23:01:56 -0400 [thread overview]
Message-ID: <1087095716.4085.4.camel@ori.thedillows.org> (raw)
In-Reply-To: <OF72A3CA91.7584BEA0-ON88256EAF.001F34CA-88256EAF.001F8BE8@us.ibm.com>
On Thu, 2004-06-10 at 01:45, David Stevens wrote:
> PS - Here's a trivial program that will join a group. If you run this on
> one side, then a ping to the multicast address will work when it's in
> the group, and stop answering when it exits. There are more general
> things that have been around for years for testing-- I just threw this
> together just now. (I hope it doesn't have any bugs! :-) ) Should be
> suitable for testing hardware multicast address filters...
Thank you for sending this program; it saved me having to write my own,
and it helped me to demonstrate that multicast already works properly
under typhoon. As it turns out, my copy of tcpdump was turning on
ALL_MULTI on the interface, even with "-p", and the NIC was responding
appropriately. So the multicast packets I saw coming in were legitimate.
So, summary, typhoon multicast is OK, on both big and little endian
machines.
Roger, thanks for spurring me to finally test this.
Dave
next prev parent reply other threads:[~2004-06-13 3:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 16:53 [0/3] mc_filter on big-endian arch Roger Luethi
2004-06-07 2:29 ` David Dillow
2004-06-07 11:48 ` Roger Luethi
2004-06-07 11:59 ` Roger Luethi
2004-06-10 5:09 ` David Stevens
2004-06-10 5:45 ` David Stevens
2004-06-13 3:01 ` David Dillow [this message]
2004-06-10 10:20 ` Roger Luethi
2004-06-10 13:37 ` Dave Dillow
2004-06-10 22:47 ` David Stevens
2004-06-07 13:52 ` David Dillow
2004-06-19 21:37 ` Jeff Garzik
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=1087095716.4085.4.camel@ori.thedillows.org \
--to=dave@thedillows.org \
--cc=akpm@osdl.org \
--cc=dlstevens@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=rl@hellgate.ch \
/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).