The installation page currently says:
You can find the most current deb packages in my repository:
and points users to:
echo "deb https://repo.ddswd.de/deb stable main" | sudo tee /etc/apt/sources.list.d/vpncloud.list
wget https://repo.ddswd.de/deb/public.key -qO - | sudo apt-key add
sudo apt update
sudo apt install vpncloud
However, the repository at https://repo.ddswd.de/deb/ appears to provide only vpncloud version 2.2.0, while the latest GitHub release is 2.3.0.
This is relevant because v2.3.0 includes:
[fixed] Fixed problem with IPv4 addresses in listen option
I ran into a connection issue on 2.2.0 where IPv4 listen/peer addresses were internally shown as IPv4-mapped IPv6 addresses, e.g.:
Own addresses: [[::ffff:x.x.x.x]:3210]
Connecting to [::ffff:y.y.y.y]:3214
ERROR - Socker error: IOError when sending (Address family not supported by protocol (os error 97))
The system itself has IPv6 enabled, net.ipv6.bindv6only = 0, and outbound IPv6 works, so this looks like it may be related to the IPv4 listen handling fixed after 2.2.0.
After upgrading to 2.3.0 everything works fine.
Could the official Debian repository be updated to provide the latest release packages, or could the install page be adjusted to clarify that the GitHub release .deb files may be newer than the repository packages?
References:
The installation page currently says:
and points users to:
However, the repository at
https://repo.ddswd.de/deb/appears to provide onlyvpncloudversion2.2.0, while the latest GitHub release is2.3.0.This is relevant because
v2.3.0includes:I ran into a connection issue on
2.2.0where IPv4 listen/peer addresses were internally shown as IPv4-mapped IPv6 addresses, e.g.:The system itself has IPv6 enabled,
net.ipv6.bindv6only = 0, and outbound IPv6 works, so this looks like it may be related to the IPv4 listen handling fixed after2.2.0.After upgrading to 2.3.0 everything works fine.
Could the official Debian repository be updated to provide the latest release packages, or could the install page be adjusted to clarify that the GitHub release
.debfiles may be newer than the repository packages?References: