Download StrongSwan
Author: c | 2025-04-25
First download StrongSwan source code from official site. Extract source code tarball to directory strongswan/ Configure strongswan autoconf to compile plugin. vim strongswan/configure.ac. strongswan.org Downloads GitHub. strongSwan Docs. What’s New in strongSwan 6.0; Introduction to strongSwan; Introduction to IPsec; Installation. Installation Documentation;
strongswan/strongswan: strongSwan - IPsec-based
Why can't I install strongSwan VPN Client?The installation of strongSwan VPN Client may fail because of the lack of device storage, poor network connection, or the compatibility of your Android device. Therefore, please check the minimum requirements first to make sure strongSwan VPN Client is compatible with your phone.How to check if strongSwan VPN Client is safe to download?strongSwan VPN Client is safe to download on APKPure, as it has a trusted and verified digital signature from its developer.How to download strongSwan VPN Client old versions?APKPure provides the latest version and all the older versions of strongSwan VPN Client. You can download any version you want from here: All Versions of strongSwan VPN ClientWhat's the file size of strongSwan VPN Client?strongSwan VPN Client takes up around 8.3 MB of storage. It's recommended to download APKPure App to install strongSwan VPN Client successfully on your mobile device with faster speed.What language does strongSwan VPN Client support?strongSwan VPN Client supports isiZulu,中文,Việt Nam, and more languages. Go to More Info to know all the languages strongSwan VPN Client supports.
strongswan/strongswan: strongSwan - IPsec-based VPN - GitHub
In a previous tutorial, we configured an IPsec tunnel between a Cisco 1812 router and TheGreenBow IPsec VPN client installed on Windows OS. TheGreenBow is an excellent product; however, the free version is only valid for 30 days. Once the trial period expires, you must purchase a license to continue using it. Therefore, we will focus on configuring a free IPsec VPN client solution such as StrongSwan on Linux Debian.The IPsec protocol for a VPN is configured using the Internet Key Exchange (IKE) protocol. The terms IPsec and IKE are used interchangeably. An IPsec VPN is also called an IKE VPN, IKEv2 VPN, XAUTH VPN, Cisco VPN or IKE/IPsec VPN.StrongSwan is an open-source, user-space IKE implementation. IKE v1 and v2 are implemented as a user-level daemon. The IKE protocol is also encrypted. The IPsec protocol is implemented by the Linux kernel, and OpenSwan configures the kernel to add and remove VPN tunnel configurations.The network topology is depicted in Figure 1. The StrongSwan client is the initiator, and the responder is the Cisco 1812. However, OpenSwan does not use the terms "source" and "destination" or "server" and "client" because IKE/IPsec are peer-to-peer protocols. Instead, it uses the terms "left" and "right" to refer to the endpoints (the hosts). This also allows you to use the same configuration on both endpoints in most cases. However, administrators usually choose to always use "left" for the local host and "right" for the remote host. [1].Left :- strongSwan 5.9.1 installed on Debian bullseye 11Right:- Cisco 1812 IOS Version 15.1(4)M12aFigure 1 - Network Topology1. IPSec "Right" Configuration - Cisco 1812The initial IPsec tunnel configuration on the Cisco 1812 (left side) is found in R1-config.txt. The Cisco router has assigned a dynamic public IP address (95.103.161.130), which is translated to 'a102.mywire.org'. However, this dynamic IP can change after each router restart. For this reason, we rely on the domain name instead of the IP address in strongSwan configuration. Therefore, the "right" parameter configured in ipsec.conf is the domain name a102.mywire.org and not the IP address 95.103.161.130.By default, Cisco uses the IP address of the interface for the identity in the IKE phase. The right side (StrongSwan) receives the IDir '95.103.161.130' from the Cisco router, but it does not match the hostname 'a102.mywire.org'. As a result, Phase 1 is not successful, and the IPsec tunnel is not established, as shown in Figure 2.Figure 2 - Local and Remote ID Mismatch types in IKEV1For this reason, we need to ensure that the hostname is set to 'a102' and the domain name is set to 'mywire.org' in Cisco configuration.a102(config)# hostname a102a102(config)# ip domain name mywire.orgFurthermore, we need to configure router to use hostname to identify itself in the Phase 1:a102(config)# crypto isakmp identity hostnameThe complete Cisco IPsec "right side" configuration with omitted credentials is R1-final-ipsec.txt.2. strongSwan InstallationTo install strongSwan and the necessary plugins, run:$ sudo apt install strongswan libcharon-extra-pluginsThen, enable the strongSwan service and start it using the following commands:$ sudo systemctl enable strongswan-starter && sudo systemctl start strongswan-starter3. IPSecGitHub - strongswan/strongswan: strongSwan - IPsec-based VPN
I need to set up a connection to VPN server with Libreswan. I can't use strongswan, since they are not working well together when installed on the same OC.My system is Linux Debian 10 (Buster)Kernel version: 4.19.0-17I already have a working L2TP/IPSec VPN connection, so dont want to install additional software.When I scan remote VPN with ike-scan, server responses with next:Handshake returned:HDR=(CKY-R=574aa700c8ed7aa6, IKEv2)SA=(Encr=AES_CBC,KeyLength=128 Integ=HMAC_SHA1_96 Prf=HMAC_SHA1 DH_Group=2:modp1024)KeyExchange(132 bytes) Nonce(32 bytes) Notification(4 bytes)This looks like libreswan can support the connection.When I try to start new connection I added into ipsec.conf, I got next:002 "ikev2-srv" #1: constructed local IKE proposals for ikev2-srv (IKE SA initiator selecting KE): 1:IKE:ENCR=AES_GCM_C_256;PRF=HMAC_SHA2_512,HMAC_SHA2_256,HMAC_SHA1;INTEG=NONE;DH=MODP2048,MODP3072,MODP4096,MODP8192,ECP_256 2:IKE:ENCR=AES_GCM_C_128;PRF=HMAC_SHA2_512,HMAC_SHA2_256,HMAC_SHA1;INTEG=NONE;DH=MODP2048,MODP3072,MODP4096,MODP8192,ECP_256 3:IKE:ENCR=AES_CBC_256;PRF=HMAC_SHA2_512,HMAC_SHA2_256,HMAC_SHA1;INTEG=HMAC_SHA2_512_256,HMAC_SHA2_256_128,HMAC_SHA1_96;DH=MODP2048,MODP3072,MODP4096,MODP8192,ECP_256 4:IKE:ENCR=AES_CBC_128;PRF=HMAC_SHA2_512,HMAC_SHA2_256,HMAC_SHA1;INTEG=HMAC_SHA2_512_256,HMAC_SHA2_256_128,HMAC_SHA1_96;DH=MODP2048,MODP3072,MODP4096,MODP8192,ECP_256 (default)133 "ikev2-srv" #1: STATE_PARENT_I1: sent v2I1, expected v2R1002 "ikev2-srv" #1: WARNING: connection ikev2-srv PSK length of 8 bytes is too short for sha PRF in FIPS mode (10 bytes required)Question is: how to configure mentioned Ikev2 vpn connection with libreswan?I got login / pass and server ip and nothing more. Also , my pass is smaller than it is expected(according to output).. First download StrongSwan source code from official site. Extract source code tarball to directory strongswan/ Configure strongswan autoconf to compile plugin. vim strongswan/configure.ac.strongSwan - strongSwan 5.9.6 Released
Route-based VPN or overlay network solutions (with virtual interfaces)If you run ifconfig -a or ip link show you should be seeing something like tunX below which is a tun device used by most route-based VPN:# tun device# used by route-based VPN tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr: P-t-P: Mask: UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1300 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:1435 (1.4 KB) TX bytes:1677 (1.6 KB)# Jan 2020 refresh# sample ifconfig output with 3 virtual interfaces# for route-based VPN or overlay networknebula1: flags=4305 mtu 1300 inet 172.16.87.100 netmask 255.255.255.0 destination 172.16.87.100 inet6 fe80::b2c4:4360:a3ae:15aa prefixlen 64 scopeid 0x20 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC) RX packets 37 bytes 2980 (2.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 331 bytes 17408 (17.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0tun0: flags=4305 mtu 1500 inet 172.16.200.1 netmask 255.255.255.0 destination 172.16.200.1 inet6 fe80::9d2e:5979:5ac2:43df prefixlen 64 scopeid 0x20 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1677 bytes 80496 (80.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0wg0: flags=209 mtu 1420 inet 172.16.111.100 netmask 255.255.255.0 destination 172.16.111.100 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 37337578 bytes 10884991930 (10.8 GB) RX errors 0 dropped 67878 overruns 0 frame 0 TX packets 60202096 bytes 66040772964 (66.0 GB) TX errors 169 dropped 44429 overruns 0 carrier 0 collisions 0ip link output5: wg0: mtu 1420 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/none6: tun0: mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 100 link/none11: nebula1: mtu 1300 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500 link/nonePolicy-based VPN (e.g. strongSwan)Or if you are using IPsec (e.g. strongSwan), ifconfig -a will show a tunnel device (tunX) like below if you are using Route-based mode (default is policy-based):tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:192.168.11.2 P-t-P:192.168.11.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)If strongSwan is running policy-based routing (default), you'll be able to figure out by manipulating the kernel routing table or looking at ip-xfrm IP framework for transforming packets (encrypting payloads).# manipulate kernel routing table for more infoip rroute -nrip r show table mainip r show table local# strongswan specific table id 220ip r show table 220In addition, you can use ip tuntap show to see if there are tun/tap devices to determine if VPN is in use. ip tuntap show tun0: tunstrongSwan - strongSwan 6.0.0 Released
'cisco1812' established successfully4.2 Checking IPsec StatusTo check status of IPsec tunnel on left side (StrongSwan), enter the command below. The command provides a summary of the current IPsec Security Associations (SAs). It shows the established connections, their status, and the involved endpoints and traffic selectors.root@debian11:/home/debian# ipsec statusSecurity Associations (1 up, 0 connecting):cisco1812[6]: ESTABLISHED 3 minutes ago, 192.168.42.1[192.168.42.1]...95.103.161.130[a102.mywire.org]cisco1812{2}: INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c3fd7731_i 9af8961d_ocisco1812{2}: 192.168.42.1/32 === 192.168.88.0/244.3 Checking IPsec All ParametersThe command 'ipsec statusall' provides more detailed information about the IKE daemon (charon) and all active IPsec connections. It includes uptime, memory usage, loaded plugins, listening IP addresses, connection details etc.root@debian11:/home/debian# ipsec statusallStatus of IKE charon daemon (strongSwan 5.9.1, Linux 5.10.0-29-amd64, x86_64):uptime: 2 hours, since May 24 23:51:51 2024malloc: sbrk 2969600, mmap 0, used 916048, free 2053552worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0, scheduled: 5loaded plugins: charon aesni aes rc2 sha2 sha1 md5 mgf1 random nonce x509 revocation constraints pubkey pkcs1 pkcs7 pkcs8 pkcs12 pgp dnskey sshkey pem openssl fips-prf gmp agent xcbc hmac gcm drbg attr kernel-netlink resolve socket-default connmark farp stroke updown eap-identity eap-aka eap-md5 eap-gtc eap-mschapv2 eap-radius eap-tls eap-ttls eap-tnc xauth-generic xauth-eap xauth-pam tnc-tnccs dhcp lookip error-notify certexpire led addrblock unity countersListening IP addresses:192.168.42.1Connections:cisco1812: 192.168.42.1...a102.mywire.org IKEv1 Aggressivecisco1812: local: [192.168.42.1] uses pre-shared key authenticationcisco1812: local: [192.168.42.1] uses XAuth authentication: any with XAuth identity 'vpnuser1'cisco1812: remote: [a102.mywire.org] uses pre-shared key authenticationcisco1812: child: dynamic === 192.168.88.0/24 TUNNELSecurity Associations (1 up, 0 connecting):cisco1812[6]: ESTABLISHED 4 minutes ago, 192.168.42.1[192.168.42.1]...95.103.161.130[a102.mywire.org]cisco1812[6]: IKEv1 SPIs: 4cdd54bce6e4e709_i* fabbae546b66b0d3_r, pre-shared key+XAuth reauthentication in 23 hourscisco1812[6]: IKE proposal: AES_CBC_256/HMAC_SHA2_512_256/PRF_HMAC_SHA2_512/MODP_1536cisco1812{2}: INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c3fd7731_i 9af8961d_ocisco1812{2}: AES_CBC_256/HMAC_SHA2_512_256, 0 bytes_i, 0 bytes_o, rekeying in 50 minutescisco1812{2}: 192.168.42.1/32 === 192.168.88.0/244.4 Bringing Down IPsec TunnelTo close the IPsec tunnel enter the command below. The command closes the specified IPsec connection, terminating the IPSec Security Associations (SAs) and the IKE_SA. It sends the necessary DELETE messages to the remote peer to properly close the connection.root@debian11:/home/debian# ipsec down cisco1812closing CHILD_SA cisco1812{2} with SPIs c3fd7731_i (0 bytes) 9af8961d_o (0 bytes) and TS 192.168.42.1/32 === 192.168.88.0/24sending DELETE for ESP CHILD_SA with SPI c3fd7731generating INFORMATIONAL_V1 request 1442320517 [ HASH D ]sending packet: from 192.168.42.1[4500] to 95.103.161.130[4500] (124 bytes)deleting IKE_SA cisco1812[6] between 192.168.42.1[192.168.42.1]...95.103.161.130[a102.mywire.org]sending DELETE for IKE_SA cisco1812[6]generating INFORMATIONAL_V1 request 3190336075 [ HASH D ]sending packet: from 192.168.42.1[4500] to 95.103.161.130[4500] (140 bytes)IKE_SA [6] closed successfullyConclusionIn this tutorial, we set up an IPsec tunnel between a Cisco 1812 router and a Linux Debian system running StrongSwan. This choice was prompted by the trial limitations of TheGreenBow IPsec VPN client. We configured both sides of the tunnel, addressing issues like identity mismatch. After establishing the tunnel, we verified its status and learned how to terminate it gracefully. This tutorial equips us to deploy and manage IPsec VPN connections using StrongSwan on Linux Debian.strongSwan - strongSwan 5.9.8 Released
3.40 43 reviews 10,000+ Downloads Free Connects your device to Securepoint Unified Security using VPN About Securepoint VPN Client Securepoint VPN Client is a business app developedby Securepoint GmbH. The APK has been available since October 2018. In the last 30 days, the app was downloaded about 230 times. It's currently not in the top ranks. It's rated 3.40 out of 5 stars, based on 43 ratings. The last update of the app was on January 13, 2025. Securepoint VPN Client has a content rating "Everyone". Securepoint VPN Client has an APK download size of 19.81 MB and the latest version available is 3.1.0. Designed for Android version 6.0+. Securepoint VPN Client is FREE to download. Description Securepoint VPN Client is an SSL-VPN client developed by Securepoint GmbH. The following features are offered:* Easy remote configuration by Securepoint Unified Security* Easily import VPN configurations from the device's file system to connect to your VPN server* Full IPv6 support* Consciously lean implementation* This app uses the modern VPNService APIRecent changes:Feature: Authentication before app startFeature: UI modificationsFeature: Renaming the connection logsFix: Error fixed where an invalid IPv6 address can lead to a crashFix: Error fixed where unsaved changes in the profile editor were not recorded correctlyFix: Error fixed where simultaneous profile update and navigation change can lead to a crashFix: Sending function and widget have been fixed for shared work profiles">Show more More data about Securepoint VPN Client Price Free to download Total downloads 15 thousand Recent downloads 230 Rating 3.40 based on 43 ratings Ranking Not ranked Version 3.1.0 APK size 19.8 MB Number of libraries 12 Designed for Android 6.0+ Suitable for Everyone Ads NO ads Alternatives for the Securepoint VPN Client app Securepoint VPN Client compared with similar apps Keywords that only this app has Securepoint Fixed Feature Error Device Unified Lead Crash Profile Common keywords of similar apps Vpn Fix Security Client App Keywords missing from this app Secure Fast Connection Online Vpnservice Server Access Service Privacy Internet Servers Data Connect Easy Users Private Provide Recent User Smart Safe Speed Interface Core Functionality Required Application Browsing Experience Unlimited Strongswan Tunnel Enjoy Websites Streaming Bugs Support Authentication Simple Trend Proxy Features Google Play Rating history and histogram Downloads over time Securepoint VPN Client has been downloaded 15 thousand times. Over the past 30 days, it has been downloaded 230 times. Changelog Developer information for Securepoint GmbH Are you the. First download StrongSwan source code from official site. Extract source code tarball to directory strongswan/ Configure strongswan autoconf to compile plugin. vim strongswan/configure.ac. strongswan.org Downloads GitHub. strongSwan Docs. What’s New in strongSwan 6.0; Introduction to strongSwan; Introduction to IPsec; Installation. Installation Documentation;Comments
Why can't I install strongSwan VPN Client?The installation of strongSwan VPN Client may fail because of the lack of device storage, poor network connection, or the compatibility of your Android device. Therefore, please check the minimum requirements first to make sure strongSwan VPN Client is compatible with your phone.How to check if strongSwan VPN Client is safe to download?strongSwan VPN Client is safe to download on APKPure, as it has a trusted and verified digital signature from its developer.How to download strongSwan VPN Client old versions?APKPure provides the latest version and all the older versions of strongSwan VPN Client. You can download any version you want from here: All Versions of strongSwan VPN ClientWhat's the file size of strongSwan VPN Client?strongSwan VPN Client takes up around 8.3 MB of storage. It's recommended to download APKPure App to install strongSwan VPN Client successfully on your mobile device with faster speed.What language does strongSwan VPN Client support?strongSwan VPN Client supports isiZulu,中文,Việt Nam, and more languages. Go to More Info to know all the languages strongSwan VPN Client supports.
2025-04-04In a previous tutorial, we configured an IPsec tunnel between a Cisco 1812 router and TheGreenBow IPsec VPN client installed on Windows OS. TheGreenBow is an excellent product; however, the free version is only valid for 30 days. Once the trial period expires, you must purchase a license to continue using it. Therefore, we will focus on configuring a free IPsec VPN client solution such as StrongSwan on Linux Debian.The IPsec protocol for a VPN is configured using the Internet Key Exchange (IKE) protocol. The terms IPsec and IKE are used interchangeably. An IPsec VPN is also called an IKE VPN, IKEv2 VPN, XAUTH VPN, Cisco VPN or IKE/IPsec VPN.StrongSwan is an open-source, user-space IKE implementation. IKE v1 and v2 are implemented as a user-level daemon. The IKE protocol is also encrypted. The IPsec protocol is implemented by the Linux kernel, and OpenSwan configures the kernel to add and remove VPN tunnel configurations.The network topology is depicted in Figure 1. The StrongSwan client is the initiator, and the responder is the Cisco 1812. However, OpenSwan does not use the terms "source" and "destination" or "server" and "client" because IKE/IPsec are peer-to-peer protocols. Instead, it uses the terms "left" and "right" to refer to the endpoints (the hosts). This also allows you to use the same configuration on both endpoints in most cases. However, administrators usually choose to always use "left" for the local host and "right" for the remote host. [1].Left :- strongSwan 5.9.1 installed on Debian bullseye 11Right:- Cisco 1812 IOS Version 15.1(4)M12aFigure 1 - Network Topology1. IPSec "Right" Configuration - Cisco 1812The initial IPsec tunnel configuration on the Cisco 1812 (left side) is found in R1-config.txt. The Cisco router has assigned a dynamic public IP address (95.103.161.130), which is translated to 'a102.mywire.org'. However, this dynamic IP can change after each router restart. For this reason, we rely on the domain name instead of the IP address in strongSwan configuration. Therefore, the "right" parameter configured in ipsec.conf is the domain name a102.mywire.org and not the IP address 95.103.161.130.By default, Cisco uses the IP address of the interface for the identity in the IKE phase. The right side (StrongSwan) receives the IDir '95.103.161.130' from the Cisco router, but it does not match the hostname 'a102.mywire.org'. As a result, Phase 1 is not successful, and the IPsec tunnel is not established, as shown in Figure 2.Figure 2 - Local and Remote ID Mismatch types in IKEV1For this reason, we need to ensure that the hostname is set to 'a102' and the domain name is set to 'mywire.org' in Cisco configuration.a102(config)# hostname a102a102(config)# ip domain name mywire.orgFurthermore, we need to configure router to use hostname to identify itself in the Phase 1:a102(config)# crypto isakmp identity hostnameThe complete Cisco IPsec "right side" configuration with omitted credentials is R1-final-ipsec.txt.2. strongSwan InstallationTo install strongSwan and the necessary plugins, run:$ sudo apt install strongswan libcharon-extra-pluginsThen, enable the strongSwan service and start it using the following commands:$ sudo systemctl enable strongswan-starter && sudo systemctl start strongswan-starter3. IPSec
2025-04-04Route-based VPN or overlay network solutions (with virtual interfaces)If you run ifconfig -a or ip link show you should be seeing something like tunX below which is a tun device used by most route-based VPN:# tun device# used by route-based VPN tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr: P-t-P: Mask: UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1300 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:1435 (1.4 KB) TX bytes:1677 (1.6 KB)# Jan 2020 refresh# sample ifconfig output with 3 virtual interfaces# for route-based VPN or overlay networknebula1: flags=4305 mtu 1300 inet 172.16.87.100 netmask 255.255.255.0 destination 172.16.87.100 inet6 fe80::b2c4:4360:a3ae:15aa prefixlen 64 scopeid 0x20 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC) RX packets 37 bytes 2980 (2.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 331 bytes 17408 (17.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0tun0: flags=4305 mtu 1500 inet 172.16.200.1 netmask 255.255.255.0 destination 172.16.200.1 inet6 fe80::9d2e:5979:5ac2:43df prefixlen 64 scopeid 0x20 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1677 bytes 80496 (80.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0wg0: flags=209 mtu 1420 inet 172.16.111.100 netmask 255.255.255.0 destination 172.16.111.100 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 37337578 bytes 10884991930 (10.8 GB) RX errors 0 dropped 67878 overruns 0 frame 0 TX packets 60202096 bytes 66040772964 (66.0 GB) TX errors 169 dropped 44429 overruns 0 carrier 0 collisions 0ip link output5: wg0: mtu 1420 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/none6: tun0: mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 100 link/none11: nebula1: mtu 1300 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500 link/nonePolicy-based VPN (e.g. strongSwan)Or if you are using IPsec (e.g. strongSwan), ifconfig -a will show a tunnel device (tunX) like below if you are using Route-based mode (default is policy-based):tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:192.168.11.2 P-t-P:192.168.11.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)If strongSwan is running policy-based routing (default), you'll be able to figure out by manipulating the kernel routing table or looking at ip-xfrm IP framework for transforming packets (encrypting payloads).# manipulate kernel routing table for more infoip rroute -nrip r show table mainip r show table local# strongswan specific table id 220ip r show table 220In addition, you can use ip tuntap show to see if there are tun/tap devices to determine if VPN is in use. ip tuntap show tun0: tun
2025-04-16