Details
This change introduces a new automated test for StrongSwan PSK
connectivity.
site_linux_server.py is modified to do the following:
vpn_strongswan_config_templates()
Takes a list of configuration file names, and their contents.
The contents can have text that is replaced at write-out time
with runtime information, such as the current server IP number.
vpn_server_config()
Now suports the 'l2tpipsec' type of VPN connection.
It is the responsibility of the person writing the test to make
sure the contents of the provided configuration templates are
correct, and self-consistent.
vpn_server_kill()
If the current type of VPN is 'l2tpipsec', then all programs
known to be associated with that system are killed.
site_wifitest.py is modified thusly:
Two types of l2tpipsec configurations are supported
lt2pipsec-psk
lt2pipsec-cert
The former uses PSK, and the latter uses certificates. This
separation was done to simplify the use of 'connect-vpn' (see
review 6756032) as well as the starting of the VPN itself.
Testing
Starting StrongSwan causes the default route on the system to go
through the VPN (which causes active connections to go dead),
automated testing is incomplete at this point.
Initiating the VPN using 'connect-vpn l2tpipsec-psk' functions
correctly.
Initiating the VPN using 'connect-vpn l2tpipsec-cert' has not yet
been tested; I do not have configuration files for certificate mode.
See issue 6756032.
BUG=chromium-os:11824
Testing=See above
Review URL: http://codereview.chromium.org/6765030
Change-Id: I046e0084f9f59ea4fcdc1cccc6e6d30fee79b0f3
5 files changed
