* change type of next_node.name
* create domain entry for each entry and add to dnsmasq configuration

[Matthias Schiffer: reword documentation]

This is currently only implemented in the gluon-mesh-vpn-fastd
package.

Advertising the public key may be deemed problematic when
your threat-model involves protecting the nodes privacy
from tunnel traffic correlation by onlink observers.

It can be enabled by setting site.mesh_vpn.fastd.pubkey_privacy
to `false`.

[Matthias Schiffer: rebase]

fixes an error and removes the focus on ath10k

defaults to 11s, allowing to build devices without IBSS-support

obsoletes GLUON_ATH10K_MESH

Without -v, hexdump would sometimes replace duplicate bytes with "*" and
a newline.

Adding the fact that GLUON_RELEASE is needed with 'make manifest'
if it is used with 'make'.

This fact was mentioned in the v2017.1 release notes but is not (clearly)
mentioned inside other parts of the documentation.

Signed-off-by: Chrissi^ <chris@tinyhost.de>

[Matthias Schiffer: minor rewording]

To reduce the number of packages that need to be listed in
GLUON_SITE_PACKAGES, this adds a new variable GLUON_FEATURES. Sets of
packages are enabled automatically based on the combination of listed
feature flags.

Site-specified package feeds can provide their own feature flag
definitions.

The next-node MAC address doesn't need to be unique in different
communities, so we can as well add a default value.

The SSID for the mesh network should be cryptic, otherwise some users will try to connect to that network and have a bad user experience.

The fastd_mesh_vpn site.conf section is renamed to mesh_vpn.fastd.

This was introduced in ffhh-packages at https://github.com/freifunkhamburg/ffhh-packages/tree/master/gluon-config-mode-reboot-ffhh