From owner-freebsd-net@FreeBSD.ORG Fri Dec 31 15:58:26 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 DE4CD1065672 for ; Fri, 31 Dec 2010 15:58:25 +0000 (UTC) (envelope-from kevlo@kevlo.org) Received: from ns.kevlo.org (kevlo.org [220.128.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id DEE5E8FC0A for ; Fri, 31 Dec 2010 15:58:19 +0000 (UTC) Received: from [127.0.0.1] (kevlo@kevlo.org [220.128.136.52]) by ns.kevlo.org (8.14.3/8.14.3) with ESMTP id oBVFd7Rr011312; Fri, 31 Dec 2010 23:39:21 +0800 (CST) From: Kevin Lo To: Andriy Syrovenko 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> Content-Type: text/plain; charset="UTF-8" Date: Fri, 31 Dec 2010 23:38:58 +0800 Message-ID: <1293809938.2126.12.camel@nsl> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, flo@smeets.im, serg vasilyev , 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: Fri, 31 Dec 2010 15:58:26 -0000 This issue is easily reproduced on 9.0 -CURRENT as well. I got kernel panic after running mrouted, igmpproxy, or xorp. Kevin Andriy Syrovenko wrote: > 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 ? > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"