mirror of
https://github.com/kernelkit/infix.git
synced 2026-08-05 23:23:02 +02:00
Mattias Walström
7e5da21cf6
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:/>
57 lines
1.5 KiB
Plaintext
57 lines
1.5 KiB
Plaintext
=== WireGuard Roadwarrior
|
|
|
|
ifdef::topdoc[:imagesdir: {topdoc}../../test/case/interfaces/wireguard_roadwarrior]
|
|
|
|
==== Description
|
|
|
|
This test demonstrates a realistic roadwarrior scenario where clients
|
|
connect through an internet router to reach a VPN server.
|
|
|
|
Set up a WireGuard server with 2 roadwarrior clients connecting through
|
|
a router that simulates the internet. Each client is on a different subnet
|
|
behind the router, and has a private network that should be accessible
|
|
through the VPN tunnel.
|
|
|
|
This test verifies:
|
|
|
|
- WireGuard tunnel establishment through an intermediate router
|
|
- Roadwarrior clients on different subnets
|
|
- Access to server's private network through the VPN tunnel
|
|
- Routing between client networks and server network via WireGuard
|
|
|
|
Topology:
|
|
....
|
|
Server ---- Router ---- Client1
|
|
(VPN) (Internet) \---- Client2
|
|
|
|
WAN: 192.168.100.0/24
|
|
Server: 192.168.100.1
|
|
Router: 192.168.100.2
|
|
|
|
Client1 link: 192.168.50.0/24 (Router LAN1)
|
|
Client2 link: 192.168.51.0/24 (Router LAN2)
|
|
|
|
WireGuard tunnel: 10.0.0.0/24
|
|
Server: 10.0.0.1/24
|
|
Client1: 10.0.0.2/24
|
|
Client2: 10.0.0.3/24
|
|
|
|
Backend networks:
|
|
Server data: 192.168.0.0/24
|
|
Client1 data: 192.168.1.0/24
|
|
Client2 data: 192.168.2.0/24
|
|
....
|
|
|
|
==== Topology
|
|
|
|
image::topology.svg[WireGuard Roadwarrior topology, align=center, scaledwidth=75%]
|
|
|
|
==== Sequence
|
|
|
|
. Set up topology and attach to target DUTs
|
|
. Configure DUTs
|
|
. Check on the server that both clients is connected
|
|
. Verify IPv4 connectivity with ping 192.168.0.2 from host:data1 and host:data2
|
|
|
|
|