netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Borst <mark@borst.org>
To: Brian Haley <Brian.Haley@hp.com>
Cc: netdev@oss.sgi.com
Subject: Re: node-local multicast issues
Date: Thu, 11 Nov 2004 12:18:24 +0200	[thread overview]
Message-ID: <1100168304.24452.5.camel@mn-2> (raw)
In-Reply-To: <4192701A.3090908@hp.com>

On Wed, 2004-11-10 at 14:46 -0500, Brian Haley wrote:
> Mark Borst wrote:
> 
> > On another note: 'ping6 ff02::1' gives "connect: Invalid argument" on
> > linux.
> 
> You've got to use -I with that, maybe ping6 could give a hint.

I found that too. With -I it works fine.

> 
> > The only implementation that gives me replies is Solaris.
> 
> My trusty Tru64 UNIX box works as well :)

Good ;) My testing wasn't anything near exhaustive, just a short test ;)


-- 
Mark Borst
Researcher
Network and Protocols Group
Tampere University of Technology, Finland

  reply	other threads:[~2004-11-11 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09 10:21 node-local multicast issues Mark Borst
2004-11-09 23:21 ` David Stevens
2004-11-10 14:17   ` Mark Borst
2004-11-10 19:46     ` Brian Haley
2004-11-11 10:18       ` Mark Borst [this message]
2004-11-11 11:21     ` Mark Borst

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=1100168304.24452.5.camel@mn-2 \
    --to=mark@borst.org \
    --cc=Brian.Haley@hp.com \
    --cc=netdev@oss.sgi.com \
    /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).