mirror of https://github.com/kernelkit/infix.git synced 2026-07-22 01:13:00 +02:00

Files

T

Mattias Walström 7e5da21cf6 Add support for WireGuard

Almost full support for WireGuard

admin@server:/> show interface wg0
name                : wg0
type                : wireguard
index               : 10
mtu                 : 1420
operational status  : up
ipv4 addresses      : 10.0.0.1/24 (static)
ipv6 addresses      : fd00::1/64 (static)
peers               : 2

  Peer 1:
    public key        : ROaZyvJc5DzA2XUAAeTj2YlwDsy2w0lr3t+rWj2imAk=
    status            : UP
    endpoint          : 192.168.10.2:51821
    latest handshake  : 2025-12-09T22:51:38+00:00
    transfer tx       : 1412 bytes
    transfer rx       : 1324 bytes

  Peer 2:
    public key        : Om9CPLYdK3l93GauKrq5WXo/gbcD+1CeqFpobRLLkB4=
    status            : UP
    endpoint          : 2001:db8:3c4d:20::2:51822
    latest handshake  : 2025-12-09T22:51:38+00:00
    transfer tx       : 1812 bytes
    transfer rx       : 428 bytes
in-octets           : 1752
out-octets          : 3224

admin@server:/>

2026-01-09 11:11:32 +01:00

3.3 KiB

Raw Blame History

VPN Configuration

A Virtual Private Network (VPN) creates encrypted tunnels over public networks, enabling secure communication between remote locations or users. Unlike plain tunnels (GRE, VXLAN) that only provide encapsulation, VPNs add authentication and encryption to protect data confidentiality and integrity.

Configuring VPN

For detailed configuration instructions and examples, see:

WireGuard VPN - Complete guide to configuring WireGuard tunnels, including site-to-site, road warrior, and hub-and-spoke topologies.

Understanding VPN Tunnels

VPN tunnels establish secure connections across untrusted networks by:

Authentication: Verifying the identity of tunnel endpoints using cryptographic keys or certificates
Encryption: Protecting data confidentiality with strong ciphers
Integrity: Detecting tampering through message authentication codes

This makes VPNs essential for connecting sites over the internet, enabling remote access for mobile users, and securing traffic in untrusted environments.

VPN Deployment Models

VPNs are typically deployed in one of several models:

Site-to-Site VPN

Figure: Site-to-Site VPN connecting two office networks

Connects entire networks across locations, creating a unified private network over the internet. Routers or firewalls at each site maintain persistent tunnels, allowing seamless access between locations.

Use case: Connecting branch offices to headquarters
Characteristics: Always-on, connects networks not individual devices
Example: Main office (192.168.1.0/24) ↔ Branch office (192.168.2.0/24)

Remote Access VPN (Road Warrior)

Figure: Mobile clients connecting to corporate network

Enables individual users to securely access a private network from remote locations. Clients initiate connections as needed from dynamic IP addresses.

Use case: Remote employees accessing corporate resources
Characteristics: On-demand, handles dynamic endpoints and roaming
Example: Mobile laptop ↔ Corporate network

Hub-and-Spoke VPN

Figure: Hub-and-Spoke topology with central hub routing traffic between spokes

A central hub connects to multiple remote sites (spokes), routing traffic between them. Spokes don't connect directly to each other but communicate through the hub.

Use case: Central office connecting multiple remote locations
Characteristics: Centralized control, simplified management
Example: HQ ↔ (Branch A, Branch B, Branch C)

VPN Protocol Comparison

Different VPN protocols offer varying trade-offs between security, performance, and complexity:

Protocol	Complexity	Performance	Use Case
WireGuard	Simple	Very High	Modern deployments, all models
IPsec	Complex	High	Legacy systems, compliance reqs
OpenVPN	Moderate	Moderate	Maximum compatibility

Infix supports WireGuard as its primary VPN solution, offering the best balance of simplicity, security, and performance for modern networks.

3.3 KiB Raw Blame History