@ -6,6 +6,15 @@ TIP: Tested on a Raspberry Pi with "Buster"
networkd is a small and lean service to configure network interfaces, designed mostly for server use cases in a world with hotplugged and virtualized networking. Its configuration is similar in spirit and abstraction level to ifupdown, but you don't need any extra packages to configure bridges, bonds, vlan etc. It is not very suitable for managing WLANs yet; NetworkManager is still much more appropriate for such Desktop use cases.
networkd is a small and lean service to configure network interfaces, designed mostly for server use cases in a world with hotplugged and virtualized networking. Its configuration is similar in spirit and abstraction level to ifupdown, but you don't need any extra packages to configure bridges, bonds, vlan etc. It is not very suitable for managing WLANs yet; NetworkManager is still much more appropriate for such Desktop use cases.
There are mainly three setups to have a peer to peer network:
* unprotected ad-hoc interface by configuring the WiFi device
* unprotected ad-hoc interface using wpa_supplicant (Recommended)
* Only with suitable (RSN-IBSS capable) USB dongle:
* protected ad-hoc interface using wpa_supplicant and WPA encryption (best solution if possible)
* ad-hoc interface with additional USB/WiFi dongle for uplink to internet router
The "data collector" is a lightweight microservice application that collect and sends metadata, collected from a system, such as an IoT network, distributed system, data center, etc to a storage system.
A *wireless ad hoc network (WANET)* or *mobile ad hoc network (MANET)* is a decentralized type of wireless network.
* The data are transmitted, stored, and can be retrieved at any time.
The network is ad hoc because it *does not rely on a pre-existing infrastructure*, such as routers in wired networks or access points in wireless networks. Instead, each node participates in routing by forwarding data for other nodes, so the determination of which nodes forward data is made dynamically on the basis of network connectivity and the routing algorithm in use.
*"data collector"* are developed with a platform agnostic"container-based application strategy
[NOTE]
====
A platform-agnostic approach offers many choices
.Ad Hoc Networks
image::ROOT:adhoc.png[swarmlab,250,float=right]
* Can be seamlessly moved from local development machine to production deployments
.Vehicle-to-Vehicle (V2V) communications
image::ROOT:vehigle.png[swarmlab,250,float=right]
* Flexibility, Reliability
.Vehicle-to-Infrastructure (V2I) communications
image::ROOT:trafic.png[swarmlab,250,float=right]
** Avoiding Vendor Lock-In
* From Code to full-blown systems
** from a single container on your local machine
** to a running cloud native - container-based environment