kern/160391: [ieee80211] [patch] Panic in mesh mode

[Mark Linimon]

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

From: Mark Linimon <linimon at lonesome.com>
To: bug-followup at 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 at kbcnetworks.com> -----
 
 Date: Tue, 6 Sep 2011 08:39:56 -0700
 From: Edgar Martinez <emartinez at kbcnetworks.com>
 To: Adrian Chadd <adrian at freebsd.org>
 Cc: "freebsd-net at freebsd.org" <freebsd-net at freebsd.org>,
 	"freebsd-bugs at freebsd.org" <freebsd-bugs at 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 -----