On 09/28/2018 12:19 AM, Johannes Berg wrote:
On Thu, 2018-09-27 at 08:32 -0700, Ben Greear wrote:
It seems though that if there's some noise or so on the channel you
wouldn't be transmitting, so what kind of "network glitches" might
affect this? AP going away unexpectedly for some time?
I
On Thu, 2018-09-27 at 08:32 -0700, Ben Greear wrote:
> > It seems though that if there's some noise or so on the channel you
> > wouldn't be transmitting, so what kind of "network glitches" might
> > affect this? AP going away unexpectedly for some time?
>
> I am thinking that if the 'timeout'
On 09/27/2018 12:12 AM, Johannes Berg wrote:
On Wed, 2018-09-26 at 15:21 -0700, Ben Greear wrote:
Now only 4 retries per frame, but it seems mac80211 is all 5 of its
null-data probes within a few miliseconds. Is that expected, or should
there be a bit more pause between each of the probe
On Wed, 2018-09-26 at 15:21 -0700, Ben Greear wrote:
>
> Now only 4 retries per frame, but it seems mac80211 is all 5 of its
> null-data probes within a few miliseconds. Is that expected, or should
> there be a bit more pause between each of the probe requests to better
> weather periodic
On 09/26/2018 11:48 AM, Johannes Berg wrote:
On Wed, 2018-09-26 at 11:47 -0700, Ben Greear wrote:
I think I'll start by making sure the firmware does not do software retransmits
for frames from the driver (self-gen frames are OK to be retransmitted I guess).
You do want it to be doing
On 09/26/2018 11:48 AM, Johannes Berg wrote:
On Wed, 2018-09-26 at 11:47 -0700, Ben Greear wrote:
I think I'll start by making sure the firmware does not do software retransmits
for frames from the driver (self-gen frames are OK to be retransmitted I guess).
You do want it to be doing
On Wed, 2018-09-26 at 11:47 -0700, Ben Greear wrote:
> > > I think I'll start by making sure the firmware does not do software
> > > retransmits
> > > for frames from the driver (self-gen frames are OK to be retransmitted I
> > > guess).
> >
> > You do want it to be doing retries for frames
On 09/26/2018 11:26 AM, Johannes Berg wrote:
On Wed, 2018-09-26 at 11:04 -0700, Ben Greear wrote:
I have been running with mac80211/mlme.c's max_nullfunc_tries set to 5 for many
years.
Long ago it helped with connectivity issues with lots of vdevs and and/orloaded
APs
if I recall correctly.
On Wed, 2018-09-26 at 11:04 -0700, Ben Greear wrote:
> I have been running with mac80211/mlme.c's max_nullfunc_tries set to 5 for
> many years.
> Long ago it helped with connectivity issues with lots of vdevs and
> and/orloaded APs
> if I recall correctly.
That's different, that's the number
On 09/26/2018 01:38 AM, Johannes Berg wrote:
On Tue, 2018-09-25 at 16:12 -0700, Ben Greear wrote:
While testing out some other issue, I noticed that my ath10k system creates
several hundred null-data probes when I abruptly down the AP the station
is connected to.
I guess this is because I use
On Tue, 2018-09-25 at 16:12 -0700, Ben Greear wrote:
> While testing out some other issue, I noticed that my ath10k system creates
> several hundred null-data probes when I abruptly down the AP the station
> is connected to.
>
> I guess this is because I use the mac80211 stack to handle the
While testing out some other issue, I noticed that my ath10k system creates
several hundred null-data probes when I abruptly down the AP the station
is connected to.
I guess this is because I use the mac80211 stack to handle the probes, and
the firmware then retries each mac80211 probe many
12 matches
Mail list logo
