From owner-freebsd-net@FreeBSD.ORG Tue Dec 8 10:47:42 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1CA1106568F for ; Tue, 8 Dec 2009 10:47:42 +0000 (UTC) (envelope-from andriys@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 311FC8FC0C for ; Tue, 8 Dec 2009 10:47:41 +0000 (UTC) Received: by bwz5 with SMTP id 5so4275055bwz.3 for ; Tue, 08 Dec 2009 02:47:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=gv2aBJqrHq309VzH6NhfM1HcCy7OAGuWss/8k1BINXg=; b=PxhjMjkBzlBBj7yy6YQ9+wcmvwFmO266rGufwxKlN/1iLXLenMbV6JwziLcLZTA804 fJxPwNywOgkcacwyMul5mttYA0yh/YBGrmdVkkFupeFvMbJcDKVWTHZ3/9szc6xD3N9S VxacEcNfn1p1jmPp4Ry5obSXPwK5Ko4wlHEMM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=e+ieV29TjSKTVHPzqlzlRl/xAxTddAGBTtU6YIMev2CmSpst6kW92pD68Ru7rHJ+tq 4rXkzog2lbaS3yoCZgTy9Hc0FO6TjKE9xu2Nehu8V0OF1N4UUJj4FQzZuJdIk+SlrPQj UjuLKdOBE6tERqCwQQUyL59SUhccdXpJFIdMA= MIME-Version: 1.0 Received: by 10.204.34.75 with SMTP id k11mr926528bkd.105.1260269260900; Tue, 08 Dec 2009 02:47:40 -0800 (PST) In-Reply-To: <4B1E2574.8010704@incunabulum.net> References: <200912071020.nB7AK77I023054@freefall.freebsd.org> <4B1CDEE5.6080507@incunabulum.net> <3e2b8dd90912070305t6ffc08a6gf7acd8890d028854@mail.gmail.com> <4B1D07C3.6090005@incunabulum.net> <3e2b8dd90912080114x31d962acqf2c8a360e7b5a83d@mail.gmail.com> <4B1E1EF0.8040503@incunabulum.net> <3e2b8dd90912080155s544a7a50j17882b35f1343750@mail.gmail.com> <4B1E2574.8010704@incunabulum.net> Date: Tue, 8 Dec 2009 12:47:40 +0200 Message-ID: <3e2b8dd90912080247s247bd878ud9fe4b234ff83f84@mail.gmail.com> From: Andriy Syrovenko To: Bruce Simpson Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, flo@smeets.im Subject: Re: kern/138666: [multicast] [panic] not working multicast through igmpproxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Dec 2009 10:47:42 -0000 2009/12/8 Bruce Simpson : > The only other thing I can think of is: is this an igmpproxy issue, ie. is > the IGMP traffic which is causing problems, coming from igmpproxy itself? That's possible. > The kernel never generates IGMP control traffic related to routing. Any IGMP > traffic generated by userland, generally uses the raw socket interface. I don't yet understand all the mechanics behind the multicast routing. And igmpproxy does seem to use raw sockets to send igmp packets. However when I tried to do some investigations yesterday evening, I added a couple of printf()s to igmp_v1v2_queue_report() in sys/netinet/igmp.c, and I saw their output in dmesg while switching multicast groups. > Userland could potentially also use pcap to inject directly to the link > layer, and indeed, that might be a more desirable situation where the daemon > is intended to run on interfaces w/o an IPv4 address. Of course, this > entirely bypasses the host IP stack. This does not seem to be the case with the igmpproxy.