Differences

This shows you the differences between two versions of the page.

--- vpn-wireguard [2025/08/08 20:43] – [Interface] hogwild
+++ vpn-wireguard [2025/08/13 04:46] (current) – [Current development status] -Add warning about no IPv6 support to intro hogwild
@@ Line 12: / Line 12: @@
 ===== Current development status =====
-The WireGuard web interface menu has been working since r2024.1.
+The WireGuard web interface menu has been working since r2024.1. IPv4 is fully supported, but IPv6 is not supported at this time.
 Policy-based Routing and the kill switch feature are supported since r2025.3. Split-tunneling is supported within Policy-based Routing.
@@ Line 47: / Line 47: @@
  \\ \\
-{{::vpn-wireguard-down-2025.3.png?73}}    indicates the Wireguard service isn't running and no VPN tunnel is currently established on this interface.
+{{::vpn-wireguard-down-2025.3.png?73}}    indicates the Wireguard service isn't running and no VPN tunnel is currently established on this interface.  \\  \\
-\\ {{::vpn-wireguard-up-2025.3.png?76}}    indicates the selected WireGuard connection is running, and connected to the configured peers.
- \\
 {{::vpn-wireguard-start_now-2025.3.png?80}}   clicking this starts the WireGuard service, and makes the interface negotiate a VPN tunnel to peers.
 This may take time, especially on slower routers.
+ \\ \\ {{::vpn-wireguard-up-2025.3.png?76}}    indicates the selected WireGuard connection is running, and connected to the configured peers.
  \\
@@ Line 122: / Line 120: @@
  \\
-**Public Key** - here, enter the public key for the VPN tunnel.
+**Public Key** - displays the tunnel's public key.
+This is automatically generated by WireGuard from the Private Key. This field cannot be directly edited.
  \\
@@ Line 128: / Line 128: @@
 **VPN Interface IP** - the IP address to be assigned to the virtual network interface.
-This is used only to communicate //inside// the tunnel. It is independent from the physical network interface's IP addresses. It must be written using CIDR notation.
+This is used only to communicate //inside// the tunnel. It is independent from the physical network interface's IP addresses. To prevent addressing conflicts on participating networks or VPN peers, this must be a unique address space, specifically set aside for the VPN.
-For  example: "10.0.0.1/32". Addresses should be separated by commas or newline characters.
+It must be written using CIDR notation. For  example: "10.0.0.1/32". Addresses should be separated by commas or newline characters.
  \\ \\ **DNS Servers (out)** - the nameservers the client device will use for DNS lookups once the tunnel is active.
@@ Line 195: / Line 195: @@
 Depending on which setting you choose, other fields will appear in which to configure more settings.
- \\
+To learn about WireGuard topologies, see this webpage: [[https://www.procustodibus.com/blog/2020/10/wireguard-topologies/|Procustodibus: Primary WireGuard Topologies]]\\  \\
 **Redirect Internet traffic**
@@ Line 201: / Line 201: @@
 \\
-{{::vpn-wireguard-peers_tab-2025.3.png?87|Peers}} in this tab, enter information about the peer parameters.  \\   \\  Status
+{{::vpn-wireguard-peers_tab-2025.3.png?87|Peers}} in this tab, enter information about the peer parameters.
+ \\ \\   \\  Status

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools