Date: Fri, 22 Feb 2013 10:48:48 -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-VmonXhBfxKMAD4EqhksqOKwVffQeE=JJ%2BR0qdifwAowcBkA@mail.gmail.com> In-Reply-To: <201302221947.24307.bschmidt@techwires.net> References: <201302180246.r1I2kocv064092@freefall.freebsd.org> <201302221933.25718.bschmidt@techwires.net> <CAJ-Vmom9sE0dMXCp2Tn=DUFTGhgpH%2BW2uDHpv5VeDL3%2B3RgJsw@mail.gmail.com> <201302221947.24307.bschmidt@techwires.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ah, damn. Sorry. I was thinking about the node versus vap configuration and got confused. IBSS is the same as the APmode of operation - you advertise what you're capable of and sending stations just calculate the MIN(ampdusize) and MAX(ampdudensity) when sending to you. Exactly the same needs to be done for AP mode. STA mode should do the same too - it just happens there's only one node (the AP.) We have the same issue with 2040, shortgi, stbc, ldpc - ni_htparams includes what the peer node has, not necessarily what you've negotiated. So in the ath(4) driver I needed to look at both what _my_ capabilities are _and_ the remote capabilities before I decide whether to use 40mhz, shortgi, etc. It'd be shinier if there were some net80211 functions that did this for me. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonXhBfxKMAD4EqhksqOKwVffQeE=JJ%2BR0qdifwAowcBkA>