Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upIKEv2 VPN does not change to remote IP address on fedora based VMs #3568
Comments
Polygonbugs
changed the title from
IKEv2 VPN does not change remote IP address on fedora based VMs
to
IKEv2 VPN does not change to remote IP address on fedora based VMs
Feb 11, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Polygonbugs
Feb 11, 2018
Checked that debian-9 template is also not working properly liked as mentioned above.
Polygonbugs
commented
Feb 11, 2018
•
|
Checked that debian-9 template is also not working properly liked as mentioned above. |
andrewdavidwong
added
bug
C: Fedora
labels
Feb 11, 2018
andrewdavidwong
added this to the Release 3.2 updates milestone
Feb 11, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Polygonbugs
Mar 9, 2018
Same server OpenVPN works in PV mode machine. Could anybody test IKEv2 protocol on 4.0-rc5 which run PVH mode by default? I know that OpenVPN doesn't need kernel for this but IKEv2 dependent on it. See "https://openvpn.net/index.php/open-source/339-why-ssl-vpn.html"
Polygonbugs
commented
Mar 9, 2018
|
Same server OpenVPN works in PV mode machine. Could anybody test IKEv2 protocol on 4.0-rc5 which run PVH mode by default? I know that OpenVPN doesn't need kernel for this but IKEv2 dependent on it. See "https://openvpn.net/index.php/open-source/339-why-ssl-vpn.html" |
Polygonbugs commentedFeb 11, 2018
•
edited
Edited 3 times
-
Polygonbugs
edited Feb 11, 2018 (most recent)
-
Polygonbugs
edited Feb 11, 2018
-
Polygonbugs
edited Feb 11, 2018
Qubes OS version:
R3.2
Affected TemplateVMs:
fedora-26, fedora-26-minimal (PV domains)
Steps to reproduce the behavior:
Fedora VPN setup
sudo dnf install -y strongswan
cd /etc/strongswan
sudo gedit ipsec.conf
-add config for VPN server
sudo gedit ipsec.secrets
-add credential
sudo rm -rf ./ipsec.d/cacerts
sudo wget https://www.digicert.com/CACerts/DigiCertECCSecureServerCA.crt -O /etc/ssl/certs/DigiCertECCSecureServerCA.crt
sudo wget https://www.digicert.com/CACerts/DigiCertHighAssuranceEVRootCA.crt -O /etc/ssl/certs/DigiCertHighAssuranceEVRootCA.crt
sudo wget https://www.digicert.com/CACerts/DigiCertGlobalRootCA.crt -O /etc/ssl/certs/DigiCertGlobalRootCA.crt
sudo cp /etc/ssl/certs/* ./ipsec.d/cacerts
sudo strongswan restart
sudo strongswan up vpn
Expected behavior:
VPN is established successfully and Public IP is changed to remote server.
Actual behavior:
VPN is established successfully but Public IP is not changed.
General notes:
Same VPN server is established succesfully and get server IP on HVM linux such as Linux Mint. Does Qubes need additional IP routing to change? I use default route settings of strongswan.conf. Or additional package needed?