31 Dec
2020
31 Dec
'20
3:14 a.m.
I think we discuss about 2 different sides of our network coin.
On one hand we have the end users, which may have very little networking
or IT knowledge, and on the other the potential POP sysops.
While on the POP side the implementation and maintainance of the system
is done by knowledgeable persons, and so may actually implement whatever
interconnection protocols we like (including the existing full mesh IPIP
wich is quite fit for the current task except encryption), the user part
should be kept as simple and OS agnostic as possible.
That is why I push with the usage of well known protocols on the user
side, so that the end user can use basically cheap home routers or even
single computers/tablets/phones to achieve 44net connectivity .
What happens between POPs is another story, and the sky is the limit.
But a first practical approach is to keep existing IPIP ful mesh between
POPs which needs a minimal effort, while moving regular clients to
another VPN star topology to increase the accessibility of the network.
Marius, YO2LOJ
On 30.12.2020 18:22, Toussaint OTTAVI via 44Net wrote:
Le 30/12/2020 à 16:06, Rob PE1CHL via 44Net a écrit :
Ok, that is not my opinion. I think we should avoid running into
traps like "let us choose that new wireguard as the
standard protocol to be used by everything" as we would again exclude
everything outside of Linux and OpenWRT
and end up in the same situation as we now are with IPIP mesh: always
requiring the user to install a Linux box.
I'm not talking about choosing a specific protocol. I'm talking about
using a platform that allows installation of standard open-source
software (including the specific software we may need to write for
specific tasks). Too many of us had previous (bad) experiences with
closed software, hardware or service provider. We'd like to be able to
get rid of it completely, HI :-)