netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: netdev <netdev@oss.sgi.com>
Subject: [Fwd: Receiving MLDv1 reports in a daemon]
Date: Tue, 16 Mar 2004 07:04:13 -0800	[thread overview]
Message-ID: <4057176D.8050206@us.ibm.com> (raw)

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

Ah, sorry, my bad. I cc'd netdev in my first response
but cut down the actual post.

thanks,
Nivedita


-------- Original Message --------
Subject: Receiving MLDv1 reports in a daemon
Date: Tue, 16 Mar 2004 16:38:25 +0530 (IST)
From: Madhavi <madhavis@sasken.com>
To: <linux-kernel@vger.kernel.org>


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: file:///C|/DOCUME%7E1/NIVEDITA/LOCALS%7E1/TEMP/nsmail-1.txt --]
[-- Type: text/plain, Size: 1050 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.

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


             reply	other threads:[~2004-03-16 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 15:04 Nivedita Singhvi [this message]
2004-03-16 19:06 ` [Fwd: Receiving MLDv1 reports in a daemon] David Stevens

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=4057176D.8050206@us.ibm.com \
    --to=niv@us.ibm.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).