Intel 9260NGW (beacon) signal average values off

2018-05-02 Thread Gerrit Renker
A user with 4.15.11-1~bpo9+1 Debian kernel reported the following problem with Intel 9260NGW in a Dell XPS 13: the following nl80211 reported values were off [1]: * signal average (NL80211_STA_INFO_SIGNAL_AVG) reported as +72 dBm * beacon signal average (NL80211_STA_INFO_BEACON_SIGNAL_AVG) repo

Re: [WEXT/nl80211] few API questions

2015-11-02 Thread Gerrit Renker
Thanks a lot indeed, it is helping a good step forward. Gerrit -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[WEXT/nl80211] few API questions

2015-10-31 Thread Gerrit Renker
I have a few short nl80211 API questions to help convert a userland program from WEXT to nl80211 [1]. The iw code has been helpful, and I have used bits of it so far. When it comes to kernel components, though, I don't understand that code well enough; so I'd appreciate help with the following:

Re: [WEXT]: multiple calls for SIOCGIWSTATS return same value

2015-06-09 Thread Gerrit Renker
On Tue, 09 Jun 2015 09:33:08 +0200 Johannes Berg wrote: > > There is a similar behaviour for scan results: the signal levels reported > > for stations remain the same for all subsequent calls. Previously these > > also changed with time and position of receiver. > > You mean BSSes, not stations

Re: [WEXT]: multiple calls for SIOCGIWSTATS return same value

2015-06-08 Thread Gerrit Renker
> On Sat, 2015-06-06 at 20:37 -0600, Gerrit Renker wrote: > > A problem has been found in recent kernels where multiple > > calls using SIOCGIWSTATS return the same, identical value. > > Which "value"? I believe these return a number of different values. What >

[WEXT]: multiple calls for SIOCGIWSTATS return same value

2015-06-06 Thread Gerrit Renker
A problem has been found in recent kernels where multiple calls using SIOCGIWSTATS return the same, identical value. This behaviour is observable both using 'iwconfig ' and wavemon info screen, where it was reported in [1]. It looks as if this is a WEXT issue, since on the same system multiple '