From owner-freebsd-net@FreeBSD.ORG Thu Mar 19 16:13:38 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 78B601065A58 for ; Thu, 19 Mar 2009 16:13:38 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 49FFC8FC1E for ; Thu, 19 Mar 2009 16:13:38 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id E8CD12F742A; Thu, 19 Mar 2009 12:13:37 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 19 Mar 2009 12:13:37 -0400 X-Sasl-enc: 1jrFoWS2kO7uINQFuOcShzhz5LThO/CCwq+7lo17i8RZ 1237479217 Received: from anglepoise.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id ED2823BA1C; Thu, 19 Mar 2009 12:13:36 -0400 (EDT) Message-ID: <49C26F2F.9080401@incunabulum.net> Date: Thu, 19 Mar 2009 16:13:35 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.19 (X11/20090125) MIME-Version: 1.0 To: Vany Serezhkin References: <49C2504F.2030003@serezhkin.com> In-Reply-To: <49C2504F.2030003@serezhkin.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: 802.1x broken after SVN rev 189592 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: Thu, 19 Mar 2009 16:13:48 -0000 Hi, Based on the backtrace you've provided, this doesn't seem like a multicast related issue. I skimmed wpa_supplicant and I see that whilst it requests a link-layer multicast address, it does not use IPv4 multicast. Vany Serezhkin wrote: > Hello. > > I do not really sure in this, but : > > after the current updated to > 20090309 Merge IGMPv3 and Source-Specific Multicast (SSM) to the FreeBSD > IPv4 stack. > > I can't use any wpa_supplicant related networks. > > It faulted in any WPA authentications , that i tried. > Also it faulted when i try to login via 802.1x in my job network. General questions: Are you running any routing protocols on this machine, or anything which opens a multicast socket at system startup? Do you have more than one processor core enabled? Can you transcribe the console panic message so we can see which process has panicked in the routing socket path? thanks, BMS