User Tools
vpn-server
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| vpn-server [2024/11/06 03:41] – [Routing Notes] -Condense hogwild | vpn-server [2025/11/19 20:32] (current) – [Problem: Traffic Flowing in only one Direction] hogwild | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| \\ | \\ | ||
| - | However, there are still differences between versions. For example, clients and servers may be configured on different versions. Encryption algorithms may be negotiated differently among versions. FreshTomato | + | However, there are still differences between versions. For example, clients and servers may be configured on different versions. Encryption algorithms may be negotiated differently among versions. FreshTomato |
| \\ | \\ | ||
| Line 351: | Line 351: | ||
| * AES-128-GCM | * AES-128-GCM | ||
| * AES-256-GCM | * AES-256-GCM | ||
| - | * AES-128-CB | + | * AES-128-CBC |
| * AES-256-CBC | * AES-256-CBC | ||
| Line 448: | Line 448: | ||
| Here, you can specify a custom configuration for the OpenVPN server to use. | Here, you can specify a custom configuration for the OpenVPN server to use. | ||
| - | For details about valid custom parameters, please see: \\ [[https:// | + | For details about valid custom parameters, please see: \\ [[https:// |
| Line 534: | Line 534: | ||
| A code commit was entered for Elliptical elliptic curve cryptography on 2024-10-19, and should be included in the next release. If your release doesn' | A code commit was entered for Elliptical elliptic curve cryptography on 2024-10-19, and should be included in the next release. If your release doesn' | ||
| - | Elliptic curve cryptography is also implemented in releases of OpenVPN | + | Elliptic curve cryptography is also implemented in OpenVPN |
| \\ | \\ | ||
| Line 633: | Line 633: | ||
| - | ==== Routing all Traffic | + | ==== Routing all Traffic |
| You can route all network traffic over the VPN. The configuration for this is fairly simple. However, you'll need to learn how to configure NAT on your VPN server for the virtual TUN adapter. | You can route all network traffic over the VPN. The configuration for this is fairly simple. However, you'll need to learn how to configure NAT on your VPN server for the virtual TUN adapter. | ||
| Line 666: | Line 666: | ||
| ==== About IPv6 ==== | ==== About IPv6 ==== | ||
| - | OpenVPN v2.3 and later support IPv6. Setting up IPv6 in a VPN is similar to the IPv4 examples | + | OpenVPN v2.3 and later support IPv6. Configuring |
| \\ | \\ | ||
| Line 682: | Line 682: | ||
| \\ | \\ | ||
| - | You can use the // | + | You can use the // |
| + | |||
| + | \\ | ||
| + | |||
| + | The syntax is similar: | ||
| \\ | \\ | ||
| Line 692: | Line 696: | ||
| \\ | \\ | ||
| - | \\ | + | ===== OpenVPN Server - Notes and Troubleshooting ===== |
| - | \\ | + | ==== 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' | ||
| + | \\ | ||
| + | \\ | ||
| + | | ||
| + | | ||
vpn-server.1730864515.txt.gz · Last modified: by hogwild
Page Tools
