mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Dillow <dave@thedillows.org>
To: Roger Luethi <rl@hellgate.ch>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Multicast Driver Testing Quick How-To v 0.3 [was: Re: List of pending v2.4 kernel bugs]
Date: 09 Aug 2004 23:48:52 -0400	[thread overview]
Message-ID: <1092109732.15778.22.camel@ori.thedillows.org> (raw)
In-Reply-To: <20040805133359.GA15129@k3.hellgate.ch>

On Thu, 2004-08-05 at 09:33, Roger Luethi wrote:

> We haven't joined the next group yet, so there should be no answer:
> 
> tester# ping -r -I eth0 -t 1 -c 2 224.1.1.37
> 
> Use packet sniffer to confirm that target is not seeing the request
> (use -p option for tcpdump or tethereal to prevent promiscuous mode)
> 
> Now join the group (Ethernet level):
> 
> target# ip maddr add 01:00:5e:01:01:25 dev eth0
> 
> tester# ping -r -I eth0 -t 1 -c 2 224.1.1.37
> 
> Use packet sniffer to confirm that target is seeing the request now.

Some versions of tcpdump/libpcap will enable all-multicast mode
regardless of options given and user. This bit me on RedHat 9 using
libpcap 0.7.2 and tcpdump 3.7.2 while testing the typhoon driver.

Dave

      reply	other threads:[~2004-08-10  3:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 14:26 List of pending v2.4 kernel bugs Marcelo Tosatti
2004-07-20 19:57 ` Zwane Mwaikambo
2004-07-20 19:32   ` Marcelo Tosatti
2004-07-21 11:23 ` Roger Luethi
2004-07-30 15:56   ` Marcelo Tosatti
2004-07-30 17:08     ` Jeff Garzik
2004-07-30 17:29       ` Roger Luethi
2004-07-30 18:10         ` Jeff Garzik
2004-07-30 18:20           ` Roger Luethi
2004-08-05 13:33             ` Multicast Driver Testing Quick How-To v 0.3 [was: Re: List of pending v2.4 kernel bugs] Roger Luethi
2004-08-10  3:48               ` David Dillow [this message]

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=1092109732.15778.22.camel@ori.thedillows.org \
    --to=dave@thedillows.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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

all inboxes | Powered by JetHome®