[SAM] detect the presence of an IGMPv3 querier

Sebastian Wölke <Sebastian.Woelke@haw-hamburg.de> Fri, 20 May 2011 11:36 UTC

Return-Path: <prvs=1148fbf0b=Sebastian.Woelke@haw-hamburg.de>
X-Original-To: sam@ietfa.amsl.com
Delivered-To: sam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DA63E072F for <sam@ietfa.amsl.com>; Fri, 20 May 2011 04:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.327
X-Spam-Level:
X-Spam-Status: No, score=-1.327 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6EwQ3ny1yPQ for <sam@ietfa.amsl.com>; Fri, 20 May 2011 04:36:21 -0700 (PDT)
Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) by ietfa.amsl.com (Postfix) with ESMTP id 771F6E06BF for <sam@irtf.org>; Fri, 20 May 2011 04:36:20 -0700 (PDT)
Received: from dehawshub02.mailcluster.haw-hamburg.de ([141.22.200.52]) by mail6.is.haw-hamburg.de with ESMTP/TLS/RC4-MD5; 20 May 2011 13:36:19 +0200
Received: from dehawscas03.mailcluster.haw-hamburg.de (141.22.200.53) by DEHAWSHUB02.mailcluster.haw-hamburg.de (141.22.200.52) with Microsoft SMTP Server (TLS) id 8.1.358.0; Fri, 20 May 2011 13:36:19 +0200
Received: from mail-px0-f176.google.com (141.22.200.35) by haw-mailer.haw-hamburg.de (141.22.200.80) with Microsoft SMTP Server (TLS) id 8.1.358.0; Fri, 20 May 2011 13:36:18 +0200
Received: by pxi11 with SMTP id 11so2953535pxi.7 for <sam@irtf.org>; Fri, 20 May 2011 04:36:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.126.18 with SMTP id y18mr2542082wfc.361.1305891376170; Fri, 20 May 2011 04:36:16 -0700 (PDT)
Received: by 10.142.89.15 with HTTP; Fri, 20 May 2011 04:36:16 -0700 (PDT)
Date: Fri, 20 May 2011 13:36:16 +0200
Message-ID: <BANLkTiktFHMCiPVzApKWuXCG9o_4Z0y0_w@mail.gmail.com>
From: Sebastian Wölke <Sebastian.Woelke@haw-hamburg.de>
To: sam@irtf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [SAM] detect the presence of an IGMPv3 querier
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sebastian.Woelke@haw-hamburg.de
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG" <sam.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/sam>, <mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/sam>, <mailto:sam-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2011 12:13:34 -0000

Hi all,

I'm working on a system software that automatically detects the presence
of a multicast querier in the current subnet based on passively
monitoring Linux kernel states.

This works fine for IPv6/MLD by looking into the /proc/net/SNMP6 table.
For IPv4/IGMP, the SNMP approach does not work. I can detect an IGMPv2
querier by monitoring 'Timer' in the /proc/net/igmp table: this counts
down the [Unsolicited Report Interval]. However, this does not exist for
IGMPv3, as reports are not suppressed.

My question is about IGMPv3. Does anybody know how to detect the
presence of an IGMPv3 querier based on the kernel states of a multicast
client?

Thanks for your support,

Sebastian