From owner-freebsd-wireless@FreeBSD.ORG  Tue Sep  6 16:50:11 2011
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5F298106566C
	for <freebsd-wireless@hub.freebsd.org>;
	Tue,  6 Sep 2011 16:50:05 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 5B8168FC14
	for <freebsd-wireless@hub.freebsd.org>;
	Tue,  6 Sep 2011 16:50:05 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p86Go5U9050920
	for <freebsd-wireless@freefall.freebsd.org>;
	Tue, 6 Sep 2011 16:50:05 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p86Go5NV050919;
	Tue, 6 Sep 2011 16:50:05 GMT (envelope-from gnats)
Date: Tue, 6 Sep 2011 16:50:05 GMT
Message-Id: <201109061650.p86Go5NV050919@freefall.freebsd.org>
To: freebsd-wireless@FreeBSD.org
From: Mark Linimon <linimon@lonesome.com>
Cc: 
Subject: Re: kern/160391: [ieee80211] [patch] Panic in mesh mode
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mark Linimon <linimon@lonesome.com>
List-Id: "Discussions of 802.11 stack,
	tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2011 16:50:11 -0000

The following reply was made to PR kern/160391; it has been noted by GNATS.

From: Mark Linimon <linimon@lonesome.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/160391: [ieee80211] [patch] Panic in mesh mode
Date: Tue, 6 Sep 2011 11:44:06 -0500

 ----- Forwarded message from Edgar Martinez <emartinez@kbcnetworks.com> -----
 
 Date: Tue, 6 Sep 2011 08:39:56 -0700
 From: Edgar Martinez <emartinez@kbcnetworks.com>
 To: Adrian Chadd <adrian@freebsd.org>
 Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>,
 	"freebsd-bugs@freebsd.org" <freebsd-bugs@freebsd.org>
 Subject: RE: kern/160391: [ieee80211] [patch] Panic in mesh mode
 
 Will provide dumps soon.
 
 But yes, effectively, two physical radios on a single board.
 
 Each configured in mesh mode. 
 
 When they are both configured the same (channel/meshid/etc), and see
 each other, bad things happen. - Easy fix is to MAC filter.
 
 When they are both configured differently (channel/meshid/etc), and see
 each other, via the network, bad things happen. - Easy fix is to MAC
 filter.
 
 Interesting phenomena I am tracking down...sometimes the local and peer
 addresses are three characters vs four...and then of course its b0rkeD...
 a reboot sometimes cleans it right up, and things run...
 
 Finally, there's no mechanism to manually flush out the mesh info, yet,
 so I also noticed that it appears the routes just stop updating...
 
 I've been too busy to root cause many issues, and have only focused on
 the show-stoppers...but I really need to...
 
 ----- End forwarded message -----