From mailman-admin@ietf.org  Fri Aug  1 09:32:02 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14444
	for <ssm-archive@lists.ietf.org>; Fri, 1 Aug 2003 09:19:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iZYG-0002uE-3M
	for ssm-archive@lists.ietf.org; Fri, 01 Aug 2003 09:02:32 -0400
Date: Fri, 01 Aug 2003 09:02:32 -0400
Message-ID: <20030801130232.29120.65234.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: ssm-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, ssm-request@ietf.org) containing just the word
'help' in the message body, and an email message will be sent to you
with instructions.

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


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

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


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for ssm-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
ssm@ietf.org                             mifemu    
https://www1.ietf.org/mailman/options/ssm/ssm-archive%40lists.ietf.org


From exim@www1.ietf.org  Fri Aug  1 10:10:56 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23078
	for <ssm-archive@odin.ietf.org>; Fri, 1 Aug 2003 10:10:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iac2-0005G4-UA
	for ssm-archive@odin.ietf.org; Fri, 01 Aug 2003 10:10:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h71EAU1x020206
	for ssm-archive@odin.ietf.org; Fri, 1 Aug 2003 10:10:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iac2-0005Fl-Pm
	for ssm-web-archive@optimus.ietf.org; Fri, 01 Aug 2003 10:10:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17042
	for <ssm-web-archive@ietf.org>; Fri, 1 Aug 2003 09:35:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19iZy6-00006T-00
	for ssm-web-archive@ietf.org; Fri, 01 Aug 2003 09:29:14 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19iZmc-0005qi-00
	for ssm-web-archive@ietf.org; Fri, 01 Aug 2003 09:17:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iZdq-00033c-DR
	for ssm-web-archive@ietf.org; Fri, 01 Aug 2003 09:08:18 -0400
Date: Fri, 01 Aug 2003 09:08:18 -0400
Message-ID: <20030801130818.29120.63634.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: ssm-web-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, ssm-request@ietf.org) containing just the word
'help' in the message body, and an email message will be sent to you
with instructions.

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


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

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


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for ssm-web-archive@ietf.org:

List                                     Password // URL
----                                     --------  
ssm@ietf.org                             daemut    
https://www1.ietf.org/mailman/options/ssm/ssm-web-archive%40ietf.org



From exim@www1.ietf.org  Mon Aug 18 11:01:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21835
	for <ssm-archive@odin.ietf.org>; Mon, 18 Aug 2003 11:01:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19olVE-0008WB-0y
	for ssm-archive@odin.ietf.org; Mon, 18 Aug 2003 11:01:00 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7IF10Y0032739
	for ssm-archive@odin.ietf.org; Mon, 18 Aug 2003 11:01:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19olVD-0008Vy-Fr
	for ssm-web-archive@optimus.ietf.org; Mon, 18 Aug 2003 11:00:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21796
	for <ssm-web-archive@ietf.org>; Mon, 18 Aug 2003 11:00:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19olVA-0007aW-00
	for ssm-web-archive@ietf.org; Mon, 18 Aug 2003 11:00:56 -0400
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19olV8-0007a9-00
	for ssm-web-archive@ietf.org; Mon, 18 Aug 2003 11:00:55 -0400
Received: from kailash1.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T6423156538cbc58c235bc@fsnt.future.futsoft.com> for 
    <ssm-web-archive@ietf.org>; Mon, 18 Aug 2003 20:08:54 +0530
Received: from srinivask (srinivask.future.futsoft.com [10.6.4.121]) by 
    kailash1.future.futsoft.com (8.11.0/8.11.0) with SMTP id h7IKKmi02113 for 
    <ssm-web-archive@ietf.org>; Tue, 19 Aug 2003 01:50:48 +0530
Reply-To: <srinivask@future.futsoft.com>
From: "srinivask" <srinivask@future.futsoft.com>
To: <ssm-web-archive@ietf.org>
Subject: ietf.org mailing list memberships reminder
Date: Mon, 18 Aug 2003 20:03:34 +0530
Message-ID: <003c01c36595$b4c2bea0$7904060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit




***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************




From ssm-admin@ietf.org  Tue Aug 19 02:39:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29287
	for <ssm-archive@lists.ietf.org>; Tue, 19 Aug 2003 02:39:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p08z-0007re-LA; Tue, 19 Aug 2003 02:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p08G-0007qo-OY
	for ssm@optimus.ietf.org; Tue, 19 Aug 2003 02:38:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29225
	for <ssm@ietf.org>; Tue, 19 Aug 2003 02:38:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p08D-0005N2-00
	for ssm@ietf.org; Tue, 19 Aug 2003 02:38:13 -0400
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p08B-0005Mz-00
	for ssm@ietf.org; Tue, 19 Aug 2003 02:38:12 -0400
