This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
vpn-wireguard [2025/08/13 21:00] – [Interface] hogwild | vpn-wireguard [2025/08/13 22:38] (current) – [Interface] -punctuation hogwild | ||
---|---|---|---|
Line 5: | Line 5: | ||
WireGuard can be configured/ | WireGuard can be configured/ | ||
- | To configure WireGuard // | + | To configure WireGuard // |
Unless using an external VPN provider, it's best to " | Unless using an external VPN provider, it's best to " | ||
Line 47: | Line 47: | ||
\\ \\ | \\ \\ | ||
- | {{:: | + | {{:: |
{{:: | {{:: | ||
- | This may take time, especially on slower routers. | + | \\ {{:: |
- | \\ \\ {{:: | + | |
- | + | ||
- | \\ | + | |
{{:: | {{:: | ||
Line 105: | Line 103: | ||
**Config file** - here, enter the path to a WireGuard configuration file. | **Config file** - here, enter the path to a WireGuard configuration file. | ||
+ | |||
+ | If a path/file is specified here, all other settings in the web interface will be ignored.\\ | ||
\\ | \\ | ||
Line 122: | Line 122: | ||
**Public Key** - displays the tunnel' | **Public Key** - displays the tunnel' | ||
- | This is automatically generated by WireGuard | + | WireGuard |
\\ | \\ | ||
Line 128: | 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 to communicate |
It must be written using CIDR notation. For example: " | It must be written using CIDR notation. For example: " | ||
Line 140: | Line 140: | ||
\\ | \\ | ||
+ | |||
+ | This is usually wanted in site-to-site topology VPNs.\\ | ||
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 168: | ||
**Respond to DNS** - enables dnsmasq to resolve DNS queries arriving on this interface. | **Respond to DNS** - enables dnsmasq to resolve DNS queries arriving on this interface. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Routing Mode -** Here, select the mode to used on the WireGuard interface. | ||
+ | |||
+ | This option appears only when one of the Internal hub-and-spoke or mesh VPN types is selected.\\ | ||
+ | |||
+ | * Off - FreshTomato won't add any routing rules for the the\\ WireGuard interface.\\ | ||
+ | * Auto - choosing this means the WireGuard interface will be routed \\ using the default table (the same number as the interface port)\\ | ||
+ | * Custom Table - this option will route the WireGuard interface \\ using a custom table number. If you choose this option, you must \\ include the table number in the additional field. | ||
+ | |||
+ | \\ | ||
\\ | \\ | ||
Line 174: | Line 188: | ||
* **Create NAT on tunnel** - enables Network Address Translation on the tunnel.\\ When checked, FreshTomato rewrites the source addresses \\ of packets going through the tunnel, making them appear as if \\ they originated from the router itself (using the router’s VPN tunnel IP), \\ rather than from their original LAN addresses. \\ \\ This helps VPN clients behind the tunnel to access external networks, \\ such as the Internet. It can also simplify routing by hiding the client' | * **Create NAT on tunnel** - enables Network Address Translation on the tunnel.\\ When checked, FreshTomato rewrites the source addresses \\ of packets going through the tunnel, making them appear as if \\ they originated from the router itself (using the router’s VPN tunnel IP), \\ rather than from their original LAN addresses. \\ \\ This helps VPN clients behind the tunnel to access external networks, \\ such as the Internet. It can also simplify routing by hiding the client' | ||
- | * **Inbound Firewall** - adds firewall rules to let inbound Wireguard traffic | + | * **Inbound Firewall** - adds firewall rules to let inbound Wireguard traffic |
| | ||
Line 184: | Line 198: | ||
* Hub and Spoke - All peers can only communicate via the Hub. | * Hub and Spoke - All peers can only communicate via the Hub. | ||
* Full Mesh (defined Endpoint only) - FreshTomato will try to create \\ a full mesh among peers with EndPoint defined. | * Full Mesh (defined Endpoint only) - FreshTomato will try to create \\ a full mesh among peers with EndPoint defined. | ||
- | * Full Mesh: FreshTomato will try to establish a full mesh \\ between all peers. | + | * Full Mesh - FreshTomato will try to establish a full mesh \\ between all peers. |
* External VPN Provider - FreshTomato will try to establish \\ a VPN connection with an external VPN provider. | * External VPN Provider - FreshTomato will try to establish \\ a VPN connection with an external VPN provider. | ||
\\ | \\ | ||
- | Depending on which setting you choose, other fields will appear in which to configure more settings. | + | Depending on the setting you choose, other fields will appear in which to configure more settings. |
To learn about WireGuard topologies, see this webpage: [[https:// | To learn about WireGuard topologies, see this webpage: [[https:// | ||
- | **Redirect Internet traffic** | + | **Redirect Internet traffic |
+ | |||
+ | \\ | ||
+ | |||
+ | * \\ | ||
+ | * All \\ | ||
+ | * Routing Policy \\ | ||
+ | * Routing Policy (Strict) | ||
\\ | \\ |