On Wed, May 02, 2018 at 11:52:18AM +0200, Stefan Sperling wrote:
> On Wed, May 02, 2018 at 12:30:30PM +0300, Paul Irofti wrote:
> > On Mon, Apr 30, 2018 at 10:55:22AM +0200, Stefan Sperling wrote:
> > > + /*
> > > + * During a scan on 5Ghz, prefer RSSI measured for probe
> > > +
On Wed, May 02, 2018 at 12:30:30PM +0300, Paul Irofti wrote:
> On Mon, Apr 30, 2018 at 10:55:22AM +0200, Stefan Sperling wrote:
> > + /*
> > +* During a scan on 5Ghz, prefer RSSI measured for probe
> > +* response frames. i.e. don't allow beacons to lower the
> > +
On Mon, Apr 30, 2018 at 10:55:22AM +0200, Stefan Sperling wrote:
> I've ran into what seems to be a fairly modern dual-band AP (issued
> by a French ISP). This AP camps on channel 112. This channel requires
> radar detection which may explain the behaviour described below.
>
> The AP sends 5GHz be
On 2018 Apr 30 (Mon) at 10:55:22 +0200 (+0200), Stefan Sperling wrote:
:Setting aside concerns about my lack of understanding of the underlying
:reason for this behaviour, the hack below is sufficient to make this AP
:show up as a strong contender in the candidate list and be preferred
:over 2GHz a
On Tue, May 01, 2018 at 10:06:54PM -0500, Patrick Dohman wrote:
> I believe you are correct to correlate RSSI & probe response.
> My understanding is that 802.11 beacon is a management frame to synchronize
> networks.
> Essentially the beacon interval determines the multiple for the DTIM & may
>
I believe you are correct to correlate RSSI & probe response.
My understanding is that 802.11 beacon is a management frame to synchronize
networks.
Essentially the beacon interval determines the multiple for the DTIM & may
include additional capability frames.
The beacon blinks at a configurable
On Tue, May 01, 2018 at 10:22:22AM +0100, Stuart Henderson wrote:
> On 2018/05/01 10:48, Stefan Sperling wrote:
> > > On 2018/04/30 11:08, Stefan Sperling wrote:
> > > > Derp. A dBm value of -10 would of course be better than -60.
> > > >
> > > > Whatever the numbers shown by tcpdump really mean,
On 2018/05/01 10:48, Stefan Sperling wrote:
> > On 2018/04/30 11:08, Stefan Sperling wrote:
> > > Derp. A dBm value of -10 would of course be better than -60.
> > >
> > > Whatever the numbers shown by tcpdump really mean, the probe response's
> > > one is better!!!
> >
> > Better as in "more accu
On Mon, Apr 30, 2018 at 01:35:59PM +0100, Stuart Henderson wrote:
> On 2018/04/30 10:55, Stefan Sperling wrote:
> > The AP sends 5GHz beacons with a ridicously low RSSI while no client
> > is connected, and OpenBSD prefers the 2GHz band...
>
> Surely it has to be the receiver that is adding the RS
On 2018/04/30 10:55, Stefan Sperling wrote:
> The AP sends 5GHz beacons with a ridicously low RSSI while no client
> is connected, and OpenBSD prefers the 2GHz band...
Surely it has to be the receiver that is adding the RSSI infornation?
The AP can't know.
Seems it would either have to be the cli
On Mon, Apr 30, 2018 at 10:55:22AM +0200, Stefan Sperling wrote:
> tcpdump confirms that beacons are received with a low RSSI of -10dBm
> Whereas probe responses consistently arrive with much more promising
> RSSI values of about -60dBm:
Derp. A dBm value of -10 would of course be better than -60
I've ran into what seems to be a fairly modern dual-band AP (issued
by a French ISP). This AP camps on channel 112. This channel requires
radar detection which may explain the behaviour described below.
The AP sends 5GHz beacons with a ridicously low RSSI while no client
is connected, and OpenBSD
12 matches
Mail list logo
