- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

wtap should not set the IEEE80211_F_DATAPAD flag;

Approved by: adrian (mentor)

wtap fix malloc/free.

* Remove malloc/free pointer cast;
* Check return value from malloc;

Submitted by: glebius
Approved by: adrian (mentor)

wtap should check if ieee80211_vap_setup fails.

* If ieee80211_vap_setup fails, we free allocated M_80211_VAP
memory and return NULL;

Approved by: adrian (mentor)

wtap: fix clang warning.

* The warning message was:
'warning error: format string is not a string literal';
* Changed how make_dev is called, now a string literal
for formatting is used;

Approved by: adrian (mentor)

Mechanically substitute flags from historic mbuf allocator with
malloc(9) flags in sys/dev.

Don't grab an unreferenced pointer to the VAP bss node.

Fix wtap to not panic in wtap_beacon_intrp.

* Changed KASSERT to be debug printf (DWTAP_PRINTF). If state is not
IEEE80211_S_RUN we return without scheduling a new callout;
* When net80211 stack changes state to IEEE802_11_INIT we stop the
beacon callout task;

Remove this - it's not needed as it's defined in ieee80211_freebsd.h.

Correctly calculate the callout interval for beacon generation.

Submitted by: monthadar@gmail.com

Enforce that wtap requires VIMAGE to be useful.

Remove direct access to si_name.

Code should just use the devtoname() function to obtain the name of a
character device. Also add const keywords to pieces of code that need it
to build properly.

MFC after: 2 weeks

Introduce wtap, the beginnings of a net80211 wlan simulator.

This introduces:

* a basic wtap interface
* a HAL, which implements an abstraction layer for implementing
different device behavious;
* A visibility plugin, which allows for control over which nodes
see other nodes (useful for mesh work.)

It doesn't yet implement sta/adhoc/hostap modes but these are quite
feasible to implement.

Monthadar uses it to do 802.11s mesh verification.

The userland tools will be committed in a follow-up commit.

Submitted by: Monthadar Al Jaberi <monthadar@gmail.com>