Received: from kailash1.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T642632ed20cbc58c235bc@fsnt.future.futsoft.com> for <ssm@ietf.org>; Tue, 
    19 Aug 2003 10:40:01 +0530
Received: from srinivask (srinivask.future.futsoft.com [10.6.4.121]) by 
    kailash1.future.futsoft.com (8.11.0/8.11.0) with SMTP id h7JAppi21533 for 
    <ssm@ietf.org>; Tue, 19 Aug 2003 16:21:51 +0530
Reply-To: <srinivask@future.futsoft.com>
From: "srinivask" <srinivask@future.futsoft.com>
To: <ssm@ietf.org>
Date: Tue, 19 Aug 2003 10:34:42 +0530
Message-ID: <004c01c3660f$6733daa0$7904060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Subject: [ssm] FW: IGMPV3 - Experiment-1
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



 -----Original Message-----
From: 	srinivask [mailto:srinivask@future.futsoft.com]
Sent:	Monday, 18 August 2003 8:14 PM
To:	'gantsich@cc.gatech.edu'
Subject:	IGMPV3 - Experiment-1

Hello Sir,

I would like to know why the following problem comens into picture, when i
follow the below spwcified steps.

- I have  built  a Igmpv3(Multicast protocol with ssm support) kernel in
Linux-7.1(red hat) , as per the Linux build proceedure, as per the URL-
      http://www.cc.gatech.edu/~gantsich/igmpv3.htm

-The kernel was tested for igmpv3 functionality, delta support is achieved
when test applications are run on the kernel.
- The above make sure the igmpv3 applied patch is successfull. THE patch
supports both delta/full state igmpv3 .
- when tested for full state/advanced igmpv3 mode support by kernel, The
test
application gives the following error.

     "Error in setting filter :"Package not installed".

- On debugginng the, application  it was found that ,on executing the
statement
----------  ioctl(sd, SIOCSIPMSFILTER, (char *)
fmode)------------->igmp_ioctl()--------->igmp_ioctl_set(struct sock *sk,
void * arg) ; the error had come.

- Other observation -

when i reboot/start the Igmpv3 kernel , there is one kernel log  message
saying ,    "ds: no socket drivers loaded",  on bootup.

- I want to know also whether this full state igmpv3  support is ethernet
card
vendor specific,means some vendor cards have this support and some may not.
like 3c59x driver may have and 8139too realtek driver .does not have.

could you please elaborate on this.
Basically i want to know how can i solve this problem.

Best regds,
srinivsk



***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From exim@www1.ietf.org  Tue Aug 19 02:39:37 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29320
	for <ssm-archive@odin.ietf.org>; Tue, 19 Aug 2003 02:39:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p099-0007uM-Eu
	for ssm-archive@odin.ietf.org; Tue, 19 Aug 2003 02:39:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7J6dBP5030393
	for ssm-archive@odin.ietf.org; Tue, 19 Aug 2003 02:39:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p099-0007u2-1J
	for ssm-web-archive@optimus.ietf.org; Tue, 19 Aug 2003 02:39:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29255
	for <ssm-web-archive@ietf.org>; Tue, 19 Aug 2003 02:39:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p095-0005Ni-00
	for ssm-web-archive@ietf.org; Tue, 19 Aug 2003 02:39:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p094-0005Nc-00
	for ssm-web-archive@ietf.org; Tue, 19 Aug 2003 02:39:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p08z-0007re-LA; Tue, 19 Aug 2003 02:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p08G-0007qo-OY
	for ssm@optimus.ietf.org; Tue, 19 Aug 2003 02:38:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29225
	for <ssm@ietf.org>; Tue, 19 Aug 2003 02:38:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p08D-0005N2-00
	for ssm@ietf.org; Tue, 19 Aug 2003 02:38:13 -0400
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p08B-0005Mz-00
	for ssm@ietf.org; Tue, 19 Aug 2003 02:38:12 -0400
Received: from kailash1.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T642632ed20cbc58c235bc@fsnt.future.futsoft.com> for <ssm@ietf.org>; Tue, 
    19 Aug 2003 10:40:01 +0530
Received: from srinivask (srinivask.future.futsoft.com [10.6.4.121]) by 
    kailash1.future.futsoft.com (8.11.0/8.11.0) with SMTP id h7JAppi21533 for 
    <ssm@ietf.org>; Tue, 19 Aug 2003 16:21:51 +0530
