From owner-freebsd-net@FreeBSD.ORG Wed Dec 15 10:44:47 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 D69A8106566B for ; Wed, 15 Dec 2010 10:44:47 +0000 (UTC) (envelope-from andriys@gmail.com) Received: from mail-bw0-f49.google.com (mail-bw0-f49.google.com [209.85.214.49]) by mx1.freebsd.org (Postfix) with ESMTP id DC3FC8FC14 for ; Wed, 15 Dec 2010 10:44:46 +0000 (UTC) Received: by bwz5 with SMTP id 5so2085413bwz.8 for ; Wed, 15 Dec 2010 02:44:45 -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=Mx3/W5DXhL2MD4O5S6+JlWQAnZsv9XF/DgHFgMyn3TU=; b=KSuR7JNddD2NMe7pjSUfMVg4wNaif0X+z5LXyOwomEemZjbCpxV8u0E3y57d6tOvvZ n6YTBfru3nKHiemAYr8RQIqtk8TLoFwKo1c3yG+hNPj+mp9JzZt2B9KIeNnx/Oy+Y+I4 6hyfpR6fUUuyVH64V1xBEOD0pGM5DdUYhzxHM= 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=GGZM0wzxl5o7YCwuejFuPPOXIH2HwlyBVg+GaSP9x0t3eL7VMzXWmvT8JZ5yIDaRJa W1njJXC4iGlCt7U/ZXYTvIikv+jor2kJoHKcdX9kWtuUHvwQx+6sgBGVD39RpxlGJivr NyWtw7VhdZX1ySAXsRJrMFvG8zbL+vlxc5enM= MIME-Version: 1.0 Received: by 10.204.122.67 with SMTP id k3mr4131162bkr.65.1292408225954; Wed, 15 Dec 2010 02:17:05 -0800 (PST) Received: by 10.204.144.194 with HTTP; Wed, 15 Dec 2010 02:17:05 -0800 (PST) In-Reply-To: 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 12:17:05 +0200 Message-ID: From: Andriy Syrovenko To: serg vasilyev Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 10:44:47 -0000 Hi! Yes, I have PF enabled with some NAT rules present in the rule set. However disabling PF (even by commenting out 'pf_enable' in the /etc/rc.conf and rebooting the machine) does not make any difference. The problem persist regardless of whether NAT is enabled or not (or even whether pf.ko is loaded or not). Best regards, Andriy. 2010/12/15 serg vasilyev > 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 ? >