1 VPP as IKEv2 initiator and strongSwan as responder
2 ==================================================
7 To make the examples easier to configure ``docker`` it is required to pull strongSwan docker image. The networking is done using Linux' veth interfaces and namespaces.
15 192.168.3.2 192.168.5.2
18 +----+----+ 192.168.10.2 +-----+----+
20 |initiator+----------------------+responder |
21 +---------+ +----------+
25 Create veth interfaces and namespaces and configure them:
28 sudo ip link add gw type veth peer name swanif
29 sudo ip link set dev gw up
32 sudo ip link add veth_priv type veth peer name priv
33 sudo ip link set dev priv up
34 sudo ip link set dev veth_priv up netns ns
36 sudo ip netns exec ns \
39 ip addr add 192.168.3.2/24 dev veth_priv
40 ip route add 192.168.5.0/24 via 192.168.3.1"
44 Create directory with strongswan configs that will be mounted to the docker container
49 Create the ``ipsec.conf`` file in the ``/tmp/sswan`` directory with following content:
60 ike=aes256gcm16-prfsha256-modp2048!
65 leftid=@sswan.vpn.example.com
66 leftsubnet=192.168.5.0/24
69 rightid=@roadwarrior.vpp
72 rightsubnet=192.168.3.0/24
75 ``/tmp/sswan/ipsec.secrets``
80 ``/tmp/sswan/strongswan.conf``
85 include strongswan.d/charon/*.conf
89 time_format = %b %e %T
97 include strongswan.d/*.conf
100 Start docker container with strongSwan:
103 docker run --name sswan -d --privileged --rm --net=none \
104 -v /tmp/sswan:/conf -v /tmp/sswan:/etc/ipsec.d philplckthun/strongswan
107 Finish configuration of initiator's private network:
110 pid=$(docker inspect --format "{{.State.Pid}}" sswan)
111 sudo ip link set netns $pid dev swanif
113 sudo nsenter -t $pid -n ip addr add 192.168.10.1/24 dev swanif
114 sudo nsenter -t $pid -n ip link set dev swanif up
116 sudo nsenter -t $pid -n ip addr add 192.168.5.2/32 dev lo
117 sudo nsenter -t $pid -n ip link set dev lo up
123 sudo /usr/bin/vpp unix { \
124 cli-listen /tmp/vpp.sock \
126 api-segment { prefix vpp } \
127 plugins { plugin dpdk_plugin.so { disable } }
130 ... and configure it:
133 create host-interface name gw
134 set interface ip addr host-gw 192.168.10.2/24
135 set interface state host-gw up
137 create host-interface name priv
138 set interface ip addr host-priv 192.168.3.1/24
139 set interface state host-priv up
141 ikev2 profile add pr1
142 ikev2 profile set pr1 auth shared-key-mic string Vpp123
143 ikev2 profile set pr1 id local fqdn roadwarrior.vpp
144 ikev2 profile set pr1 id remote fqdn sswan.vpn.example.com
146 ikev2 profile set pr1 traffic-selector local ip-range 192.168.3.0 - 192.168.3.255 port-range 0 - 65535 protocol 0
147 ikev2 profile set pr1 traffic-selector remote ip-range 192.168.5.0 - 192.168.5.255 port-range 0 - 65535 protocol 0
149 ikev2 profile set pr1 responder host-gw 192.168.10.1
150 ikev2 profile set pr1 ike-crypto-alg aes-gcm-16 256 ike-dh modp-2048
151 ikev2 profile set pr1 esp-crypto-alg aes-gcm-16 256
153 create ipip tunnel src 192.168.10.2 dst 192.168.10.1
154 ikev2 profile set pr1 tunnel ipip0
155 ip route add 192.168.5.0/24 via 192.168.10.1 ipip0
156 set interface unnumbered ipip0 use host-gw
159 Initiate the IKEv2 connection:
162 vpp# ikev2 initiate sa-init pr1
166 vpp# show ikev2 sa details
167 iip 192.168.10.2 ispi f717b0cbd17e27c3 rip 192.168.10.1 rspi e9b7af7fc9b13361
168 encr:aes-gcm-16 prf:hmac-sha2-256 dh-group:modp-2048
169 nonce i:eb0354613b268c6372061bbdaab13deca37c8a625b1f65c073d25df2ecfe672e
170 r:70e1248ac09943047064f6a2135fa2a424778ba03038ab9c4c2af8aba179ed84
171 SK_d 96bd4feb59be2edf1930a12a3a5d22e30195ee9f56ea203c5fb6cba5dd2bb80f
172 SK_e i:00000000: 5b75b9d808c8467fd00a0923c06efee2a4eb1d033c57532e05f9316ed9c56fe9
174 r:00000000: 95121b63372d20b83558dc3e209b9affef042816cf071c86a53543677b40c15b
176 SK_p i:fb40d1114c347ddc3228ba004d4759d58f9c1ae6f1746833f908d39444ef92b1
177 r:aa049828240cb242e1d5aa625cd5914dc8f8e980a74de8e06883623d19384902
178 identifier (i) id-type fqdn data roadwarrior.vpp
179 identifier (r) id-type fqdn data sswan.vpn.example.com
180 child sa 0:encr:aes-gcm-16 esn:yes
181 spi(i) 9dffd57a spi(r) c4e0ef53
182 SK_e i:290c681694f130b33d511335dd257e78721635b7e8aa87930dd77bb1d6dd3f42
183 r:0a09fa18cf1cf65c6324df02b46dcc998b84e5397cf911b63e0c096053946c2e
184 traffic selectors (i):0 type 7 protocol_id 0 addr 192.168.3.0 - 192.168.3.255 port 0 - 65535
185 traffic selectors (r):0 type 7 protocol_id 0 addr 192.168.5.0 - 192.168.5.255 port 0 - 65535
188 Now we can generate some traffic between responder's and initiator's private networks and see it works.
191 $ sudo ip netns exec ns ping 192.168.5.2
192 PING 192.168.5.2 (192.168.5.2) 56(84) bytes of data.
193 64 bytes from 192.168.5.2: icmp_seq=1 ttl=63 time=0.450 ms
194 64 bytes from 192.168.5.2: icmp_seq=2 ttl=63 time=0.630 ms