On Wed, May 31, 2017 at 01:25:36PM +0200, Mark Kettenis wrote:
> > Date: Wed, 31 May 2017 11:53:19 +0200
> > From: Stefan Sperling
> >
> > On Wed, May 31, 2017 at 11:23:07AM +0200, Mark Kettenis wrote:
> > > Is the beacon interval always the same for all modes/hardware?
> >
> >
> Date: Wed, 31 May 2017 11:53:19 +0200
> From: Stefan Sperling
>
> On Wed, May 31, 2017 at 11:23:07AM +0200, Mark Kettenis wrote:
> > Is the beacon interval always the same for all modes/hardware?
>
> It is defined by the AP. The value (in TU) is sent to clients in beacons:
>
On Wed, May 31, 2017 at 11:23:07AM +0200, Mark Kettenis wrote:
> Is the beacon interval always the same for all modes/hardware?
It is defined by the AP. The value (in TU) is sent to clients in beacons:
# tcpdump -n -i iwn0 -y IEEE802_11_RADIO -vv
11:50:23.170309 802.11 flags=0<>: beacon,
-p -r1.78 ieee80211_var.h
> --- net80211/ieee80211_var.h 30 May 2017 11:00:38 - 1.78
> +++ net80211/ieee80211_var.h 31 May 2017 08:34:47 -
> @@ -262,7 +262,7 @@ struct ieee80211com {
> int ic_max_nnodes; /* max length of ic_nnodes */
>
int ic_max_nnodes; /* max length of ic_nnodes */
u_int16_t ic_lintval; /* listen interval */
int16_t ic_txpower; /* tx power setting (dBm) */
- u_int16_t ic_bmisstimeout;/* beacon miss threshol