From owner-freebsd-net@FreeBSD.ORG Wed Dec 15 00:13:25 2010 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 27E2E106564A for ; Wed, 15 Dec 2010 00:13:25 +0000 (UTC) (envelope-from sergv326@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id DB1288FC08 for ; Wed, 15 Dec 2010 00:13:24 +0000 (UTC) Received: by iwn39 with SMTP id 39so1393021iwn.13 for ; Tue, 14 Dec 2010 16:13:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=H7peCWAACLzNl6bJ2a4jcrTV4imNm82FG+bH6gq9T/0=; b=drFmfKPzkZcWFA4AwGStzumd+CQF+YpiW2X6/Xdb22uvhVrl1NXSUVemUaP7Mcjpap ChPJgULoKTHr4A+5yYGAMtP+THCe9+c+Gz03rH9qhXolra6cUjmkacf1BH/dM/ZkBhio w8mAw4XEqetawKidTE6A9arhSSfwf3LxPmEv4= 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=wRlAfggtcwbN2yIlZA2+Oc8RJnX/iphlYyfcOwgDCU6ZucwRULAp5T5i3FbORFyH5p 8eWR9k5N4i3DkSXWVunvLpEs4MkgSriMVv7KRfOO1EbBZSIwMnH7K7s8WJfqFLnVuG/T oIF/AY3hz7ff4ki6d/dhgWCXb2Lgg7nFQLx2Q= MIME-Version: 1.0 Received: by 10.42.174.138 with SMTP id v10mr5119802icz.91.1292370178185; Tue, 14 Dec 2010 15:42:58 -0800 (PST) Received: by 10.42.3.11 with HTTP; Tue, 14 Dec 2010 15:42:58 -0800 (PST) In-Reply-To: <3e2b8dd90912090037v6c8e13e1v869471d4e03ecfd5@mail.gmail.com> 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> <3e2b8dd90912080247s247bd878ud9fe4b234ff83f84@mail.gmail.com> <3e2b8dd90912090037v6c8e13e1v869471d4e03ecfd5@mail.gmail.com> Date: Wed, 15 Dec 2010 02:42:58 +0300 Message-ID: From: serg vasilyev To: Andriy Syrovenko Content-Type: text/plain; charset=ISO-8859-1 Cc: flo@smeets.im, freebsd-net@freebsd.org, Bruce Simpson 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: Wed, 15 Dec 2010 00:13:25 -0000 2009/12/9, Andriy Syrovenko : > Hi, > > Well, turning off the transmit checksum offloading on the upstream > interface solves the problem with IP checksums of IGMP report and > leave messages always being 0. So after issuing the > > ifconfig re1 -txcsum > > command, the proxy successfully subscribes to receiving multicast > streams, and I can see multicast UDP traffic coming in on the upstream > interface. However there is another serious problem. Shortly alfter my > router starts forwarding multicast traffic kernel crashes. The crash > may happen either immediately when I press the play button in my IPTV > player, or just after several channel switches. You can find crash > reports in the attached files. They are almost identical, differing > only in whether the pf module is loaded. > > > The interesting part of the story is if I block incoming UDP multicast > traffic using something like > > block in quick inet proto udp from any to 224.0.0.0/4 > > in my pf.conf, system remains stable. But as soon as I comment the > rule and reload pf, kernel crashes. I suspect the problem is not > strictly related to the igmp processing, but to the multicast routing > in general. Probably something wrong with thread synchronization. My > system is a dual-core Intel Atom. > > Another interesting observation is when my BSD box is disconnected > from the upstream router, I can see only IGMPv3 messages going out the > upstream interface, even despite the fact that igmpproxy supports > IGMPv2 only. > > br, > Andrey > Does your system do any nat processing ?