Commit 1d4d61d2 authored by Rouven Czerwinski's avatar Rouven Czerwinski

overview: add design choices

Signed-off-by: default avatarRouven Czerwinski <rouven@czerwinskis.de>
parent 7e20611c
......@@ -22,3 +22,37 @@ wireless service as an AP or to a local LAN via a seperate ethernet port on the
node. Client nodes are usually embedded wireless routers flashed with the FFBS
firmware.
================
Desgin Choices
================
During the design of the new Freifunk Infrastructure several desgin choices had
to be made, these are outlined here.
Use Routing everywhere and Mesh where needed
============================================
In the classical B.A.T.M.A.N. infrastructure,
the whole network is built upon layer two,
which includes every node in the network.
This results in broadcast traffic having to be sent to every node as well.
Routing information is also shared across the network,
resulting in a baseline traffic on every node,
even when the node itself is not actively communicating with the network.
In contrast, for this new infrastructure we are using routing between the
individual nodes and only employ the meshing protocol for routers which do not
have their own network connection.
Rely on modern VPN
==================
The fastd infrastructure is great,
but not especially fast on small nodes.
Recent developments have brought forth Wireguard,
which allows even the smallest routers (e.g. WR841N) to achieve speeds
to almost saturate a VDSL 50Mbit-Link (40MBit/s in our Last test).
This removes the long standing limitation of the small nodes not being
especially fast.
Together with the routing approach it should allow for faster network speeds for
all users.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment