[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 02915) Re: IPv6 Multicast on recent Linux Kernels
- To: usagi-users@xxxxxxxxxxxxxx
- Subject: (usagi-users 02915) Re: IPv6 Multicast on recent Linux Kernels
- From: Pavlin Radoslavov <pavlin@xxxxxxxx>
- Date: Tue, 20 Apr 2004 01:20:52 -0700
- In-reply-to: Message from Stig Venaas <Stig.Venaas@uninett.no> of "Thu, 15 Apr 2004 00:08:42 +0200." <20040414220842.GC15457@sverresborg.uninett.no>
- Reply-to: usagi-users@xxxxxxxxxxxxxx
- Resent-date: Tue, 20 Apr 2004 17:33:02 +0900
- Resent-from: sekiya@xxxxxxxxxxxxxx
- Resent-message-id: <200404201733.FMLAAB24760.usagi-users@linux-ipv6.org>
- Resent-to: usagi-users@xxxxxxxxxxxxxx (moderated)
> > > The symptoms are that it is unable to join Multicast groups, however
> > > if there is another machine on the subnet, already a member of the
> > > group, then it picks up the packets ok. Linux will also will remain a
> > > member of the multicast group, even with the other machine leaves.
> >
> > Are you running a multicast router? Do the other machines on the network
> > have the same ICMPv6 "type" code for reports (206) ? This number isn't
> > assigned by IANA last I checked, so implementations had to choose a
> > number--
> > won't interoperate if they aren't using the same one.
>
> IANA now lists it! It says:
> 143 Version 2 Multicast Listener Report [RFC-vida-mld-v2-08.txt]
>
> I think this must have happened just a few days ago. So perhaps we can
> change then? Some implementations are already using 143. Don't know what
> FreeBSD does.
By looking into the KAME's CVS repository, it appears that until few
days ago the value was 206.
However, on Apr 15, 2004 the value was changed to the one defined by
IANA (143).
It looks like the change has happened the same day the value has
been officially assigned :)
Pavlin