Date: Fri, 22 Feb 2013 10:04:39 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Bernhard Schmidt <bschmidt@techwires.net> Cc: freebsd-bugs@freebsd.org, PseudoCylon <moonlightakkiy@yahoo.ca>, freebsd-wireless@freebsd.org Subject: Re: kern/176201: [net80211] [patch] 11n station includes unrelated ht params into ASSOC_REQ packet Message-ID: <CAJ-VmomCtXoDWfpc%2B-XK-xBFb7dCCzPtrLDMegCT%2BZWL1Ye=xQ@mail.gmail.com> In-Reply-To: <201302221859.31446.bschmidt@techwires.net> References: <201302180246.r1I2kocv064092@freefall.freebsd.org> <201302221859.31446.bschmidt@techwires.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hm, we need to use MIN(rxmax) and MAX(density) regardless, right? If an AP is transmitting to a STA that has a lower rxmax or higher density, it should obey that. The same rules apply for mesh, ibss, tdma operational modes. So yes, what we should do is: * initialise rxmax/density with the VAP capabilities * track what the remote node rxmax/density is * have a couple of functions that return the density and rxmax based on the destination node and current VAP config * teach the 11n drivers to use that. Thanks, Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomCtXoDWfpc%2B-XK-xBFb7dCCzPtrLDMegCT%2BZWL1Ye=xQ>