Re: [SAM] detect the presence of an IGMPv3 querier
Sebastian Wölke <Sebastian.Woelke@haw-hamburg.de> Mon, 23 May 2011 07:51 UTC
Return-Path: <prvs=1176289b4=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 4BE56E0726 for <sam@ietfa.amsl.com>; Mon, 23 May 2011 00:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.88
X-Spam-Level:
X-Spam-Status: No, score=-0.88 tagged_above=-999 required=5 tests=[AWL=0.447, 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 L9PpcCM3UJYw for <sam@ietfa.amsl.com>; Mon, 23 May 2011 00:51:24 -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 89220E075F for <sam@irtf.org>; Mon, 23 May 2011 00:51:23 -0700 (PDT)
Received: from dehawshub01.mailcluster.haw-hamburg.de ([141.22.200.36]) by mail6.is.haw-hamburg.de with ESMTP/TLS/RC4-MD5; 23 May 2011 09:48:03 +0200
Received: from dehawscas03.mailcluster.haw-hamburg.de (141.22.200.53) by DEHAWSHUB01.mailcluster.haw-hamburg.de (141.22.200.36) with Microsoft SMTP Server (TLS) id 8.1.358.0; Mon, 23 May 2011 09:48:02 +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; Mon, 23 May 2011 09:48:02 +0200
Received: by pxi11 with SMTP id 11so4448933pxi.7 for <sam@irtf.org>; Mon, 23 May 2011 00:48:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.126.18 with SMTP id y18mr777896wfc.361.1306136880000; Mon, 23 May 2011 00:48:00 -0700 (PDT)
Received: by 10.142.89.15 with HTTP; Mon, 23 May 2011 00:47:59 -0700 (PDT)
In-Reply-To: <4DD6A8C0.1000501@venaas.com>
References: <BANLkTiktFHMCiPVzApKWuXCG9o_4Z0y0_w@mail.gmail.com> <4DD6A8C0.1000501@venaas.com>
Date: Mon, 23 May 2011 09:47:59 +0200
Message-ID: <BANLkTikARxgDQfcbbCtsNpnBU2eeNX9oWQ@mail.gmail.com>
From: Sebastian Wölke <Sebastian.Woelke@haw-hamburg.de>
To: Stig Venaas <stig@venaas.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: sam@irtf.org
Subject: Re: [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: Mon, 23 May 2011 07:51:27 -0000
This dosen't work. The default Querier version is V3. If no Querier present the version is set to V3. Sebastian 2011/5/20 Stig Venaas <stig@venaas.com>: > On 5/20/2011 4:36 AM, Sebastian Wölke wrote: >> 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? > > If you look at "/proc/net/igmp" it should give you the querier version. > I see e.g.: > > Idx Device : Count Querier Group Users Timer Reporter > 1 lo : 0 V3 > 010000E0 1 0:00000000 0 > 2 eth0 : 3 V3 > 010000E0 1 0:00000000 0 > > Doesn't this work? > > Stig > >> >> Thanks for your support, >> >> Sebastian >> _______________________________________________ >> SAM mailing list >> SAM@irtf.org >> http://www.irtf.org/mailman/listinfo/sam > >
- [SAM] detect the presence of an IGMPv3 querier Sebastian Wölke
- Re: [SAM] detect the presence of an IGMPv3 querier Stig Venaas
- Re: [SAM] detect the presence of an IGMPv3 querier Sebastian Wölke
- Re: [SAM] detect the presence of an IGMPv3 querier Thomas C. Schmidt