Add automated StrongSwan test

server/site_tests/network_VPN/050StrongSwanGenesis

Index: server/site_tests/network_VPN/050StrongSwanGenesis
diff --git a/server/site_tests/network_VPN/050StrongSwanGenesis b/server/site_tests/network_VPN/050StrongSwanGenesis
new file mode 100644
index 0000000000000000000000000000000000000000..591f85316accc92f54cb99e6a15def846a026a60
--- /dev/null
+++ b/server/site_tests/network_VPN/050StrongSwanGenesis
@@ -0,0 +1,47 @@
+# Copyright (c) 2011 The Chromium OS Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+#
+# An example of how to set up a StrongSwan VPN from the Client (DUT),

[kmixter1, 2011/04/07 07:07:23]

Strongswan does IPsec.  OpenS/WAN, FreeS/WAN, Racoon and some other packages all
can do IPsec and are alternatives (Android uses Racoon).  We may some day want
to change to one of them or another.  So that's one reason not to use strongswan
in file names and comments.  Another is that IPsec itself can be set up in
tunnel mode, in which it alone is a VPN.  We may end up supporting that kind of
VPN (IKEv2 tunnel mode is becoming a more popular VPN alternative these days). 
In either of those cases, naming these files "strongswan" as an equivalence with
L2TP/IPsec will be confusing.

+# through the Router to to the Server.
+#
+
+{ "name" : "VPNStrongSwanGenesis",
+  "steps":[
+    #  Create WiFi connection from Client to Router.
+    [ "create",         { "type" : "hostap" } ],
+    [ "config",         { "channel" : "2412", "mode" : "11b" } ],
+    [ "connect",        { "security" : "none" } ],
+
+    # The text '@ipsecrets-ip@' is automtically replaced with the
+    # correct server IP for the current test configuration, and should
+    # not be replaced through this list of steps; in fact, any
+    # replacements will be automatically overridden.
+    #
+    # The text '@local-listen-ip@' is also replaced with the IP number
+    # of the interface connected to the WiFi router.  The default is
+    # 'wifi_addr' (192.168.2.254), and it should not be replaced this
+    # list of steps; in fact, any replacements will be automatically
+    # overridden.  Configure and launch the VPN server.  Automatically
+    # kills any previously running server.
+    #
+    [ "vpn_server_config", {
+                "kind" : "l2tpipsec",
+                "replacements" : { "@plutodebug@" : "all" }}],
+
+    #  Launch the VPN Client.
+    [ "vpn_client_config", { "kind"       : "l2tpipsec-psk",
+                             "password"   : "password",  # ipsec.secrets
+                             "chapuser"   : "chapuser",  # chap-secrets
+                             "chapsecret" : "chapsecret" # chap-secrets
+                           }],
+
+    # Verify the client is connected to the server
+    [ "client_ping",       { "ping_ip" : "192.168.1.99", # IP in xl2tpd.conf.
+                             "count" : "10" } ],
+
+    [ "vpn_client_kill" ],       # Shut down the VPN Client.
+    [ "vpn_server_kill" ],       # Shut down the VPN Server.
+    [ "disconnect" ],            # Disconnect WiFi setup
+    ],
+}