improved motivation
This commit is contained in:
@@ -5,7 +5,7 @@
|
||||
\label{Methodology}
|
||||
|
||||
This chapter describes the methodology used to benchmark peer-to-peer
|
||||
overlay VPN implementations. The experimental design prioritizes
|
||||
mesh VPN implementations. The experimental design prioritizes
|
||||
reproducibility at every layer---from dependency management to network
|
||||
conditions---enabling independent verification of results and
|
||||
facilitating future comparative studies.
|
||||
@@ -58,13 +58,13 @@ mesh topologies. Table~\ref{tab:vpn_selection} summarizes the selection.
|
||||
\hline
|
||||
Tailscale (Headscale) & Coordinated mesh & Open-source coordination server \\
|
||||
ZeroTier & Coordinated mesh & Global virtual Ethernet \\
|
||||
Nebula & Lighthouse-based mesh & Slack's overlay network \\
|
||||
Tinc & Decentralized mesh & Established since 1998 \\
|
||||
Nebula & Coordinated mesh & Slack's overlay network \\
|
||||
Tinc & Fully decentralized & Established since 1998 \\
|
||||
Yggdrasil & Fully decentralized & Spanning-tree routing \\
|
||||
Mycelium & Fully decentralized & End-to-end encrypted IPv6 overlay \\
|
||||
Hyprspace & Fully decentralized & libp2p-based, IPFS-compatible \\
|
||||
EasyTier & Decentralized mesh & Rust-based, multi-protocol \\
|
||||
VpnCloud & Decentralized mesh & Lightweight, kernel bypass option \\
|
||||
EasyTier & Fully decentralized & Rust-based, multi-protocol \\
|
||||
VpnCloud & Fully decentralized & Lightweight, kernel bypass option \\
|
||||
WireGuard & Point-to-point & Reference baseline (not a mesh VPN) \\
|
||||
\hline
|
||||
Internal (no VPN) & N/A & Baseline for raw network performance \\
|
||||
@@ -359,6 +359,17 @@ isolated from stateful interactions typical in imperative package
|
||||
management. This property is essential for ensuring identical test
|
||||
environments across benchmark runs.
|
||||
|
||||
\subsection{A Comparative Study on Virtual Private Networks}
|
||||
|
||||
Lackorzynski et al.\ \cite{lackorzynski_comparative_2019} evaluate
|
||||
VPN protocols in the context of industrial communication systems (Industry 4.0),
|
||||
benchmarking OpenVPN, IPSec, Tinc, Freelan, MACsec, and WireGuard.
|
||||
Their analysis focuses on point-to-point protocol performance---throughput,
|
||||
latency, and CPU overhead---rather than overlay network behavior.
|
||||
In contrast, this thesis evaluates VPNs that provide a full data plane
|
||||
with peer-to-peer connectivity, NAT traversal, and dynamic peer discovery.
|
||||
|
||||
|
||||
\subsection{Full-Mesh VPN Performance Evaluation}
|
||||
|
||||
Kjorveziroski et al.\ \cite{kjorveziroski_full-mesh_2024} provide a
|
||||
@@ -377,11 +388,4 @@ This thesis extends their work in several ways:
|
||||
\item Fully reproducible experimental framework via Nix/NixOS/Clan
|
||||
\end{itemize}
|
||||
|
||||
\subsection{Low Maintenance Peer-to-Peer Overlays}
|
||||
|
||||
Shukla et al.\ propose integrating Software Defined Networks with
|
||||
DHT-based P2P overlays to reduce maintenance overhead
|
||||
\cite{shukla_towards_2021}. Their work on aligning overlay topology
|
||||
with physical networks is relevant to understanding the performance
|
||||
characteristics of mesh VPNs that must discover and maintain peer
|
||||
connectivity dynamically.
|
||||
|
||||
@@ -75,7 +75,7 @@ evidence-based comparison of peer-to-peer overlay VPN implementations.
|
||||
Existing research on this topic remains sparse.
|
||||
One notable work from 2024, ``Full-mesh VPN performance evaluation
|
||||
for a secure edge-cloud continuum'' \cite{kjorveziroski_full-mesh_2024},
|
||||
benchmarks a subset of overlay VPNs but focuses primarily
|
||||
benchmarks a subset of mesh VPNs but focuses primarily
|
||||
on solutions with a central point of failure.
|
||||
In contrast, this thesis evaluates more widely adopted mesh VPNs
|
||||
with an emphasis on fully decentralized architectures.
|
||||
|
||||
Reference in New Issue
Block a user