Add split tunnel interface to vpnProvider

extensions/common/api/vpn_provider.idl

Index: extensions/common/api/vpn_provider.idl
diff --git a/extensions/common/api/vpn_provider.idl b/extensions/common/api/vpn_provider.idl
index 867484e576e42103a7fa064f8c923f2e5fc78af4..b909c03c2d514b8d656a4bef75dc0fb5743a3e3e 100644
--- a/extensions/common/api/vpn_provider.idl
+++ b/extensions/common/api/vpn_provider.idl
@@ -15,10 +15,13 @@ namespace vpnProvider {
     DOMString? broadcastAddress;
     // MTU setting for the VPN interface. (default: 1500 bytes)
     DOMString? mtu;
-    // Bypass network traffic to the below IPs from the tunnel. Typically used
-    // to bypass traffic to and from the VPN server. Currently only one IP is
-    // supported.
-    DOMString[] bypassTunnelForIp;
+    // Exclude network traffic to the below IP blocks in CIDR notation from the
+    // tunnel. This can be used to bypass traffic to and from the VPN server.
+    DOMString[] exclusionList;
+    // Include network traffic to the below IP blocks in CIDR notation to the
+    // tunnel. By default all user traffic is routed to the tunnel. This
+    // parameter can be used to setup split tunnel.

[not at google - send to devlin, 2015/02/18 19:14:04]

Which takes precedence?

[kaliamoorthi, 2015/02/19 12:53:59]

I responded to this question in the comment. Its the most specific one with the
longest matching prefix.

+    DOMString[] inclusionList;
     // A list of search domains. (default: no search domain)
     DOMString[]? domainSearch;
     // A list of IPs for the DNS servers.