init writing over benchmark
This commit is contained in:
61
main.tex
61
main.tex
@@ -83,8 +83,8 @@
|
||||
% THESIS INFORMATION
|
||||
%----------------------------------------------------------------------------------------
|
||||
|
||||
\thesistitle{Development and Verification of a Theoretical Model for
|
||||
the Clan Framework} % Your thesis title, this is used in the title
|
||||
\thesistitle{Decrypting the Overlay: A Reproducible Analysis of P2P
|
||||
VPN Implementation and Overhead} % Your thesis title, this is used in the title
|
||||
% and abstract, print it elsewhere with \ttitle
|
||||
\supervisor{\textsc{Ber Lorke}} % Your supervisor's name, this is
|
||||
% used in the title page, print it elsewhere with \supname
|
||||
@@ -217,25 +217,43 @@ and Management}} % Your department's name and URL, this is used in
|
||||
|
||||
\begin{abstract}
|
||||
\addchaptertocentry{\abstractname} % Add the abstract to the table of contents
|
||||
This thesis investigates Clan, an open-source framework for machine
|
||||
configuration management in peer-to-peer networks. The research
|
||||
focuses on its capabilities as a unified source of truth for
|
||||
managing distributed systems. Underpinning this analysis are key
|
||||
technologies: ZeroTier, Mycelium, and the "Data Mesher," a
|
||||
conflict-free replicated database supporting decentralized operations.
|
||||
|
||||
The study examines three main aspects critical to evaluating Clan's
|
||||
efficacy: fault tolerance, scalability, and security. Fault
|
||||
tolerance is analyzed in the context of network disruptions and
|
||||
node failures. Scalability is evaluated through theoretical models
|
||||
and real-world implementations to measure system performance under
|
||||
varying loads. Security is tested through targeted attack scenarios
|
||||
to assess the framework's resilience to potential threats.
|
||||
This thesis evaluates the performance and fault tolerance of
|
||||
peer-to-peer mesh VPNs through an automated, reproducible
|
||||
benchmarking framework
|
||||
built on the Clan deployment system.
|
||||
We establish a cloud API–independent, binary-reproducible environment
|
||||
for deploying and assessing various VPN implementations,
|
||||
including Tailscale (via Headscale), Hyprspace, Lighthouse, Tinc,
|
||||
and ZeroTier.
|
||||
|
||||
To simulate real-world network conditions, we employ four impairment profiles
|
||||
with varying degrees of packet loss, reordering, latency, and jitter.
|
||||
Our benchmark suite comprises RIST video streaming, Nix cache downloads,
|
||||
iperf3 throughput tests, QUIC transfers, and ping latency measurements.
|
||||
The experiments run on three machines interconnected at 1\,Gbps,
|
||||
each equipped with four CPU cores and eight threads.
|
||||
In total, we evaluate ten VPNs across seven benchmarks and four
|
||||
impairment profiles,
|
||||
yielding over 300 unique measurements.
|
||||
|
||||
Our analysis reveals that Tailscale outperforms the Linux kernel's
|
||||
default networking stack under degraded network conditions—a
|
||||
counterintuitive finding
|
||||
we investigate through source code analysis of packet handling,
|
||||
encryption schemes, and resilience mechanisms.
|
||||
This investigation also uncovered several critical security vulnerabilities
|
||||
across the evaluated VPNs.
|
||||
|
||||
We validate our hypotheses by re-running benchmarks with tuned
|
||||
Linux kernel parameters,
|
||||
demonstrating measurable improvements in network throughput.
|
||||
This work contributes to decentralized networking research
|
||||
by providing an extensible framework for reproducible P2P benchmarks,
|
||||
offering insights into overlay VPN implementation quality,
|
||||
and demonstrating that default Linux kernel settings are suboptimal
|
||||
for adverse network conditions.
|
||||
|
||||
By comprehensively addressing these three aspects, this thesis aims
|
||||
to provide a detailed evaluation of Clan and its supporting
|
||||
technologies, particularly in the management of distributed
|
||||
peer-to-peer systems.
|
||||
\end{abstract}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
@@ -246,9 +264,8 @@ and Management}} % Your department's name and URL, this is used in
|
||||
\addchaptertocentry{\acknowledgementname} % Add the
|
||||
% acknowledgements to the table of contents
|
||||
|
||||
I am very grateful to my team members Mic92, Lassulus, W, Hsjobeki,
|
||||
DavHau, Kenji, Paul and Timo with whom
|
||||
I worked together with to create the Clan framework.
|
||||
I am very grateful to my work collegues Mic92, Lassulus, W, Hsjobeki,
|
||||
DavHau and Pinpox with whom I worked together to create the Clan framework.
|
||||
As well as my supervisor, Ber Lorke, for his guidance and support
|
||||
during my research.
|
||||
His advice and feedback have been invaluable.
|
||||
|
||||
Reference in New Issue
Block a user