Kernel Panic when in mesh mode How-To-Repeat: create two mesh nodes, pass traffic
Responsible Changed From-To: freebsd-bugs->freebsd-net Over to maintainer(s).
Responsible Changed From-To: freebsd-net->freebsd-wireless Over to maintainer(s).
----- Forwarded message from Adrian Chadd <adrian@freebsd.org> ----- Date: Tue, 6 Sep 2011 18:07:41 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Edgar Martinez <emartinez@kbcnetworks.com> Cc: freebsd-net@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/160391: [ieee80211] [patch] Panic in mesh mode Hi Edgar, Can you please provide; * A dmesg, just so we can see what/how many radios; * what do you mean by "create two mesh nodes" - do you mean two mesh nodes on the same board, one on each radio? Thanks, Adrian ----- End forwarded message -----
----- 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 -----
batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Keyword: patch or patch-ready – in lieu of summary line prefix: [patch] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>