This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
vpn-wireguard [2024/03/27 15:49] – [Current development] -grammar, formatting hogwild | vpn-wireguard [2024/04/16 16:51] (current) – [Type of VPN] -change "amongst" to "between" hogwild | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | The FreshTomato Wireguard | + | FreshTomato' |
- | ===== Current development ===== | + | ===== Current development |
- | The Wireguard GUI menu is currently a work in progress. Some basic functionality | + | The Wireguard GUI menu is currently a work in progress. Some basic functionality |
* External VPN provider connectivity | * External VPN provider connectivity | ||
Line 17: | Line 17: | ||
\\ | \\ | ||
- | Because of this, you should focus on on site-to-site configurations until that changes. | + | For this reason, you should focus on on site-to-site configurations until that status |
===== Type of VPN ===== | ===== Type of VPN ===== | ||
- | {{: | + | |
- | This setting | + | {{: |
- | * Hub and Spoke = any peer can only communicate via the Hub. | + | |
- | * Full Mesh - Endpoint only = will try to create a full mesh but only amongst | + | This setting |
- | * Full Mesh = will try to establish a full mesh amongst | + | |
- | * External VPN Provider | + | * Hub and Spoke: Any peers can only communicate via the Hub. |
+ | * Full Mesh (defined | ||
+ | * Full Mesh: FreshTomato | ||
+ | * External VPN Provider | ||
===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
- | While you try to configure your own VPN please | + | |
- | * **wg show** (command line) will help you understand the relationship between peers | + | When trying |
- | * **route** can help you verifying | + | |
- | * **traceroute** is a must use when verifying end-to-end connectivity, a good approach is to test in order: | + | ***wg show** (via the command line) output |
- | | + | ***route** |
- | | + | ***traceroute** is a must when verifying end-to-end connectivity. A good approach is to test the following |
- | | + | *Local LAN IP |
- | | + | *Local VPN IP |
- | The point where this fail provides a crucial | + | *Remote VPN IP |
+ | *Remote LAN IP | ||
+ | |||
+ | The point of failure will provide critical | ||