FreshTomato Wiki

User Tools

Site Tools

Trace: • vpn-pptp • advanced-vlan • schedule_wol • tools-wol • one_off_reboot • media_bridge • advanced-routing • nas-ups • advanced-ctnf • forward-upnp
vpn-wireguard

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
vpn-wireguard [2025/11/14 17:03] – [General Troubleshooting] -Formatting hogwildvpn-wireguard [2026/03/08 21:42] (current) – pedro
Line 12: Line 12:
  
 Note that WireGuard only supports UDP stream, not TCP. Note that WireGuard only supports UDP stream, not TCP.
- 
  
 ===== Current development status ===== ===== Current development status =====
Line 35: Line 34:
   * Integrity VPN   * Integrity VPN
   * NordVPN   * NordVPN
-  * PIA (Private Internet Access+  * PIA (Private Internet Access)
   * ProtonVPN   * ProtonVPN
   * SurfShark   * SurfShark
Line 46: Line 45:
 [[https://www.linksysinfo.org/index.php?threads/wireguard-on-freshtomato.76295/page-23#post-348056|How to Connect to a VPN Provider's WireGuard Tunnel on FreshTomato]] [[https://www.linksysinfo.org/index.php?threads/wireguard-on-freshtomato.76295/page-23#post-348056|How to Connect to a VPN Provider's WireGuard Tunnel on FreshTomato]]
  
 +===== Scripts =====
 +
 +The Scripts tab allows you to define custom shell commands that are executed automatically at specific stages of the WireGuard interface lifecycle. This is useful for starting or stopping additional services, adding firewall rules (e.g. iptables), or configuring custom routing when the tunnel comes up or goes down. \\ \\  There are four script hooks available:
 +
 +  * Pre-Up Script – runs before the interface is brought up
 +  * Post-Up Script – runs after the interface has been brought up
 +  * Pre-Down Script – runs before the interface is taken down
 +  * Post-Down Script – runs after the interface has been taken down
 +
 +To reference the current WireGuard interface name dynamically within any script, use ''%i'' (without quotes) — it will be substituted with the actual interface name at runtime (e.g. wg0, wg1, etc.).
 +
 +Example:
 +
 +>iptables -A FORWARD -i %i -j ACCEPT
  
 ===== Status ===== ===== Status =====
Line 62: Line 75:
  
 {{::vpn-wireguard-stop_now-2025.3.png?76}}   terminates the current WireGuard VPN tunnel and stops the service. {{::vpn-wireguard-stop_now-2025.3.png?76}}   terminates the current WireGuard VPN tunnel and stops the service.
- 
  
 ===== Wireguard Configuration ===== ===== Wireguard Configuration =====
Line 85: Line 97:
  
 {{::vpn-wireguard-config_tab-2025.3.png?95}}  here, enter the main configuration settings for the chosen interface. {{::vpn-wireguard-config_tab-2025.3.png?95}}  here, enter the main configuration settings for the chosen interface.
- 
  
 ===== Interface ===== ===== Interface =====
Line 217: Line 228:
   * Routing Policy - this lets you create rules, specifying which devices \\ or destination addresses/subnets should have their Internet traffic \\ routed through the VPN or directly to the internet, without encryption. \\ This can include "split-tunneling". \\ \\    * Routing Policy - this lets you create rules, specifying which devices \\ or destination addresses/subnets should have their Internet traffic \\ routed through the VPN or directly to the internet, without encryption. \\ This can include "split-tunneling". \\ \\ 
   * Routing Policy (Strict) - only explicitly-defined traffic will go through the\\ tunnel. All other traffic is excluded and can't use the tunnel.   * Routing Policy (Strict) - only explicitly-defined traffic will go through the\\ tunnel. All other traffic is excluded and can't use the tunnel.
- 
  
 ===== Peer Parameters ===== ===== Peer Parameters =====
Line 284: Line 294:
  
  \\  \\
- 
  
 ===== Import Config from file ===== ===== Import Config from file =====
Line 315: Line 324:
  
 {{::vpn-wireguard-peers_tab-2025.3.png?95|Peers}} in this tab, you enter settings for the peer devices. {{::vpn-wireguard-peers_tab-2025.3.png?95|Peers}} in this tab, you enter settings for the peer devices.
- 
  
 ===== Peers ===== ===== Peers =====
- 
  
 This section allows you to enter and view settings for all peers of this WireGuard interface/instance. This section allows you to enter and view settings for all peers of this WireGuard interface/instance.
Line 363: Line 370:
  
 \\ \\
- 
  
 ===== Peer's Parameters ===== ===== Peer's Parameters =====
Line 422: Line 428:
  
 {{::vpn-wireguard-peers-peers_parameters-add_to_peers-2025.3.png?80}} clicking this adds all completed settings in the section to the [Peers] section in the WireGuard Configuration file. \\   \\   \\ {{::vpn-wireguard-peers-peers_parameters-clean-2025.3.png?80}}** **clicking this will clear all fields in this section, but won't save those changes until you click Save. {{::vpn-wireguard-peers-peers_parameters-add_to_peers-2025.3.png?80}} clicking this adds all completed settings in the section to the [Peers] section in the WireGuard Configuration file. \\   \\   \\ {{::vpn-wireguard-peers-peers_parameters-clean-2025.3.png?80}}** **clicking this will clear all fields in this section, but won't save those changes until you click Save.
- 
  
 ===== Status ===== ===== Status =====
Line 452: Line 457:
   - Latest Handshake performed   - Latest Handshake performed
   - Number of bytes sent and received by this peer   - Number of bytes sent and received by this peer
- 
  
 ===== WireGuard Notes and Troubleshooting ===== ===== WireGuard Notes and Troubleshooting =====
Line 465: Line 469:
  
  \\  \\
- 
  
 ==== General Troubleshooting ==== ==== General Troubleshooting ====
 +
 + \\
  
 Please remember these troubleshooting tips when trying to configure your VPN: Please remember these troubleshooting tips when trying to configure your VPN:
Line 483: Line 488:
  \\  \\
  
 +==== Problem: Traffic flowing in only one Direction ====
  
-==== Problem: Traffic flowing in one Direction ====+ \\
  
 Sometimes, it may occur that from one end of your setup ("A)", you can ping devices and both VPN virtual interfaces at the other end ("B"), however, from end B, you cannot ping the remote router or devices or the client VPN virtual interface at end A. Sometimes, it may occur that from one end of your setup ("A)", you can ping devices and both VPN virtual interfaces at the other end ("B"), however, from end B, you cannot ping the remote router or devices or the client VPN virtual interface at end A.
vpn-wireguard.1763139783.txt.gz · Last modified: by hogwild

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki