This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
vpn-wireguard [2025/08/08 20:38] – [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 ===== | ===== 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. | Policy-based Routing and the kill switch feature are supported since r2025.3. Split-tunneling is supported within Policy-based Routing. | ||
Line 26: | Line 26: | ||
These VPN providers' | These VPN providers' | ||
+ | * Coming soon: IVPN | ||
* Integrity VPN | * Integrity VPN | ||
* NordVPN | * NordVPN | ||
Line 46: | Line 47: | ||
\\ \\ | \\ \\ | ||
- | {{:: | + | {{:: |
- | + | ||
- | \\ {{:: | + | |
- | + | ||
- | \\ | + | |
{{:: | {{:: | ||
This may take time, especially on slower routers. | This may take time, especially on slower routers. | ||
+ | |||
+ | \\ \\ {{:: | ||
\\ | \\ | ||
Line 121: | Line 120: | ||
\\ | \\ | ||
- | **Public Key** - here, enter the public key for the VPN tunnel. | + | **Public Key** - displays |
+ | |||
+ | This is automatically generated by WireGuard from the Private Key. This field cannot be directly edited. | ||
\\ | \\ | ||
Line 127: | Line 128: | ||
**VPN Interface IP** - the IP address to be assigned to the virtual network interface. | **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' | + | This is used only to communicate //inside// the tunnel. It is independent from the physical network interface' |
- | For example: " | + | It must be written using CIDR notation. |
- | \\ **DNS Servers (out)** - the nameservers the client device will use for DNS lookups once the tunnel is active. | + | \\ \\ **DNS Servers (out)** - the nameservers the client device will use for DNS lookups once the tunnel is active. |
These can be: | These can be: | ||
Line 137: | Line 138: | ||
* Internal (private) to the VPN, such as a DNS resolver reachable only via the VPN. | * Internal (private) to the VPN, such as a DNS resolver reachable only via the VPN. | ||
* Public, such as Google DNS (8.8.8.8) or Cloudflare (1.1.1.1). | * Public, such as Google DNS (8.8.8.8) or Cloudflare (1.1.1.1). | ||
+ | |||
+ | \\ | ||
This setting is the same as the “DNS” setting in a wg-quick configuration file | This setting is the same as the “DNS” setting in a wg-quick configuration file | ||
Line 166: | Line 169: | ||
\\ | \\ | ||
- | **Firewall** - here, choose the firewall setting | + | **Firewall** - lets you choose the appropriate |
\\ | \\ | ||
- | * **Create NAT on tunnel** - enables NAT on the VPN tunnel | + | * **Create NAT on tunnel** - enables NAT on the VPN interface. Essentially, |
* When this setting is on, packets traveling through the tunnel are NATed, meaning their source IP is translated to match the tunnel or server IP, allowing for easier outbound access from the client network without needing explicit routing rules back from destination networks. | * When this setting is on, packets traveling through the tunnel are NATed, meaning their source IP is translated to match the tunnel or server IP, allowing for easier outbound access from the client network without needing explicit routing rules back from destination networks. | ||
* This is especially useful if the VPN clients are on private or overlapping IP ranges, or if the destination network only knows about the server IP. | * This is especially useful if the VPN clients are on private or overlapping IP ranges, or if the destination network only knows about the server IP. | ||
Line 192: | Line 195: | ||
Depending on which setting you choose, other fields will appear in which to configure more settings. | 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:// |
**Redirect Internet traffic** | **Redirect Internet traffic** | ||
Line 198: | Line 201: | ||
\\ | \\ | ||
- | {{:: | + | {{:: |
+ | |||
+ | | ||