This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
vpn-wireguard [2024/04/16 16:49] – [Troubleshooting] -formatting hogwild | vpn-wireguard [2024/04/16 16:51] (current) – [Type of VPN] -change "amongst" to "between" hogwild | ||
---|---|---|---|
Line 6: | Line 6: | ||
- | ===== Current development ===== | + | ===== Current development |
- | The Wireguard GUI menu is currently a work in progress. Some basic functionality is already | + | The Wireguard GUI menu is currently a work in progress. Some basic functionality is working |
* External VPN provider connectivity | * External VPN provider connectivity | ||
Line 28: | Line 28: | ||
* Hub and Spoke: Any peers can only communicate via the Hub. | * Hub and Spoke: Any peers can only communicate via the Hub. | ||
* Full Mesh (defined Endpoint only): FreshTomato will try to create a full mesh but only among peers which have the EndPoint defined. | * Full Mesh (defined Endpoint only): FreshTomato will try to create a full mesh but only among peers which have the EndPoint defined. | ||
- | * Full Mesh: FreshTomato will try to establish a full mesh amongst | + | * Full Mesh: FreshTomato will try to establish a full mesh between |
* External VPN Provider - This option is greyed out, as the function is still a work in progress. | * External VPN Provider - This option is greyed out, as the function is still a work in progress. | ||
Line 36: | Line 36: | ||
When trying to configure your VPN, please remember these troubleshooting tips: | When trying to configure your VPN, please remember these troubleshooting tips: | ||
- | * **wg show** (via the command line) output will help you understand the relationship between peers. | + | ***wg show** (via the command line) output will help you understand the relationship between peers. |
- | * **route** (via the command line) can help you to verify routing decisions while the VPN is connected. | + | ***route** (via the command line) can help you to verify routing decisions while the VPN is connected. |
- | * **traceroute** is a must when verifying end-to-end connectivity. A good approach is to test the following in order: | + | ***traceroute** is a must when verifying end-to-end connectivity. A good approach is to test the following in order: |
- | * Local LAN IP | + | *Local LAN IP |
- | * Local VPN IP | + | *Local VPN IP |
- | * Remote VPN IP | + | *Remote VPN IP |
- | * Remote LAN IP | + | *Remote LAN IP |
The point of failure will provide critical insight into whatever issue you are facing. | The point of failure will provide critical insight into whatever issue you are facing. | ||