This is very alpha level.
For HND ARM Routers. RT-AC86U, RT-AX88U
https://drive.google.com/open?id=1wqDcJDUp8p3MRXlOFY8AKkeZR9ecEAMf
For SDK 7.14 ARM Routers. RT-AC3100, RT-AC88U, RT-AC5300
Download and unzip ipk file after that copy them to proper place.
ㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡ
CAPATH is self-signed ca certificate file name.
For example protonvpn.der, NordVPN.pem
This is provided by VPN provider.
https://protonvpn.com/support/linux-ikev2-protonvpn/
https://support.nordvpn.com/Connect...nect-to-NordVPN-with-IKEv2-IPSec-on-Linux.htm
Some providers use certificates signed by a known CA.
ID and Password are normally your account of VPN service.
This setting is expected to be compatible with most VPN providers.
nano /opt/etc/init.d/S90ikev2
Done.
ㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡ
For Policy Based Routing.
You can easily send the packets you want to the VPN using SNAT.
nano /opt/etc/ikev2/ikev2-updown.sh
Just change them like
And uncomment this line to ignore dns pushing of server.
nano /opt/etc/init.d/S90ikev2
For HND ARM Routers. RT-AC86U, RT-AX88U
https://drive.google.com/open?id=1wqDcJDUp8p3MRXlOFY8AKkeZR9ecEAMf
Code:
opkg install /path/ikev2client_alpha-2_aarch64-3.10.ipk
For SDK 7.14 ARM Routers. RT-AC3100, RT-AC88U, RT-AC5300
Download and unzip ipk file after that copy them to proper place.
ㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡ
CAPATH is self-signed ca certificate file name.
For example protonvpn.der, NordVPN.pem
This is provided by VPN provider.
https://protonvpn.com/support/linux-ikev2-protonvpn/
https://support.nordvpn.com/Connect...nect-to-NordVPN-with-IKEv2-IPSec-on-Linux.htm
Some providers use certificates signed by a known CA.
Code:
opkg install ca-certificates
export CAPATH=/opt/etc/ssl/certs
ID and Password are normally your account of VPN service.
This setting is expected to be compatible with most VPN providers.
nano /opt/etc/init.d/S90ikev2
Code:
export CAPATH=CA path for example) /jffs/protonvpn.der
export HOST=IP or DDNS for exmaple) us-01.protonvpn.com
export ID=YOUR ID
export PASSWORD=YOUR PASSWORD
Done.
Code:
/opt/etc/init.d/S90ikev2 start
ㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡ
For Policy Based Routing.
You can easily send the packets you want to the VPN using SNAT.
nano /opt/etc/ikev2/ikev2-updown.sh
Code:
up-client)
iptables -t nat -I POSTROUTING -o eth0 ! -p esp -j SNAT --to-source ${PLUTO_MY_SOURCEIP}
down-client)
iptables -t nat -D POSTROUTING -o eth0 ! -p esp -j SNAT --to-source ${PLUTO_MY_SOURCEIP} 2>/dev/null
Just change them like
Code:
up-client)
iptables -t nat -I POSTROUTING -s 192.168.50.100 -o eth0 ! -p esp -j SNAT --to-source ${PLUTO_MY_SOURCEIP}
down-client)
iptables -t nat -D POSTROUTING -s 192.168.50.100 -o eth0 ! -p esp -j SNAT --to-source ${PLUTO_MY_SOURCEIP} 2>/dev/null
And uncomment this line to ignore dns pushing of server.
nano /opt/etc/init.d/S90ikev2
Code:
#For Policy Based Routing
#sed -i "s|load = yes|load = no|g" /etc/strongswan.d/charon/resolve.conf
-> sed -i "s|load = yes|load = no|g" /etc/strongswan.d/charon/resolve.conf
Last edited: