User Tools
vpn-wireguard
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| vpn-wireguard [2025/09/15 03:52] – [Peer's Parameters] -Clarify Source IP Filtering explanation hogwild | vpn-wireguard [2025/11/11 00:07] (current) – [General Troubleshooting] -Change to "point of failure you find" hogwild | ||
|---|---|---|---|
| Line 66: | Line 66: | ||
| ===== Wireguard Configuration ===== | ===== Wireguard Configuration ===== | ||
| - | WireGuard uses virtual network adapters (or " | + | WireGuard uses virtual network adapters (or " |
| - | WireGuard allows you to create 3 separate | + | WireGuard allows you to create 3 separate network |
| \\ | \\ | ||
| Line 89: | Line 89: | ||
| ===== Interface ===== | ===== Interface ===== | ||
| - | Settings here are used to configure the router' | + | Settings here are used to configure the router' |
| \\ | \\ | ||
| Line 99: | Line 99: | ||
| \\ | \\ | ||
| - | **Poll Interval** - WireGuard's PersistentKeepalive setting. | + | **Poll Interval** - a watchdog timer for the WireGuard |
| - | This determines how often clients behind NAT send keepalive packets to maintain NAT mappings. | + | If we can't ping 1.1.1.1 via the WireGuard interface, wg is restarted.\\ |
| - | + | ||
| - | \\ | + | |
| * The recommended setting is 25 seconds. This causes WireGuard \\ to send a small packet to its peer every 25 seconds when no \\ other traffic occurs. This keeps the connection alive through \\ NAT or firewalls that might otherwise close idle UDP sessions. \\ \\ | * The recommended setting is 25 seconds. This causes WireGuard \\ to send a small packet to its peer every 25 seconds when no \\ other traffic occurs. This keeps the connection alive through \\ NAT or firewalls that might otherwise close idle UDP sessions. \\ \\ | ||
| Line 226: | Line 224: | ||
| ===== Peer Parameters ===== | ===== Peer Parameters ===== | ||
| - | In this area, you can manually configure Peer settings. Some fields populate automatically if you import a configuration file instead of/in addition to manually entering settings. | + | Here, you can manually configure Peer settings. Some fields populate automatically if you import a configuration file instead of/in addition to manually entering settings. |
| **Router behind NAT** - sets whether/how often keepalive packets are sent from the router to defined peers. | **Router behind NAT** - sets whether/how often keepalive packets are sent from the router to defined peers. | ||
| Line 246: | Line 244: | ||
| **Allowed IPs** - here, enter the IP address ranges to be routed through the particular peer. | **Allowed IPs** - here, enter the IP address ranges to be routed through the particular peer. | ||
| - | Outgoing packets bound for addresses in the " | + | Outgoing packets bound for addresses in the " |
| \\ | \\ | ||
| Line 276: | Line 274: | ||
| (As set in the Network menu). | (As set in the Network menu). | ||
| - | | + | |
| - | + | ||
| - | **Forward all peer traffic** - adding an Allowed IP of " | + | |
| \\ | \\ | ||
| Line 295: | Line 291: | ||
| ===== Import Config from file ===== | ===== Import Config from file ===== | ||
| - | Available since r2025.3, this lets you quickly and easily import a pre-generated WireGuard configuration file. This file can come from an external VPN provider, or other source, such as another WireGuard endpoint. Files must be compatible with the wg-quick format (usually ending in " | + | Available since r2025.3, this lets you quickly and easily import a pre-generated WireGuard configuration file. This file can come from an external VPN provider, or another WireGuard endpoint. Files must be compatible with the wg-quick format (usually ending in " |
| Typically, with an external VPN provider, you choose appropriate settings on their website for the configuration you want. The VPN provider then generates a corresponding configuration file to import. For most providers, this will be a wg-quick compatible file. | Typically, with an external VPN provider, you choose appropriate settings on their website for the configuration you want. The VPN provider then generates a corresponding configuration file to import. For most providers, this will be a wg-quick compatible file. | ||
| - | While FreshTomat' | + | Even though FreshTomato |
| - | '' | + | For example, to display all variables and their settings for the " |
| + | |||
| + | "nvram show|grep wg0_" | ||
| + | |||
| + | \\ | ||
| - | will display all variables and their settings for interface " | + | The only exception occurs when you copy a configuration file to a folder on the router and enter a path to that file in the //Config File// field. In that case, that file will be saved as a configuration file, in wg-quick format. |
| \\ | \\ | ||
| Line 432: | Line 432: | ||
| If a link is up, the handshake done and the tunnel established, | If a link is up, the handshake done and the tunnel established, | ||
| + | |||
| + | \\ | ||
| For example, for this WireGuard instance: | For example, for this WireGuard instance: | ||
| - | |||
| - | \\ \\ {{:: | ||
| - | |||
| - | \\ | ||
| The first block of text includes this router' | The first block of text includes this router' | ||
| Line 446: | Line 444: | ||
| - UDP listening port | - UDP listening port | ||
| - | \\ | + | \\ \\ {{:: |
| + | |||
| + | \\ | ||
| The second block of text displays the Peer' | The second block of text displays the Peer' | ||
| Line 484: | Line 484: | ||
| * Remote LAN IP | * Remote LAN IP | ||
| - | | + | |
| \\ | \\ | ||
vpn-wireguard.1757904758.txt.gz · Last modified: by hogwild
Page Tools
