Site Tools


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/12 20:10] – [Interface] -Remove inappropriate Keepalive text hogwildvpn-wireguard [2025/11/19 20:30] (current) – [Problem: Traffic flowing in one Direction] -Change to: " hogwild
Line 101: Line 101:
 **Poll Interval** - a watchdog timer for the WireGuard connection (in minutes) **Poll Interval** - a watchdog timer for the WireGuard connection (in minutes)
  
-This causes FreshTomato to ping 1.1.1.1 via the WireGuard interface, if not reply is received in time, the wg services is restarted.\\  \\ +This causes FreshTomato to ping 1.1.1.1 via the WireGuard interface. If no reply is received in time, the wg service is restarted.\\  \\ 
- +
  \\  \\
  
Line 481: Line 481:
     * Remote LAN IP     * Remote LAN IP
  
- \\  The point of failure you find will provide critical insight into the type of issue you are facing.+ \\  The point of failure you find will guide you in understanding what type of issue you are facing.
  
  \\  \\
 +
 +
 +==== Problem: Traffic flowing in only 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.
 +
 +It this occurs, please check that there are default routes setup from B to A. Also, please check that on the client side, (in this case, end B), the "Inbound firewall" option is disabled. On the server side, make sure to add the client's subnet, so it knows how to route traffic from the server back to the client.
  
  
vpn-wireguard.1762978223.txt.gz · Last modified: by hogwild