Re: Receiving MLDv1 reports in a daemon

Re: Receiving MLDv1 reports in a daemon

[Nivedita Singhvi]

Madhavi wrote:

> I am trying to incorporate the functionality of MLDv1 into a daemon. This
> would be in addition to the functionality already supported by the kernel
> IPv6 stack.

The correct mailing list to post to in this case
would be netdev@oss.sgi.com, the networking development
mailing list (i.e. the place to catch the MLD author,
for instance ;)).

thanks,
Nivedita

Receiving MLDv1 reports in a daemon

[Madhavi]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1043 bytes --]


Hi

I am trying to incorporate the functionality of MLDv1 into a daemon. This
would be in addition to the functionality already supported by the kernel
IPv6 stack.

I am opening a raw socket with proto IPPROTO_ICMPV6 in my daemon process.
When I am sending an MLDv1 report from the host, the Router is able to
receive the report. But, I am not able to receive it over the socket.

I have checked the kernel code and found that the kernel is sending reports
only if the group address being reported is added to the device multicast
list. Since I won't know the group address in advance, I can't add it to
the device multicast list.

Is there any other way to get the MLDv1 reports to my daemon. Any solution
to this problem would be very helpful to me.

Thanks & regards
Madhavi.

Madhavi Suram
Senior Software Engineer
Customer Delivery / Networks
Sasken Communication Technologies Limited
139/25, Ring Road, Domlur
Bangalore - 560071 India
Email: madhavis@sasken.com
Tel: + 91 80 5355501 Extn: 8062
Fax: + 91 80 5351133
URL: www.sasken.com


[-- Attachment #2: Type: text/plain, Size: 1049 bytes --]

***********************************************************************

********************************************************************

SASKEN BUSINESS DISCLAIMER

This message may contain confidential, proprietary or legally Privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, Disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.

***********************************************************************

Re: Receiving MLDv1 reports in a daemon

[David Stevens]

[-- Attachment #1: Type: text/plain, Size: 738 bytes --]







madhavis@sasken.com wrote on 03/16/2004 08:15:25 PM:

> Is there any other way to get the MLDv1 reports to my daemon. Any
solution
> to this problem would be very helpful to me.

As I responded before, though you may not have seen it, you need to put
the device in "multicast promiscuous mode" by setting the IFF_ALLMULTI
interface flag (SIOCSIFFLAGS). Then you should receive all multicasts for
all groups (and all protocols) sent on that network. If you create the
socket as you described, your program should receive all ICMPv6
multicasts sent to any group.

In MLDv2, it's much easier. All reports are sent to the "all multicast
routers" multicast address, so you can simply join that group.

                              +-DLS

[-- Attachment #2: Type: text/html, Size: 922 bytes --]