FreshTomato Wiki

User Tools

Site Tools

Trace: • vpn-wireguard
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/09/29 18:44] – [Status] -Move description of first block of text above screenshot hogwildvpn-wireguard [2025/11/11 00:07] (current) – [General Troubleshooting] -Change to "point of failure you find" hogwild
Line 99: Line 99:
  \\  \\
  
-**Poll Interval** - WireGuard's PersistentKeepalive setting.+**Poll Interval** - a watchdog timer for the WireGuard connection (in minutes)
  
-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.\\  \\ FIXME
- +
- \\+
  
   * 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 434: Line 432:
  
 If a link is up, the handshake done and the tunnel established, you should see the peer's interface ID, and the the time of the latest handshake process. You should also see real-time traffic data such as bytes transmitted (tx) and bytes received (rx). These details confirm the tunnel is established and data is flowing through it. If a link is up, the handshake done and the tunnel established, you should see the peer's interface ID, and the the time of the latest handshake process. You should also see real-time traffic data such as bytes transmitted (tx) and bytes received (rx). These details confirm the tunnel is established and data is flowing through it.
 +
 + \\
  
 For example, for this WireGuard instance: For example, for this WireGuard instance:
- 
- 
  
 The first block of text includes this router's: The first block of text includes this router's:
Line 445: Line 443:
   - Public key   - Public key
   - UDP listening port   - UDP listening port
- 
- \\ 
- 
  
  \\ \\ {{::vpn-wireguard-status-2025.3.png?473}}  \\ \\ {{::vpn-wireguard-status-2025.3.png?473}}
  
 \\ \\
- 
-The first block of text includes this router's: 
- 
-  - WireGuard Interface name 
-  - Interface's alias (if set) 
-  - Public key 
-  - UDP listening port 
- 
- \\ 
  
 The second block of text displays the Peer's: \\ The second block of text displays the Peer's: \\
Line 498: Line 484:
     * Remote LAN IP     * Remote LAN IP
  
- \\  The point of failure found will provide critical insight into the type of issue you are facing.+ \\  The point of failure you find will provide critical insight into the type of issue you are facing.
  
  \\  \\
vpn-wireguard.1759167874.txt.gz · Last modified: by hogwild

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki