[Solved] Bult-in OpenVPN server on IPv6 not working
[Solved] Bult-in OpenVPN server on IPv6 not working
I used to have a public IPv4 with the previous ISP and thanks to that (plus a DDNS service) I was able to use the built-in OpenVPN feature to connect to my home network anytime.
My new ISP gives me:
- an IPv4 address through PPoE (and it's behind a CGNAT so my public IP differs from my router IP)
- and a public IPv6 through Dynamic IP
The public IPv4 can no longer be used to access my home network since it's behind a CGNAT, but I now have a public IP on IPv6. How can I connect to the built-in OpeVPN server using the public IPv6 address?
I've tried to change the client configuration adding proto udp6 and the IPv6 address but it can't connect with the error Fri Jan 05 08:46:45 2024 write UDPv6: Unknown error (code=10051)
client
dev tun
proto udp6
float
nobind
cipher AES-128-CBC
comp-lzo adaptive
resolv-retry infinite
remote-cert-tls server
persist-key
persist-tun
remote 2A07:7E83:1000:XXXX:XXXX:XXXX:XXXX:XXXX
[....REDACTED KEY....]
Full log:
Fri Jan 05 08:46:38 2024 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set.
Fri Jan 05 08:46:38 2024 DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-128-CBC' to --data-ciphers or change --cipher 'AES-128-CBC' to --data-ciphers-fallback 'AES-128-CBC' to silence this warning.
Fri Jan 05 08:46:38 2024 OpenVPN 2.5.3 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Jun 17 2021
Fri Jan 05 08:46:38 2024 Windows version 10.0 (Windows 10 or greater) 64bit
Fri Jan 05 08:46:38 2024 library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10
Fri Jan 05 08:46:38 2024 TCP/UDP: Preserving recently used remote address: [AF_INET6]2a07:7e83:1000:XXXX:XXXX:XXXX:XXXX:XXXX
Fri Jan 05 08:46:38 2024 UDPv6 link local: (not bound)
Fri Jan 05 08:46:38 2024 UDPv6 link remote: [AF_INET6]2a07:7e83:1000:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX
Fri Jan 05 08:46:41 2024 write UDPv6: Unknown error (code=10051)
Fri Jan 05 08:46:45 2024 write UDPv6: Unknown error (code=10051)
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Sunshine, I have the same problem as the others, I am unable to use the IP v6 address to host an OpenVPN Server.
You mentioned that the competition does not have this feature, but all Asus Routers from the past 2 years have support for this, but they don't advertise it. If I configure a TCP OpenVPN server in the Asus router it will also listen on the IPv6 address.
This is a shame, since the tp link Er7212pc that I own can't be used for what I needed, so it now sits in the drawer.
- Copy Link
- Report Inappropriate Content
I am experiencing the same issue. Could you please escalate this to the development team once again? Increasingly, users require IPv6 support on VPN servers, whether OpenVPN or WireGuard. In consumer markets, IPv4 is becoming obsolete as ISPs now primarily provide residential users with public IPv6 addresses. Public IPv4 is largely reserved for business purposes. Therefore, having VPN servers configured for IPv6 should be an available option for consumer-grade routers.
Please share any updates on whether this feature is planned for future releases. If not, unfortunately, many users may be forced to seek alternative router options.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 2646
Replies: 12
Voters 1
