Browse Source

adhoc

master
zeus 3 years ago
parent
commit
04270b5332
  1. BIN
      network-adhoc/modules/ROOT/images/adhoc.png
  2. BIN
      network-adhoc/modules/ROOT/images/bidirectional-communication.png
  3. BIN
      network-adhoc/modules/ROOT/images/docker-images.png
  4. BIN
      network-adhoc/modules/ROOT/images/fluent-mongo.png
  5. BIN
      network-adhoc/modules/ROOT/images/gynamic-swarm.png
  6. BIN
      network-adhoc/modules/ROOT/images/intro.png
  7. BIN
      network-adhoc/modules/ROOT/images/nvc.png
  8. BIN
      network-adhoc/modules/ROOT/images/nvc1.png
  9. BIN
      network-adhoc/modules/ROOT/images/openweb.png
  10. 1
      network-adhoc/modules/ROOT/images/replica-set-primary-with-two-secondaries.bakedsvg.svg
  11. BIN
      network-adhoc/modules/ROOT/images/swarm-poc.png
  12. BIN
      network-adhoc/modules/ROOT/images/swarm-poc1.png
  13. BIN
      network-adhoc/modules/ROOT/images/swarmlab-connect.png
  14. BIN
      network-adhoc/modules/ROOT/images/trafic.png
  15. BIN
      network-adhoc/modules/ROOT/images/types-of-mounts-bind.png
  16. BIN
      network-adhoc/modules/ROOT/images/vehigle.png
  17. BIN
      network-adhoc/modules/ROOT/images/vue-modules.png
  18. BIN
      network-adhoc/modules/ROOT/images/vue.png
  19. 15
      network-adhoc/modules/ROOT/pages/index-setup.adoc
  20. 26
      network-adhoc/modules/ROOT/pages/index.adoc

BIN
network-adhoc/modules/ROOT/images/adhoc.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 146 KiB

BIN
network-adhoc/modules/ROOT/images/bidirectional-communication.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

BIN
network-adhoc/modules/ROOT/images/docker-images.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 125 KiB

BIN
network-adhoc/modules/ROOT/images/fluent-mongo.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 27 KiB

BIN
network-adhoc/modules/ROOT/images/gynamic-swarm.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 24 KiB

BIN
network-adhoc/modules/ROOT/images/intro.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 70 KiB

BIN
network-adhoc/modules/ROOT/images/nvc.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 24 KiB

BIN
network-adhoc/modules/ROOT/images/nvc1.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 7.9 KiB

BIN
network-adhoc/modules/ROOT/images/openweb.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 35 KiB

1
network-adhoc/modules/ROOT/images/replica-set-primary-with-two-secondaries.bakedsvg.svg

File diff suppressed because one or more lines are too long

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
network-adhoc/modules/ROOT/images/swarm-poc.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 58 KiB

BIN
network-adhoc/modules/ROOT/images/swarm-poc1.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 58 KiB

BIN
network-adhoc/modules/ROOT/images/swarmlab-connect.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 216 KiB

BIN
network-adhoc/modules/ROOT/images/trafic.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 97 KiB

BIN
network-adhoc/modules/ROOT/images/types-of-mounts-bind.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 23 KiB

BIN
network-adhoc/modules/ROOT/images/vehigle.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 98 KiB

BIN
network-adhoc/modules/ROOT/images/vue-modules.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 70 KiB

BIN
network-adhoc/modules/ROOT/images/vue.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 70 KiB

15
network-adhoc/modules/ROOT/pages/index-setup.adoc

@ -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
== Install systemd-networkd == Install systemd-networkd
=== deinstall classic networking and install it! === deinstall classic networking and install it!
@ -295,3 +304,9 @@ echo ""
echo "ping -c3 raspberrypi.local" echo "ping -c3 raspberrypi.local"
echo "" echo ""
---- ----
* https://raspberrypi.stackexchange.com/questions/94047/how-to-setup-an-unprotected-ad-hoc-ibss-network-and-if-possible-with-wpa-encry/94048#94048[origin^]

26
network-adhoc/modules/ROOT/pages/index.adoc

@ -2,31 +2,23 @@
image::ROOT:swarmlab.png[swarmlab,150,float=right] image::ROOT:swarmlab.png[swarmlab,150,float=right]
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
====
https://www.researchgate.net/publication/272497022_The_Role_of_Ad_Hoc_Networks_in_the_Internet_of_Things_A_Case_Scenario_for_Smart_Environments[More here^]

Loading…
Cancel
Save