Reply-To: <srinivask@future.futsoft.com>
From: "srinivask" <srinivask@future.futsoft.com>
To: <ssm@ietf.org>
Date: Tue, 19 Aug 2003 10:34:42 +0530
Message-ID: <004c01c3660f$6733daa0$7904060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Subject: [ssm] FW: IGMPV3 - Experiment-1
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



 -----Original Message-----
From: 	srinivask [mailto:srinivask@future.futsoft.com]
Sent:	Monday, 18 August 2003 8:14 PM
To:	'gantsich@cc.gatech.edu'
Subject:	IGMPV3 - Experiment-1

Hello Sir,

I would like to know why the following problem comens into picture, when i
follow the below spwcified steps.

- I have  built  a Igmpv3(Multicast protocol with ssm support) kernel in
Linux-7.1(red hat) , as per the Linux build proceedure, as per the URL-
      http://www.cc.gatech.edu/~gantsich/igmpv3.htm

-The kernel was tested for igmpv3 functionality, delta support is achieved
when test applications are run on the kernel.
- The above make sure the igmpv3 applied patch is successfull. THE patch
supports both delta/full state igmpv3 .
- when tested for full state/advanced igmpv3 mode support by kernel, The
test
application gives the following error.

     "Error in setting filter :"Package not installed".

- On debugginng the, application  it was found that ,on executing the
statement
----------  ioctl(sd, SIOCSIPMSFILTER, (char *)
fmode)------------->igmp_ioctl()--------->igmp_ioctl_set(struct sock *sk,
void * arg) ; the error had come.

- Other observation -

when i reboot/start the Igmpv3 kernel , there is one kernel log  message
saying ,    "ds: no socket drivers loaded",  on bootup.

- I want to know also whether this full state igmpv3  support is ethernet
card
vendor specific,means some vendor cards have this support and some may not.
like 3c59x driver may have and 8139too realtek driver .does not have.

could you please elaborate on this.
Basically i want to know how can i solve this problem.

Best regds,
srinivsk



***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



From ssm-admin@ietf.org  Tue Aug 19 03:28:56 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29288
	for <ssm-archive@lists.ietf.org>; Tue, 19 Aug 2003 02:39:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p090-0007rm-4t; Tue, 19 Aug 2003 02:39:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p08J-0007qt-3C
	for ssm@optimus.ietf.org; Tue, 19 Aug 2003 02:38:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29229
	for <ssm@ietf.org>; Tue, 19 Aug 2003 02:38:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p08F-0005N7-00
	for ssm@ietf.org; Tue, 19 Aug 2003 02:38:15 -0400
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p08E-0005Mz-00
	for ssm@ietf.org; Tue, 19 Aug 2003 02:38:14 -0400
Received: from kailash1.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T64263421d7cbc58c235bc@fsnt.future.futsoft.com> for <ssm@ietf.org>; Tue, 
    19 Aug 2003 10:41:20 +0530
Received: from srinivask (srinivask.future.futsoft.com [10.6.4.121]) by 
    kailash1.future.futsoft.com (8.11.0/8.11.0) with SMTP id h7JArAi21574 for 
    <ssm@ietf.org>; Tue, 19 Aug 2003 16:23:10 +0530
Reply-To: <srinivask@future.futsoft.com>
From: "srinivask" <srinivask@future.futsoft.com>
To: <ssm@ietf.org>
Date: Tue, 19 Aug 2003 10:36:01 +0530
Message-ID: <004d01c3660f$965807c0$7904060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Subject: [ssm] Igmpv3 - Experiment-1
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello everybody,

I would like to know why the following problem comens into picture, when i
follow the below spwcified steps.

- I have  built  a Igmpv3(Multicast protocol with ssm support) kernel in
Linux-7.1(red hat) , as per the Linux build proceedure, as per the URL-
      http://www.cc.gatech.edu/~gantsich/igmpv3.htm

-The kernel was tested for igmpv3 functionality, delta support is achieved
when test applications are run on the kernel.
- The above make sure the igmpv3 applied patch is successfull. THE patch
supports both delta/full state igmpv3 .
- when tested for full state/advanced igmpv3 mode support by kernel, The
test
application gives the following error.

     "Error in setting filter :"Package not installed".

- On debugginng the, application  it was found that ,on executing the
statement
----------  ioctl(sd, SIOCSIPMSFILTER, (char *)
fmode)------------->igmp_ioctl()--------->igmp_ioctl_set(struct sock *sk,
void * arg) ; the error had come.

