This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| vpn-wireguard [2025/10/22 21:35] – [Interface] -Correct Poll Interval explanation, per pedro's advice. hogwild | vpn-wireguard [2025/11/19 20:30] (current) – [Problem: Traffic flowing in one Direction] -Change to: " hogwild | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| Note that tabs or other interface components in your menus may be different colours, depending on which web interface theme is chosen in the Admin Access menu. | Note that tabs or other interface components in your menus may be different colours, depending on which web interface theme is chosen in the Admin Access menu. | ||
| - | This HOWTO: | + | For an introduction to WireGuard, and some basic theory, the [[wireguard_on_freshtomato|Set up WireGuard]] |
| Unless using an external VPN provider, it's best to " | Unless using an external VPN provider, it's best to " | ||
| 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) | ||
| - | If we can' | + | This causes FreshTomato to ping 1.1.1.1 via the WireGuard interface. If no reply is received in time, the wg service |
| - | + | ||
| - | * 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. \\ \\ | + | |
| - | * Default: 0. This disables the feature, so packets are sent only\\ as needed. This is fine for most users not behind restrictive NAT. | + | |
| \\ | \\ | ||
| Line 484: | Line 481: | ||
| * Remote LAN IP | * Remote LAN IP | ||
| - | | + | |
| \\ | \\ | ||
| + | |||
| + | |||
| + | ==== Problem: Traffic flowing in only one Direction ==== | ||
| \\ | \\ | ||
| + | |||
| + | Sometimes, it may occur that from one end of your setup (" | ||
| + | |||
| + | 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 " | ||