From owner-freebsd-stable@FreeBSD.ORG Fri Oct 9 07:21:38 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C0B81065696 for ; Fri, 9 Oct 2009 07:21:38 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id 189E38FC1F for ; Fri, 9 Oct 2009 07:21:37 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1Mw9Xi-000DIR-NS for freebsd-stable@freebsd.org; Fri, 09 Oct 2009 11:05:34 +0400 From: "Alexander Zagrebin" To: Date: Fri, 9 Oct 2009 11:05:34 +0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 Thread-Index: AcpIruUPGr1FtcZFRc2372cG6BGUYw== Subject: igmp problems on 8.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Oct 2009 07:21:38 -0000 After upgrading from 7.2-RELEASE to 8.0-RC1 i have noticed problems with igmp. xorp sees IGMP_V2_LEAVE_GROUP, but not IGMP_V2_MEMBERSHIP_REPORT. igmpproxy has the same behavior. xorp_rtrmgr.log contains only: [ TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 192.168.0.10 to 224.0.0.2 on vif rl0 [ TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 192.168.0.10 to 224.0.0.2 on vif rl0 [ TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 192.168.0.10 to 224.0.0.2 on vif rl0 [ TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 192.168.0.10 to 224.0.0.2 on vif rl0 but /var/log/messages (KTR and KTR_VERBOSE enabled): kernel: cpu1 ip_mforward: delete mfc orig 192.168.0.10 group e0000002 ifp 0xc3e99400 kernel: cpu1 igmp_input: called w/mbuf (0xc494f900,24) kernel: cpu1 ip_mforward: delete mfc orig 192.168.0.10 group ef20013a ifp 0xc3e99400 kernel: cpu1 igmp_input: called w/mbuf (0xc4072300,24) kernel: cpu1 process v2 report 239.32.1.58 on ifp 0xc3e99400(rl0) kernel: cpu1 ip_mforward: delete mfc orig 192.168.0.10 group ef20013a ifp 0xc3e99400 kernel: cpu1 igmp_input: called w/mbuf (0xc4073500,24) kernel: cpu1 process v2 report 239.32.1.58 on ifp 0xc3e99400(rl0) kernel: cpu1 ip_mforward: delete mfc orig 192.168.0.10 group ef20013a ifp 0xc3e99400 kernel: cpu1 igmp_input: called w/mbuf (0xc429cc00,24) kernel: cpu1 process v2 report 239.32.1.58 on ifp 0xc3e99400(rl0) kernel: cpu1 ip_mforward: delete mfc orig 192.168.0.10 group e0000002 ifp 0xc3e99400 kernel: cpu1 igmp_input: called w/mbuf (0xc4926500,24) kernel: cpu1 ip_mforward: delete mfc orig 192.168.0.10 group ef200139 ifp 0xc3e99400 kernel: cpu1 igmp_input: called w/mbuf (0xc429fe00,24) kernel: cpu1 process v2 report 239.32.1.57 on ifp 0xc3e99400(rl0) kernel: cpu1 ip_mforward: delete mfc orig 192.168.0.10 group ef200139 ifp 0xc3e99400 kernel: cpu1 igmp_input: called w/mbuf (0xc4242a00,24) kernel: cpu1 process v2 report 239.32.1.57 on ifp 0xc3e99400(rl0) kernel: cpu1 ip_mforward: delete mfc orig 192.168.0.10 group e0000002 ifp 0xc3e99400 kernel: cpu1 igmp_input: called w/mbuf (0xc491f700,24) kernel: cpu1 ip_mforward: delete mfc orig 192.168.0.10 group ef200108 ifp 0xc3e99400 ... So the kernel processes igmp v2 reports, but user space daemons doesn't recieve it. Any suggestions? PS: It is not ipfw issue (when testing, the first ipfw rule is "allow ip from any to any") -- Alexander Zagrebin