- Other observation -

when i reboot/start the Igmpv3 kernel , there is one kernel log  message
saying ,    "ds: no socket drivers loaded",  on bootup.

- I want to know also whether this full state igmpv3  support is ethernet
card
vendor specific,means some vendor cards have this support and some may not.
like 3c59x driver may have and 8139too realtek driver .does not have.

could you please elaborate on this.
Basically i want to know how can i solve this problem.

Best regds,
srinivsk



***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From exim@www1.ietf.org  Tue Aug 19 03:28:57 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29321
	for <ssm-archive@odin.ietf.org>; Tue, 19 Aug 2003 02:39:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p099-0007uN-Ey
	for ssm-archive@odin.ietf.org; Tue, 19 Aug 2003 02:39:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7J6dBD0030392
	for ssm-archive@odin.ietf.org; Tue, 19 Aug 2003 02:39:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p099-0007u3-2s
	for ssm-web-archive@optimus.ietf.org; Tue, 19 Aug 2003 02:39:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29257
	for <ssm-web-archive@ietf.org>; Tue, 19 Aug 2003 02:39:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p095-0005Nf-00
	for ssm-web-archive@ietf.org; Tue, 19 Aug 2003 02:39:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p094-0005Nb-00
	for ssm-web-archive@ietf.org; Tue, 19 Aug 2003 02:39:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p090-0007rm-4t; Tue, 19 Aug 2003 02:39:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p08J-0007qt-3C
	for ssm@optimus.ietf.org; Tue, 19 Aug 2003 02:38:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29229
	for <ssm@ietf.org>; Tue, 19 Aug 2003 02:38:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p08F-0005N7-00
	for ssm@ietf.org; Tue, 19 Aug 2003 02:38:15 -0400
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p08E-0005Mz-00
	for ssm@ietf.org; Tue, 19 Aug 2003 02:38:14 -0400
Received: from kailash1.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T64263421d7cbc58c235bc@fsnt.future.futsoft.com> for <ssm@ietf.org>; Tue, 
    19 Aug 2003 10:41:20 +0530
Received: from srinivask (srinivask.future.futsoft.com [10.6.4.121]) by 
    kailash1.future.futsoft.com (8.11.0/8.11.0) with SMTP id h7JArAi21574 for 
    <ssm@ietf.org>; Tue, 19 Aug 2003 16:23:10 +0530
Reply-To: <srinivask@future.futsoft.com>
From: "srinivask" <srinivask@future.futsoft.com>
To: <ssm@ietf.org>
Date: Tue, 19 Aug 2003 10:36:01 +0530
Message-ID: <004d01c3660f$965807c0$7904060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Subject: [ssm] Igmpv3 - Experiment-1
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello everybody,

I would like to know why the following problem comens into picture, when i
follow the below spwcified steps.

- I have  built  a Igmpv3(Multicast protocol with ssm support) kernel in
Linux-7.1(red hat) , as per the Linux build proceedure, as per the URL-
      http://www.cc.gatech.edu/~gantsich/igmpv3.htm

-The kernel was tested for igmpv3 functionality, delta support is achieved
when test applications are run on the kernel.
- The above make sure the igmpv3 applied patch is successfull. THE patch
supports both delta/full state igmpv3 .
- when tested for full state/advanced igmpv3 mode support by kernel, The
test
application gives the following error.

     "Error in setting filter :"Package not installed".

- On debugginng the, application  it was found that ,on executing the
statement
----------  ioctl(sd, SIOCSIPMSFILTER, (char *)
fmode)------------->igmp_ioctl()--------->igmp_ioctl_set(struct sock *sk,
void * arg) ; the error had come.

- Other observation -

when i reboot/start the Igmpv3 kernel , there is one kernel log  message
saying ,    "ds: no socket drivers loaded",  on bootup.

- I want to know also whether this full state igmpv3  support is ethernet
card
vendor specific,means some vendor cards have this support and some may not.
like 3c59x driver may have and 8139too realtek driver .does not have.

could you please elaborate on this.
Basically i want to know how can i solve this problem.

Best regds,
srinivsk



***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



From ssm-admin@ietf.org  Tue Aug 19 03:53:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00883
	for <ssm-archive@lists.ietf.org>; Tue, 19 Aug 2003 03:53:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p1Ic-00028N-5r; Tue, 19 Aug 2003 03:53:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p1IQ-00027x-C6
	for ssm@optimus.ietf.org; Tue, 19 Aug 2003 03:52:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00845
	for <ssm@ietf.org>; Tue, 19 Aug 2003 03:52:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p1IN-0005hn-00
	for ssm@ietf.org; Tue, 19 Aug 2003 03:52:47 -0400
