mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ignacy Gawedzki <Ignacy.Gawedzki@lri.fr>
To: usagi-users@linux-ipv6.org
Cc: David Stevens <dlstevens@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: (usagi-users 02872) Re: IPv6 multicast in 2.4.25 broken?
Date: Wed, 31 Mar 2004 17:57:52 +0200	[thread overview]
Message-ID: <20040331175752.A16121@qubit.lri.fr> (raw)
In-Reply-To: <20040331220129.d245fc9%hibi665@oki.com>; from hibi665@oki.com on Wed, Mar 31, 2004 at 10:01:29PM +0900

On Wed, Mar 31, 2004 at 10:01:29PM +0900, thus spake Takashi Hibi:
> Isn't it related to the patch (usagi-users 02627)?
> http://www2.linux-ipv6.org/ml/usagi-users/msg02626.html
> 
> If the socket is bound to non-multicast address, it can't receive
> multicast packets.

This is why it doesn't work anymore, as it shouldn't have in the first
place.  Thanks for pointing this out.  I did not know that source
address selection is automatic, depending on the multicast address
prefix (ff05::/16, ff02::/16, etc) and the IPV6_MULTICAST_IF option, so
I instinctively did bind the socket to the unicast address and not the
multicast address.

Now it seems to work like a charm. =)

Thanks,

Ignacy

-- 
To err is human, to moo bovine.

      parent reply	other threads:[~2004-03-31 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 18:52 Ignacy Gawedzki
     [not found] ` <OFE1BE522F.02DB03E7-ON88256E67.00767AD5-88256E67.0077576D@us.ibm.com>
2004-03-31  8:40   ` (usagi-users 02870) " Ignacy Gawedzki
     [not found]     ` <20040331220129.d245fc9%hibi665@oki.com>
2004-03-31 15:57       ` Ignacy Gawedzki [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=20040331175752.A16121@qubit.lri.fr \
    --to=ignacy.gawedzki@lri.fr \
    --cc=dlstevens@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=usagi-users@linux-ipv6.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
all inboxes | Powered by JetHome®