Received: from oak.fernuni-hagen.de ([132.176.114.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p1IN-0005hX-00
	for ssm@ietf.org; Tue, 19 Aug 2003 03:52:47 -0400
Received: from amavis by oak.FernUni-Hagen.de with scanned-ok (Exim 4.04)
	id 19p1Ht-00025A-00; Tue, 19 Aug 2003 09:52:17 +0200
Received: from lgks2.fernuni-hagen.de ([132.176.12.66])
	by oak.FernUni-Hagen.de with esmtp (Exim 4.04)
	id 19p1Hl-00024a-00; Tue, 19 Aug 2003 09:52:09 +0200
Received: from LGKS2/SpoolDir by lgks2.fernuni-hagen.de (Mercury 1.48);
    19 Aug 03 09:52:10 +0200
Received: from SpoolDir by LGKS2 (Mercury 1.48); 19 Aug 03 09:52:01 +0200
Received: from notebookms (132.176.12.154) by lgks2.fernuni-hagen.de (Mercury 1.48);
    19 Aug 03 09:51:55 +0200
From: "Stepping, Michael" <michael.stepping@fernuni-hagen.de>
To: <srinivask@future.futsoft.com>, <ssm@ietf.org>
Subject: RE: [ssm] Igmpv3 - Experiment-1
Date: Tue, 19 Aug 2003 09:51:54 +0200
Message-ID: <NHBBIKJKCDACDGJNEKHPKEOPDKAA.michael.stepping@fernuni-hagen.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 5 (Lowest)
X-MSMail-Priority: Low
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Low
In-Reply-To: <004d01c3660f$965807c0$7904060a@future.futsoft.com>
X-Virus-Scanned: by AMaViS perl-11
Content-Transfer-Encoding: 7bit
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

> - I want to know also whether this full state igmpv3  support is ethernet
> card
> vendor specific,means some vendor cards have this support and
> some may not.
> like 3c59x driver may have and 8139too realtek driver .does not have.
>

In modern up-to-date Operating Systems usually the Ethernet-Frame
is built in Software, means by a loadable driver. Therefore (Ethernet)
Hardware provides only a MAC-Interface (Medium Access Control).

Example:
You want to transmit a frame, let us say an RTP/UDP/IP frame.
Usually you built an application where it is your task to build
an RTP frame including RTP header. Then you ask the socket
to establish an UDP (Datagram) Socket and put this self-built frame
to the socket (so far nothing new, I assume).
Then usually the TCP/IP Kernel Driver catches this frame and adds
in this case the UDP header. After that the IP header is built in front.
Now nearly all Operating Systems have built-in a tool with the meaning
"Protocol Manager".
This Protocol Manager manages now that your IP frame is
diverted to the correct netcard. The netcard provides access by the MAC
interface.
(In MS Windows OS this is a part of the NDIS (Network Describing
Interface Specification) interface, in Novell this interface is called ODI,
for Linux
I need a hint.)
Usually the netcard driver adds the protocol specific headers and the
netcard hardware adds the necessary checksums and introductions (PLLs...).

That was a long story. The result: In the last 15 years the netcards
provided more or less a raw access. It is easier to exchange a piece of
software
than exchanging a monolithic netcard.
So, IGMP is a topic of the IP stack and is not influenced by your netcard.
(Of course there could be bugs in the software that do not initialize the
netcard correct or set filters for the several frames wrong or ....)

If I am wrong, please correct me.

Michael


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From exim@www1.ietf.org  Tue Aug 19 03:53:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00931
	for <ssm-archive@odin.ietf.org>; Tue, 19 Aug 2003 03:53:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p1If-00029y-Sn
	for ssm-archive@odin.ietf.org; Tue, 19 Aug 2003 03:53:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7J7r5h8008301
	for ssm-archive@odin.ietf.org; Tue, 19 Aug 2003 03:53:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p1If-00029o-Nm
	for ssm-web-archive@optimus.ietf.org; Tue, 19 Aug 2003 03:53:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00864
	for <ssm-web-archive@ietf.org>; Tue, 19 Aug 2003 03:53:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p1Id-0005hy-00
	for ssm-web-archive@ietf.org; Tue, 19 Aug 2003 03:53:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p1Ic-0005hv-00
	for ssm-web-archive@ietf.org; Tue, 19 Aug 2003 03:53:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p1Ic-00028N-5r; Tue, 19 Aug 2003 03:53:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p1IQ-00027x-C6
	for ssm@optimus.ietf.org; Tue, 19 Aug 2003 03:52:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00845
	for <ssm@ietf.org>; Tue, 19 Aug 2003 03:52:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p1IN-0005hn-00
	for ssm@ietf.org; Tue, 19 Aug 2003 03:52:47 -0400
Received: from oak.fernuni-hagen.de ([132.176.114.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p1IN-0005hX-00
	for ssm@ietf.org; Tue, 19 Aug 2003 03:52:47 -0400
Received: from amavis by oak.FernUni-Hagen.de with scanned-ok (Exim 4.04)
	id 19p1Ht-00025A-00; Tue, 19 Aug 2003 09:52:17 +0200
Received: from lgks2.fernuni-hagen.de ([132.176.12.66])
	by oak.FernUni-Hagen.de with esmtp (Exim 4.04)
	id 19p1Hl-00024a-00; Tue, 19 Aug 2003 09:52:09 +0200
Received: from LGKS2/SpoolDir by lgks2.fernuni-hagen.de (Mercury 1.48);
    19 Aug 03 09:52:10 +0200
Received: from SpoolDir by LGKS2 (Mercury 1.48); 19 Aug 03 09:52:01 +0200
Received: from notebookms (132.176.12.154) by lgks2.fernuni-hagen.de (Mercury 1.48);
    19 Aug 03 09:51:55 +0200
From: "Stepping, Michael" <michael.stepping@fernuni-hagen.de>
To: <srinivask@future.futsoft.com>, <ssm@ietf.org>
Subject: RE: [ssm] Igmpv3 - Experiment-1
Date: Tue, 19 Aug 2003 09:51:54 +0200
Message-ID: <NHBBIKJKCDACDGJNEKHPKEOPDKAA.michael.stepping@fernuni-hagen.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 5 (Lowest)
X-MSMail-Priority: Low
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Low
In-Reply-To: <004d01c3660f$965807c0$7904060a@future.futsoft.com>
X-Virus-Scanned: by AMaViS perl-11
Content-Transfer-Encoding: 7bit
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

> - I want to know also whether this full state igmpv3  support is ethernet
> card
> vendor specific,means some vendor cards have this support and
> some may not.
> like 3c59x driver may have and 8139too realtek driver .does not have.
>

In modern up-to-date Operating Systems usually the Ethernet-Frame
is built in Software, means by a loadable driver. Therefore (Ethernet)
Hardware provides only a MAC-Interface (Medium Access Control).

Example:
You want to transmit a frame, let us say an RTP/UDP/IP frame.
Usually you built an application where it is your task to build
an RTP frame including RTP header. Then you ask the socket
to establish an UDP (Datagram) Socket and put this self-built frame
to the socket (so far nothing new, I assume).
Then usually the TCP/IP Kernel Driver catches this frame and adds
in this case the UDP header. After that the IP header is built in front.
Now nearly all Operating Systems have built-in a tool with the meaning
"Protocol Manager".
This Protocol Manager manages now that your IP frame is
diverted to the correct netcard. The netcard provides access by the MAC
interface.
(In MS Windows OS this is a part of the NDIS (Network Describing
Interface Specification) interface, in Novell this interface is called ODI,
for Linux
I need a hint.)
Usually the netcard driver adds the protocol specific headers and the
netcard hardware adds the necessary checksums and introductions (PLLs...).

That was a long story. The result: In the last 15 years the netcards
provided more or less a raw access. It is easier to exchange a piece of
software
than exchanging a monolithic netcard.
So, IGMP is a topic of the IP stack and is not influenced by your netcard.
(Of course there could be bugs in the software that do not initialize the
netcard correct or set filters for the several frames wrong or ....)

If I am wrong, please correct me.

Michael


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



From ssm-admin@ietf.org  Tue Aug 19 08:10:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06459
	for <ssm-archive@lists.ietf.org>; Tue, 19 Aug 2003 08:10:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p5JJ-00027A-DO; Tue, 19 Aug 2003 08:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p5Io-00026j-Ub
	for ssm@optimus.ietf.org; Tue, 19 Aug 2003 08:09:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06397
	for <ssm@ietf.org>; Tue, 19 Aug 2003 08:09:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p5In-00071q-00
	for ssm@ietf.org; Tue, 19 Aug 2003 08:09:29 -0400
Received: from lennon.multicasttech.com
	([63.105.122.7] helo=multicasttech.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p5In-00071k-00
	for ssm@ietf.org; Tue, 19 Aug 2003 08:09:29 -0400
Received: from [68.100.43.31] (account <marshall_eubanks@multicasttech.com>)
  by multicasttech.com (CommuniGate Pro WebUser 3.4.8)
  with HTTP id 1727861; Tue, 19 Aug 2003 08:09:19 -0400
From: "Marshall Eubanks" <tme@multicasttech.com>
Subject: Re: [ssm] FW: IGMPV3 - Experiment-1
To: <srinivask@future.futsoft.com>, <ssm@ietf.org>
X-Mailer: CommuniGate Pro Web Mailer v.3.4.8
Date: Tue, 19 Aug 2003 08:09:19 -0400
Message-ID: <web-1727861@multicasttech.com>
In-Reply-To: <004c01c3660f$6733daa0$7904060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

On Tue, 19 Aug 2003 10:34:42 +0530
 "srinivask" <srinivask@future.futsoft.com> wrote:
> 
> 

Did you look at the redhat 7.3 rpm's for IGMPv3 that we put up last year ?

http://www.multicasttech.com/igmpv3/

I know that there were some missing routines that had to be included
to make the rpm work; you might look at the included packages.

Regards
Marshall Eubanks


>  -----Original Message-----
> From: 	srinivask [mailto:srinivask@future.futsoft.com]
> Sent:	Monday, 18 August 2003 8:14 PM
> To:	'gantsich@cc.gatech.edu'
> Subject:	IGMPV3 - Experiment-1
> 
> Hello Sir,
> 
> I would like to know why the following problem comens into picture, when i
> follow the below spwcified steps.
> 
> - I have  built  a Igmpv3(Multicast protocol with ssm support) kernel in
> Linux-7.1(red hat) , as per the Linux build proceedure, as per the URL-
>       http://www.cc.gatech.edu/~gantsich/igmpv3.htm
> 
> -The kernel was tested for igmpv3 functionality, delta support is achieved
> when test applications are run on the kernel.
> - The above make sure the igmpv3 applied patch is successfull. THE patch
> supports both delta/full state igmpv3 .
> - when tested for full state/advanced igmpv3 mode support by kernel, The
> test
> application gives the following error.
> 
>      "Error in setting filter :"Package not installed".
> 
> - On debugginng the, application  it was found that ,on executing the
> statement
> ----------  ioctl(sd, SIOCSIPMSFILTER, (char *)
> fmode)------------->igmp_ioctl()--------->igmp_ioctl_set(struct sock *sk,
> void * arg) ; the error had come.
> 
> - Other observation -
> 
> when i reboot/start the Igmpv3 kernel , there is one kernel log  message
> saying ,    "ds: no socket drivers loaded",  on bootup.
> 
> - I want to know also whether this full state igmpv3  support is ethernet
> card
> vendor specific,means some vendor cards have this support and some may not.
> like 3c59x driver may have and 8139too realtek driver .does not have.
> 
> could you please elaborate on this.
> Basically i want to know how can i solve this problem.
> 
> Best regds,
> srinivsk
> 
> 
> 
> ***************************************************************************
> This message is proprietary to Future Software Limited (FSL)
> and is intended solely for the use of the individual to whom it
> is addressed. It may contain  privileged or confidential information
> and should not be circulated or used for any purpose other than for
> what it is intended.
> 
> If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient,
> you are notified that you are strictly prohibited from using,
> copying, altering, or disclosing the contents of this message.
> FSL accepts no responsibility for loss or damage arising from
> the use of the information transmitted by this email including
> damage from virus.
> ***************************************************************************
> 
> 
> _______________________________________________
> ssm mailing list
> ssm@ietf.org
> https://www1.ietf.org/mailman/listinfo/ssm


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From exim@www1.ietf.org  Tue Aug 19 08:10:37 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06488
	for <ssm-archive@odin.ietf.org>; Tue, 19 Aug 2003 08:10:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p5JR-00028q-7Q
	for ssm-archive@odin.ietf.org; Tue, 19 Aug 2003 08:10:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7JCA9ke008228
	for ssm-archive@odin.ietf.org; Tue, 19 Aug 2003 08:10:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p5JQ-00028d-OX
	for ssm-web-archive@optimus.ietf.org; Tue, 19 Aug 2003 08:10:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06426
	for <ssm-web-archive@ietf.org>; Tue, 19 Aug 2003 08:10:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p5JP-00072J-00
	for ssm-web-archive@ietf.org; Tue, 19 Aug 2003 08:10:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p5JO-00072G-00
	for ssm-web-archive@ietf.org; Tue, 19 Aug 2003 08:10:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p5JJ-00027A-DO; Tue, 19 Aug 2003 08:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19p5Io-00026j-Ub
	for ssm@optimus.ietf.org; Tue, 19 Aug 2003 08:09:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06397
	for <ssm@ietf.org>; Tue, 19 Aug 2003 08:09:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p5In-00071q-00
	for ssm@ietf.org; Tue, 19 Aug 2003 08:09:29 -0400
Received: from lennon.multicasttech.com
	([63.105.122.7] helo=multicasttech.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p5In-00071k-00
	for ssm@ietf.org; Tue, 19 Aug 2003 08:09:29 -0400
Received: from [68.100.43.31] (account <marshall_eubanks@multicasttech.com>)
  by multicasttech.com (CommuniGate Pro WebUser 3.4.8)
  with HTTP id 1727861; Tue, 19 Aug 2003 08:09:19 -0400
From: "Marshall Eubanks" <tme@multicasttech.com>
Subject: Re: [ssm] FW: IGMPV3 - Experiment-1
To: <srinivask@future.futsoft.com>, <ssm@ietf.org>
X-Mailer: CommuniGate Pro Web Mailer v.3.4.8
Date: Tue, 19 Aug 2003 08:09:19 -0400
Message-ID: <web-1727861@multicasttech.com>
In-Reply-To: <004c01c3660f$6733daa0$7904060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

On Tue, 19 Aug 2003 10:34:42 +0530
 "srinivask" <srinivask@future.futsoft.com> wrote:
> 
> 

Did you look at the redhat 7.3 rpm's for IGMPv3 that we put up last year ?

http://www.multicasttech.com/igmpv3/

I know that there were some missing routines that had to be included
to make the rpm work; you might look at the included packages.

Regards
Marshall Eubanks


>  -----Original Message-----
> From: 	srinivask [mailto:srinivask@future.futsoft.com]
> Sent:	Monday, 18 August 2003 8:14 PM
> To:	'gantsich@cc.gatech.edu'
> Subject:	IGMPV3 - Experiment-1
> 
> Hello Sir,
> 
> I would like to know why the following problem comens into picture, when i
> follow the below spwcified steps.
> 
> - I have  built  a Igmpv3(Multicast protocol with ssm support) kernel in
> Linux-7.1(red hat) , as per the Linux build proceedure, as per the URL-
>       http://www.cc.gatech.edu/~gantsich/igmpv3.htm
> 
> -The kernel was tested for igmpv3 functionality, delta support is achieved
> when test applications are run on the kernel.
> - The above make sure the igmpv3 applied patch is successfull. THE patch
> supports both delta/full state igmpv3 .
> - when tested for full state/advanced igmpv3 mode support by kernel, The
> test
> application gives the following error.
> 
>      "Error in setting filter :"Package not installed".
> 
> - On debugginng the, application  it was found that ,on executing the
> statement
> ----------  ioctl(sd, SIOCSIPMSFILTER, (char *)
> fmode)------------->igmp_ioctl()--------->igmp_ioctl_set(struct sock *sk,
> void * arg) ; the error had come.
> 
> - Other observation -
> 
> when i reboot/start the Igmpv3 kernel , there is one kernel log  message
> saying ,    "ds: no socket drivers loaded",  on bootup.
> 
> - I want to know also whether this full state igmpv3  support is ethernet
> card
> vendor specific,means some vendor cards have this support and some may not.
> like 3c59x driver may have and 8139too realtek driver .does not have.
> 
> could you please elaborate on this.
> Basically i want to know how can i solve this problem.
> 
> Best regds,
> srinivsk
> 
> 
> 
> ***************************************************************************
> This message is proprietary to Future Software Limited (FSL)
> and is intended solely for the use of the individual to whom it
> is addressed. It may contain  privileged or confidential information
> and should not be circulated or used for any purpose other than for
> what it is intended.
> 
> If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient,
> you are notified that you are strictly prohibited from using,
> copying, altering, or disclosing the contents of this message.
> FSL accepts no responsibility for loss or damage arising from
> the use of the information transmitted by this email including
> damage from virus.
> ***************************************************************************
> 
> 
> _______________________________________________
> ssm mailing list
> ssm@ietf.org
> https://www1.ietf.org/mailman/listinfo/ssm


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



