<p>You can access to the latest <ahref="https://github.com/SoftEtherVPN/SoftEtherVPN/tree/master/developer_tools/vpnserver-jsonrpc-clients/">SoftEther VPN Server JSON-RPC Document on GitHub</a>.</p>
<h2id="what-is-softether-vpn-server-json-rpc-api-suite">What is SoftEther VPN Server JSON-RPC API Suite?</h2>
<p>The API Suite allows you to easily develop your original SoftEther VPN Server management application to control the VPN Server (e.g. creating users, adding Virtual Hubs, disconnecting a specified VPN sessions).</p>
<ul>
<li>Almost all control APIs, which the VPN Server provides, are available as JSON-RPC API.</li>
<li>You can write your own VPN Server management application in your favorite languages (JavaScript, TypeScript, Java, Python, Ruby, C#, ... etc.)</li>
<li>If you are planning to develop your own VPN cloud service, the JSON-RPC API is the best choice to realize the automated operations for the VPN Server.</li>
<li>No need to use any specific API client library since all APIs are provided on the <ahref="https://www.jsonrpc.org/specification">JSON-RPC 2.0 Specification</a>. You can use your favorite JSON and HTTPS client library to call any of all APIs in your pure runtime environment.</li>
<li>Also, the SoftEther VPN Project provides high-quality JSON-RPC client stub libraries which define all of the API client stub codes. These libraries are written in C#, JavaScript and TypeScript. <ahref="https://www.npmjs.com/package/vpnrpc">The Node.js Client Library for VPN Server RPC (vpnrpc)</a> package is also available.</li>
<li>Older versions of SoftEther VPN before June 2019 don't support JSON-RPC APIs.</li>
<li>If you want to completely disable the JSON-RPC on your VPN Server, set the <code>DisableJsonRpcWebApi</code> variable to <code>true</code> on the <code>vpn_server.config</code>.</li>
<h3id="vpnrpc-node.js-client-library-package-for-vpn-server-json-rpc">"vpnrpc": Node.js Client Library package for VPN Server JSON-RPC</h3>
<p>If you are willing to develop your original JSON-RPC client for SoftEther VPN, you can use the <ahref="https://www.npmjs.com/package/vpnrpc">JavaScript Client Library for VPN Server RPC (vpnrpc)</a>.</p>
<ul>
<li>You can use the <code>vpnrpc</code> library in JavaScript for both web browsers (e.g. Chrome, FireFox or Edge) and Node.js.</li>
<li>As a sample code there is the <ahref="https://github.com/SoftEtherVPN/SoftEtherVPN/tree/master/developer_tools/vpnserver-jsonrpc-clients/vpnserver-jsonrpc-client-typescript/sample.ts">sample.ts</a> program in TypeScript. This sample calls all of available JSON-RPC APIs against the specified SoftEther VPN Server. (Note: This sample code is written in TypeScript.)</li>
</ul>
<p>You can use the following command to download the <code>vpnrpc</code> library package with Node.js.</p>
<pre><code>$ npm install --save-dev vpnrpc
</code></pre>
<h3id="vpnrpc.ts-typescript-client-library-for-vpn-server-json-rpc">"vpnrpc.ts": TypeScript Client Library for VPN Server JSON-RPC</h3>
<p>If you are willing to develop your original JSON-RPC client for SoftEther VPN, you can use the <ahref="https://github.com/SoftEtherVPN/SoftEtherVPN/tree/master/developer_tools/vpnserver-jsonrpc-clients/vpnserver-jsonrpc-client-typescript/">TypeScript Client Library for VPN Server RPC (vpnrpc.ts)</a>.</p>
<ul>
<li>You can use the <ahref="https://github.com/SoftEtherVPN/SoftEtherVPN/tree/master/developer_tools/vpnserver-jsonrpc-clients/vpnserver-jsonrpc-client-typescript/vpnrpc.ts">vpnrpc.ts</a> library in TypeScript / JavaScript for both web browsers (e.g. Chrome, FireFox or Edge) and Node.js.</li>
<li>As a sample code there is the <ahref="https://github.com/SoftEtherVPN/SoftEtherVPN/tree/master/developer_tools/vpnserver-jsonrpc-clients/vpnserver-jsonrpc-client-typescript/sample.ts">sample.ts</a> program in TypeScript. This sample calls one by one all of available JSON-RPC APIs against the specified SoftEther VPN Server.</li>
</ul>
<h3id="vpnserver-jsonrpc-client-csharp-c-client-library-for-vpn-server-json-rpc">"vpnserver-jsonrpc-client-csharp": C# Client Library for VPN Server JSON-RPC</h3>
<p>If you are willing to develop your original JSON-RPC client for SoftEther VPN, you can use the <ahref="https://github.com/SoftEtherVPN/SoftEtherVPN/tree/master/developer_tools/vpnserver-jsonrpc-clients/vpnserver-jsonrpc-client-csharp/">vpnserver-jsonrpc-client-csharp C# library</a>.</p>
<li>The <ahref="https://github.com/SoftEtherVPN/SoftEtherVPN/tree/master/developer_tools/vpnserver-jsonrpc-clients/vpnserver-jsonrpc-client-csharp/rpc-stubs/">client library codes for C#</a> is written in pure C# 7.3. It works on .NET Core 2.1 or later on Windows, Linux and macOS. Very comfort with Visual Studio for both Windows or macOS.</li>
<li>As a sample code there is the <ahref="https://github.com/SoftEtherVPN/SoftEtherVPN/blob/master/developer_tools/vpnserver-jsonrpc-clients/vpnserver-jsonrpc-client-csharp/sample/VpnServerRpcTest.cs">VpnServerRpcTest.cs</a> program in C#. This sample calls one by one all of available JSON-RPC APIs against the specified SoftEther VPN Server.</li>
<p>You must specify the following HTTPS custom headers for authentication on each of requests.</p>
<table>
<thead>
<tr>
<th>Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>X-VPNADMIN-HUBNAME</code></td>
<td>The name of the Virtual Hub if you want to connect to the VPN Server as a Virtual Hub Admin Mode. Specify empty string if you want to connect to the VPN Server as the Entire VPN Server Admin Mode.</td>
</tr>
<tr>
<td><code>X-VPNADMIN-PASSWORD</code></td>
<td>Specify the administration password.</td>
</tr>
</tbody>
</table>
<ul>
<li>You can omit the above HTTPS custom authentication headers if you are calling JSON-RPC APIs from the web browser which is already logged in to the VPN Server with HTTPS Basic Authentication. In such usage the credential of HTTPS Basic Authtication will be used.</li>
</ul>
<hr/>
<h2id="table-of-contents">Table of contents</h2>
<ul>
<li><ahref="#test">Test - Test RPC function</a></li>
<li><ahref="#getserverinfo">GetServerInfo - Get server information</a></li>
<li><ahref="#getserverstatus">GetServerStatus - Get Current Server Status</a></li>
<li><ahref="#createlistener">CreateListener - Create New TCP Listener</a></li>
<li><ahref="#enumlistener">EnumListener - Get List of TCP Listeners</a></li>
<li><ahref="#enummactable">EnumMacTable - Get the MAC Address Table Database</a></li>
<li><ahref="#deletemactable">DeleteMacTable - Delete MAC Address Table Entry</a></li>
<li><ahref="#enumiptable">EnumIpTable - Get the IP Address Table Database</a></li>
<li><ahref="#deleteiptable">DeleteIpTable - Delete IP Address Table Entry</a></li>
<li><ahref="#setkeep">SetKeep - Set the Keep Alive Internet Connection Function</a></li>
<li><ahref="#getkeep">GetKeep - Get the Keep Alive Internet Connection Function</a></li>
<li><ahref="#enablesecurenat">EnableSecureNAT - Enable the Virtual NAT and DHCP Server Function (SecureNAT Function)</a></li>
<li><ahref="#disablesecurenat">DisableSecureNAT - Disable the Virtual NAT and DHCP Server Function (SecureNAT Function)</a></li>
<li><ahref="#setsecurenatoption">SetSecureNATOption - Change Settings of SecureNAT Function</a></li>
<li><ahref="#getsecurenatoption">GetSecureNATOption - Get Settings of SecureNAT Function</a></li>
<li><ahref="#enumnat">EnumNAT - Get Virtual NAT Function Session Table of SecureNAT Function</a></li>
<li><ahref="#enumdhcp">EnumDHCP - Get Virtual DHCP Server Function Lease Table of SecureNAT Function</a></li>
<li><ahref="#getsecurenatstatus">GetSecureNATStatus - Get the Operating Status of the Virtual NAT and DHCP Server Function (SecureNAT Function)</a></li>
<li><ahref="#enumethernet">EnumEthernet - Get List of Network Adapters Usable as Local Bridge</a></li>
<li><ahref="#addlocalbridge">AddLocalBridge - Create Local Bridge Connection</a></li>
<li><ahref="#deletelocalbridge">DeleteLocalBridge - Delete Local Bridge Connection</a></li>
<li><ahref="#enumlocalbridge">EnumLocalBridge - Get List of Local Bridge Connection</a></li>
<li><ahref="#getbridgesupport">GetBridgeSupport - Get whether the localbridge function is supported on the current system</a></li>
<li><ahref="#rebootserver">RebootServer - Reboot VPN Server Service</a></li>
<li><ahref="#getcaps">GetCaps - Get List of Server Functions / Capability</a></li>
<li><ahref="#getconfig">GetConfig - Get the current configuration of the VPN Server</a></li>
<li><ahref="#setconfig">SetConfig - Write Configuration File to VPN Server</a></li>
<li><ahref="#getdefaulthubadminoptions">GetDefaultHubAdminOptions - Get Virtual Hub Administration Option default values</a></li>
<li><ahref="#gethubadminoptions">GetHubAdminOptions - Get List of Virtual Hub Administration Options</a></li>
<li><ahref="#sethubadminoptions">SetHubAdminOptions - Set Values of Virtual Hub Administration Options</a></li>
<li><ahref="#gethubextoptions">GetHubExtOptions - Get List of Virtual Hub Extended Options</a></li>
<li><ahref="#sethubextoptions">SetHubExtOptions - Set a Value of Virtual Hub Extended Options</a></li>
<li><ahref="#addl3switch">AddL3Switch - Define New Virtual Layer 3 Switch</a></li>
<li><ahref="#setaclist">SetAcList - Add Rule to Source IP Address Limit List</a></li>
<li><ahref="#getaclist">GetAcList - Get List of Rule Items of Source IP Address Limit List</a></li>
<li><ahref="#enumlogfile">EnumLogFile - Get List of Log Files</a></li>
<li><ahref="#readlogfile">ReadLogFile - Download a part of Log File</a></li>
<li><ahref="#setsyslog">SetSysLog - Set syslog Send Function</a></li>
<li><ahref="#getsyslog">GetSysLog - Get syslog Send Function</a></li>
<li><ahref="#sethubmsg">SetHubMsg - Set Today's Message of Virtual Hub</a></li>
<li><ahref="#gethubmsg">GetHubMsg - Get Today's Message of Virtual Hub</a></li>
<li><ahref="#crash">Crash - Raise a vital error on the VPN Server / Bridge to terminate the process forcefully</a></li>
<li><ahref="#getadminmsg">GetAdminMsg - Get the message for administrators</a></li>
<li><ahref="#flush">Flush - Save All Volatile Data of VPN Server / Bridge to the Configuration File</a></li>
<li><ahref="#setipsecservices">SetIPsecServices - Enable or Disable IPsec VPN Server Function</a></li>
<li><ahref="#getipsecservices">GetIPsecServices - Get the Current IPsec VPN Server Settings</a></li>
<li><ahref="#addetheripid">AddEtherIpId - Add New EtherIP / L2TPv3 over IPsec Client Setting to Accept EthreIP / L2TPv3 Client Devices</a></li>
<li><ahref="#getetheripid">GetEtherIpId - Get the Current List of EtherIP / L2TPv3 Client Device Entry Definitions</a></li>
<li><ahref="#deleteetheripid">DeleteEtherIpId - Delete an EtherIP / L2TPv3 over IPsec Client Setting</a></li>
<li><ahref="#enumetheripid">EnumEtherIpId - Get the Current List of EtherIP / L2TPv3 Client Device Entry Definitions</a></li>
<li><ahref="#setopenvpnsstpconfig">SetOpenVpnSstpConfig - Set Settings for OpenVPN Clone Server Function</a></li>
<li><ahref="#getopenvpnsstpconfig">GetOpenVpnSstpConfig - Get the Current Settings of OpenVPN Clone Server Function</a></li>
<li><ahref="#getddnsclientstatus">GetDDnsClientStatus - Show the Current Status of Dynamic DNS Function</a></li>
<li><ahref="#changeddnsclienthostname">ChangeDDnsClientHostname - Set the Dynamic DNS Hostname</a></li>
<li><ahref="#regenerateservercert">RegenerateServerCert - Generate New Self-Signed Certificate with Specified CN (Common Name) and Register on VPN Server</a></li>
<li><ahref="#makeopenvpnconfigfile">MakeOpenVpnConfigFile - Generate a Sample Setting File for OpenVPN Client</a></li>
<li><ahref="#setspeciallistener">SetSpecialListener - Enable / Disable the VPN over ICMP / VPN over DNS Server Function</a></li>
<li><ahref="#getspeciallistener">GetSpecialListener - Get Current Setting of the VPN over ICMP / VPN over DNS Function</a></li>
<li><ahref="#getazurestatus">GetAzureStatus - Show the current status of VPN Azure function</a></li>
<p>Test RPC function. Input any integer value to the IntValue_u32 field. Then the server will convert the integer to the string, and return the string in the StrValue_str field.</p>
<p>Get server information. This allows you to obtain the server information of the currently connected VPN Server or VPN Bridge. Included in the server information are the version number, build number and build information. You can also obtain information on the current server operation mode and the information of operating system that the server is operating on.</p>
<td>Type of server<BR>Values:<BR><code>0</code>: Stand-alone server<BR><code>1</code>: Farm controller server<BR><code>2</code>: Farm member server</td>
</tr>
<tr>
<td><code>ServerBuildDate_dt</code></td>
<td><code>Date</code></td>
<td>Build date and time of the server</td>
</tr>
<tr>
<td><code>ServerFamilyName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Family name</td>
</tr>
<tr>
<td><code>OsType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>OS type<BR>Values:<BR><code>1100</code>: Windows 95<BR><code>1200</code>: Windows 98<BR><code>1300</code>: Windows Me<BR><code>1400</code>: Windows (unknown)<BR><code>2100</code>: Windows NT 4.0 Workstation<BR><code>2110</code>: Windows NT 4.0 Server<BR><code>2111</code>: Windows NT 4.0 Server, Enterprise Edition<BR><code>2112</code>: Windows NT 4.0 Terminal Server<BR><code>2113</code>: BackOffice Server 4.5<BR><code>2114</code>: Small Business Server 4.5<BR><code>2200</code>: Windows 2000 Professional<BR><code>2211</code>: Windows 2000 Server<BR><code>2212</code>: Windows 2000 Advanced Server<BR><code>2213</code>: Windows 2000 Datacenter Server<BR><code>2214</code>: BackOffice Server 2000<BR><code>2215</code>: Small Business Server 2000<BR><code>2300</code>: Windows XP Home Edition<BR><code>2301</code>: Windows XP Professional<BR><code>2410</code>: Windows Server 2003 Web Edition<BR><code>2411</code>: Windows Server 2003 Standard Edition<BR><code>2412</code>: Windows Server 2003 Enterprise Edition<BR><code>2413</code>: Windows Server 2003 DataCenter Edition<BR><code>2414</code>: BackOffice Server 2003<BR><code>2415</code>: Small Business Server 2003<BR><code>2500</code>: Windows Vista<BR><code>2510</code>: Windows Server 2008<BR><code>2600</code>: Windows 7<BR><code>2610</code>: Windows Server 2008 R2<BR><code>2700</code>: Windows 8<BR><code>2710</code>: Windows Server 2012<BR><code>2701</code>: Windows 8.1<BR><code>2711</code>: Windows Server 2012 R2<BR><code>2702</code>: Windows 10<BR><code>2712</code>: Windows Server 10<BR><code>2800</code>: Windows 11 or later<BR><code>2810</code>: Windows Server 11 or later<BR><code>3000</code>: Unknown UNIX<BR><code>3100</code>: Linux<BR><code>3200</code>: Solaris<BR><code>3300</code>: Cygwin<BR><code>3400</code>: BSD<BR><code>3500</code>: MacOS X</td>
</tr>
<tr>
<td><code>OsServicePack_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Service pack number</td>
</tr>
<tr>
<td><code>OsSystemName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>OS system name</td>
</tr>
<tr>
<td><code>OsProductName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>OS product name</td>
</tr>
<tr>
<td><code>OsVendorName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>OS vendor name</td>
</tr>
<tr>
<td><code>OsVersion_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>OS version</td>
</tr>
<tr>
<td><code>KernelName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Kernel name</td>
</tr>
<tr>
<td><code>KernelVersion_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Kernel version</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getserverstatus"></a></p>
<h2id="getserverstatus-rpc-api-get-current-server-status">"GetServerStatus" RPC API - Get Current Server Status</h2>
<p>Get Current Server Status. This allows you to obtain in real-time the current status of the currently connected VPN Server or VPN Bridge. You can get statistical information on data communication and the number of different kinds of objects that exist on the server. You can get information on how much memory is being used on the current computer by the OS.</p>
<p>Create New TCP Listener. This allows you to create a new TCP Listener on the server. By creating the TCP Listener the server starts listening for a connection from clients at the specified TCP/IP port number. A TCP Listener that has been created can be deleted by the DeleteListener API. You can also get a list of TCP Listeners currently registered by using the EnumListener API. To execute this API, you must have VPN Server administrator privileges.</p>
<p>Get List of TCP Listeners. This allows you to get a list of TCP listeners registered on the current server. You can obtain information on whether the various TCP listeners have a status of operating or error. To call this API, you must have VPN Server administrator privileges.</p>
<p>Delete TCP Listener. This allows you to delete a TCP Listener that's registered on the server. When the TCP Listener is in a state of operation, the listener will automatically be deleted when its operation stops. You can also get a list of TCP Listeners currently registered by using the EnumListener API. To call this API, you must have VPN Server administrator privileges.</p>
<p>Enable / Disable TCP Listener. This starts or stops the operation of TCP Listeners registered on the current server. You can also get a list of TCP Listeners currently registered by using the EnumListener API. To call this API, you must have VPN Server administrator privileges.</p>
<h2id="setserverpassword-rpc-api-set-vpn-server-administrator-password">"SetServerPassword" RPC API - Set VPN Server Administrator Password</h2>
<p>Set VPN Server Administrator Password. This sets the VPN Server administrator password. You can specify the password as a parameter. To call this API, you must have VPN Server administrator privileges.</p>
<h2id="setfarmsetting-rpc-api-set-the-vpn-server-clustering-configuration">"SetFarmSetting" RPC API - Set the VPN Server clustering configuration</h2>
<p>Set the VPN Server clustering configuration. Use this to set the VPN Server type as Standalone Server, Cluster Controller Server or Cluster Member Server. Standalone server means a VPN Server that does not belong to any cluster in its current state. When VPN Server is installed, by default it will be in standalone server mode. Unless you have particular plans to configure a cluster, we recommend the VPN Server be operated in standalone mode. A cluster controller is the central computer of all member servers of a cluster in the case where a clustering environment is made up of multiple VPN Servers. Multiple cluster members can be added to the cluster as required. A cluster requires one computer to serve this role. The other cluster member servers that are configured in the same cluster begin operation as a cluster member by connecting to the cluster controller. To call this API, you must have VPN Server administrator privileges. Also, when this API is executed, VPN Server will automatically restart. This API cannot be called on VPN Bridge.</p>
<td>Type of server<BR>Values:<BR><code>0</code>: Stand-alone server<BR><code>1</code>: Farm controller server<BR><code>2</code>: Farm member server</td>
</tr>
<tr>
<td><code>NumPort_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Valid only for Cluster Member servers. Number of the Ports_u32 element.</td>
</tr>
<tr>
<td><code>Ports_u32</code></td>
<td><code>number[]</code> (uint32)</td>
<td>Valid only for Cluster Member servers. Specify the list of public port numbers on this server. The list must have at least one public port number set, and it is also possible to set multiple public port numbers.</td>
</tr>
<tr>
<td><code>PublicIp_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only for Cluster Member servers. Specify the public IP address of this server. If you wish to leave public IP address unspecified, specify the empty string. When a public IP address is not specified, the IP address of the network interface used when connecting to the cluster controller will be automatically used.</td>
</tr>
<tr>
<td><code>ControllerName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Valid only for Cluster Member servers. Specify the host name or IP address of the destination cluster controller.</td>
</tr>
<tr>
<td><code>ControllerPort_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Valid only for Cluster Member servers. Specify the TCP port number of the destination cluster controller.</td>
</tr>
<tr>
<td><code>MemberPasswordPlaintext_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Valid only for Cluster Member servers. Specify the password required to connect to the destination controller. It needs to be the same as an administrator password on the destination controller.</td>
</tr>
<tr>
<td><code>Weight_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>This sets a value for the performance standard ratio of this VPN Server. This is the standard value for when load balancing is performed in the cluster. For example, making only one machine 200 while the other members have a status of 100, will regulate that machine to receive twice as many connections as the other members. Specify 1 or higher for the value. If this parameter is left unspecified, 100 will be used.</td>
</tr>
<tr>
<td><code>ControllerOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Valid only for Cluster Controller server. By specifying true, the VPN Server will operate only as a controller on the cluster and it will always distribute general VPN Client connections to members other than itself. This function is used in high-load environments.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getfarmsetting"></a></p>
<h2id="getfarmsetting-rpc-api-get-clustering-configuration-of-current-vpn-server">"GetFarmSetting" RPC API - Get Clustering Configuration of Current VPN Server</h2>
<p>Get Clustering Configuration of Current VPN Server. You can use this to acquire the clustering configuration of the current VPN Server. To call this API, you must have VPN Server administrator privileges.</p>
<td>Type of server<BR>Values:<BR><code>0</code>: Stand-alone server<BR><code>1</code>: Farm controller server<BR><code>2</code>: Farm member server</td>
</tr>
<tr>
<td><code>NumPort_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Valid only for Cluster Member servers. Number of the Ports_u32 element.</td>
</tr>
<tr>
<td><code>Ports_u32</code></td>
<td><code>number[]</code> (uint32)</td>
<td>Valid only for Cluster Member servers. Specify the list of public port numbers on this server. The list must have at least one public port number set, and it is also possible to set multiple public port numbers.</td>
</tr>
<tr>
<td><code>PublicIp_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only for Cluster Member servers. Specify the public IP address of this server. If you wish to leave public IP address unspecified, specify the empty string. When a public IP address is not specified, the IP address of the network interface used when connecting to the cluster controller will be automatically used.</td>
</tr>
<tr>
<td><code>ControllerName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Valid only for Cluster Member servers. Specify the host name or IP address of the destination cluster controller.</td>
</tr>
<tr>
<td><code>ControllerPort_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Valid only for Cluster Member servers. Specify the TCP port number of the destination cluster controller.</td>
</tr>
<tr>
<td><code>MemberPasswordPlaintext_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Valid only for Cluster Member servers. Specify the password required to connect to the destination controller. It needs to be the same as an administrator password on the destination controller.</td>
</tr>
<tr>
<td><code>Weight_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>This sets a value for the performance standard ratio of this VPN Server. This is the standard value for when load balancing is performed in the cluster. For example, making only one machine 200 while the other members have a status of 100, will regulate that machine to receive twice as many connections as the other members. Specify 1 or higher for the value. If this parameter is left unspecified, 100 will be used.</td>
</tr>
<tr>
<td><code>ControllerOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Valid only for Cluster Controller server. By specifying true, the VPN Server will operate only as a controller on the cluster and it will always distribute general VPN Client connections to members other than itself. This function is used in high-load environments.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getfarminfo"></a></p>
<h2id="getfarminfo-rpc-api-get-cluster-member-information">"GetFarmInfo" RPC API - Get Cluster Member Information</h2>
<p>Get Cluster Member Information. When the VPN Server is operating as a cluster controller, you can get information on cluster member servers on that cluster by specifying the IDs of the member servers. You can get the following information about the specified cluster member server: Server Type, Time Connection has been Established, IP Address, Host Name, Points, Public Port List, Number of Operating Virtual Hubs, First Virtual Hub, Number of Sessions and Number of TCP Connections. This API cannot be invoked on VPN Bridge.</p>
<p>Get List of Cluster Members. Use this API when the VPN Server is operating as a cluster controller to get a list of the cluster member servers on the same cluster, including the cluster controller itself. For each member, the following information is also listed: Type, Connection Start, Host Name, Points, Number of Session, Number of TCP Connections, Number of Operating Virtual Hubs, Using Client Connection License and Using Bridge Connection License. This API cannot be invoked on VPN Bridge.</p>
<h2id="getfarmconnectionstatus-rpc-api-get-connection-status-to-cluster-controller">"GetFarmConnectionStatus" RPC API - Get Connection Status to Cluster Controller</h2>
<p>Get Connection Status to Cluster Controller. Use this API when the VPN Server is operating as a cluster controller to get the status of connection to the cluster controller. You can get the following information: Controller IP Address, Port Number, Connection Status, Connection Start Time, First Connection Established Time, Current Connection Established Time, Number of Connection Attempts, Number of Successful Connections, Number of Failed Connections. This API cannot be invoked on VPN Bridge.</p>
<h2id="setservercert-rpc-api-set-ssl-certificate-and-private-key-of-vpn-server">"SetServerCert" RPC API - Set SSL Certificate and Private Key of VPN Server</h2>
<p>Set SSL Certificate and Private Key of VPN Server. You can set the SSL certificate that the VPN Server provides to the connected client and the private key for that certificate. The certificate must be in X.509 format and the private key must be Base 64 encoded format. To call this API, you must have VPN Server administrator privileges.</p>
<h2id="getservercert-rpc-api-get-ssl-certificate-and-private-key-of-vpn-server">"GetServerCert" RPC API - Get SSL Certificate and Private Key of VPN Server</h2>
<p>Get SSL Certificate and Private Key of VPN Server. Use this to get the SSL certificate private key that the VPN Server provides to the connected client. To call this API, you must have VPN Server administrator privileges.</p>
<h2id="getservercipher-rpc-api-get-the-encrypted-algorithm-used-for-vpn-communication">"GetServerCipher" RPC API - Get the Encrypted Algorithm Used for VPN Communication</h2>
<p>Get the Encrypted Algorithm Used for VPN Communication. Use this API to get the current setting of the algorithm used for the electronic signature and encrypted for SSL connection to be used for communication between the VPN Server and the connected client and the list of algorithms that can be used on the VPN Server.</p>
<h2id="setservercipher-rpc-api-set-the-encrypted-algorithm-used-for-vpn-communication">"SetServerCipher" RPC API - Set the Encrypted Algorithm Used for VPN Communication</h2>
<p>Set the Encrypted Algorithm Used for VPN Communication. Use this API to set the algorithm used for the electronic signature and encrypted for SSL connections to be used for communication between the VPN Server and the connected client. By specifying the algorithm name, the specified algorithm will be used later between the VPN Client and VPN Bridge connected to this server and the data will be encrypted. To call this API, you must have VPN Server administrator privileges.</p>
<p>Create New Virtual Hub. Use this to create a new Virtual Hub on the VPN Server. The created Virtual Hub will begin operation immediately. When the VPN Server is operating on a cluster, this API is only valid for the cluster controller. Also, the new Virtual Hub will operate as a dynamic Virtual Hub. You can change it to a static Virtual Hub by using the SetHub API. To get a list of Virtual Hubs that are already on the VPN Server, use the EnumHub API. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Servers that are operating as a VPN Bridge or cluster member.</p>
<td>Specify the name of the Virtual Hub to create / update.</td>
</tr>
<tr>
<td><code>AdminPasswordPlainText_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify an administrator password when the administrator password is going to be set for the Virtual Hub. On the update, leave it to empty string if you don't want to change the password.</td>
</tr>
<tr>
<td><code>Online_bool</code></td>
<td><code>boolean</code></td>
<td>Online flag</td>
</tr>
<tr>
<td><code>MaxSession_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Maximum number of VPN sessions</td>
</tr>
<tr>
<td><code>NoEnum_bool</code></td>
<td><code>boolean</code></td>
<td>No Enum flag. By enabling this option, the VPN Client user will be unable to enumerate this Virtual Hub even if they send a Virtual Hub enumeration request to the VPN Server.</td>
</tr>
<tr>
<td><code>HubType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Type of the Virtual Hub (Valid only for Clustered VPN Servers)<BR>Values:<BR><code>0</code>: Stand-alone HUB<BR><code>1</code>: Static HUB<BR><code>2</code>: Dynamic HUB</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="sethub"></a></p>
<h2id="sethub-rpc-api-set-the-virtual-hub-configuration">"SetHub" RPC API - Set the Virtual Hub configuration</h2>
<p>Set the Virtual Hub configuration. You can call this API to change the configuration of the specified Virtual Hub. You can set the Virtual Hub online or offline. You can set the maximum number of sessions that can be concurrently connected to the Virtual Hub that is currently being managed. You can set the Virtual Hub administrator password. You can set other parameters for the Virtual Hub. Before call this API, you need to obtain the latest state of the Virtual Hub by using the GetHub API.</p>
<td>Specify the name of the Virtual Hub to create / update.</td>
</tr>
<tr>
<td><code>AdminPasswordPlainText_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify an administrator password when the administrator password is going to be set for the Virtual Hub. On the update, leave it to empty string if you don't want to change the password.</td>
</tr>
<tr>
<td><code>Online_bool</code></td>
<td><code>boolean</code></td>
<td>Online flag</td>
</tr>
<tr>
<td><code>MaxSession_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Maximum number of VPN sessions</td>
</tr>
<tr>
<td><code>NoEnum_bool</code></td>
<td><code>boolean</code></td>
<td>No Enum flag. By enabling this option, the VPN Client user will be unable to enumerate this Virtual Hub even if they send a Virtual Hub enumeration request to the VPN Server.</td>
</tr>
<tr>
<td><code>HubType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Type of the Virtual Hub (Valid only for Clustered VPN Servers)<BR>Values:<BR><code>0</code>: Stand-alone HUB<BR><code>1</code>: Static HUB<BR><code>2</code>: Dynamic HUB</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="gethub"></a></p>
<h2id="gethub-rpc-api-get-the-virtual-hub-configuration">"GetHub" RPC API - Get the Virtual Hub configuration</h2>
<p>Get the Virtual Hub configuration. You can call this API to get the current configuration of the specified Virtual Hub. To change the configuration of the Virtual Hub, call the SetHub API.</p>
<td>Specify the name of the Virtual Hub to create / update.</td>
</tr>
<tr>
<td><code>AdminPasswordPlainText_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify an administrator password when the administrator password is going to be set for the Virtual Hub. On the update, leave it to empty string if you don't want to change the password.</td>
</tr>
<tr>
<td><code>Online_bool</code></td>
<td><code>boolean</code></td>
<td>Online flag</td>
</tr>
<tr>
<td><code>MaxSession_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Maximum number of VPN sessions</td>
</tr>
<tr>
<td><code>NoEnum_bool</code></td>
<td><code>boolean</code></td>
<td>No Enum flag. By enabling this option, the VPN Client user will be unable to enumerate this Virtual Hub even if they send a Virtual Hub enumeration request to the VPN Server.</td>
</tr>
<tr>
<td><code>HubType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Type of the Virtual Hub (Valid only for Clustered VPN Servers)<BR>Values:<BR><code>0</code>: Stand-alone HUB<BR><code>1</code>: Static HUB<BR><code>2</code>: Dynamic HUB</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="enumhub"></a></p>
<h2id="enumhub-rpc-api-get-list-of-virtual-hubs">"EnumHub" RPC API - Get List of Virtual Hubs</h2>
<p>Get List of Virtual Hubs. Use this to get a list of existing Virtual Hubs on the VPN Server. For each Virtual Hub, you can get the following information: Virtual Hub Name, Status, Type, Number of Users, Number of Groups, Number of Sessions, Number of MAC Tables, Number of IP Tables, Number of Logins, Last Login, and Last Communication. Note that when connecting in Virtual Hub Admin Mode, if in the options of a Virtual Hub that you do not have administrator privileges for, the option Don't Enumerate this Virtual Hub for Anonymous Users is enabled then that Virtual Hub will not be enumerated. If you are connected in Server Admin Mode, then the list of all Virtual Hubs will be displayed. When connecting to and managing a non-cluster-controller cluster member of a clustering environment, only the Virtual Hub currently being hosted by that VPN Server will be displayed. When connecting to a cluster controller for administration purposes, all the Virtual Hubs will be displayed.</p>
<td>Type of HUB (Valid only for Clustered VPN Servers)<BR>Values:<BR><code>0</code>: Stand-alone HUB<BR><code>1</code>: Static HUB<BR><code>2</code>: Dynamic HUB</td>
</tr>
<tr>
<td><code>NumUsers_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Number of users</td>
</tr>
<tr>
<td><code>NumGroups_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Number of registered groups</td>
</tr>
<tr>
<td><code>NumSessions_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Number of registered sessions</td>
</tr>
<tr>
<td><code>NumMacTables_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Number of current MAC table entries</td>
</tr>
<tr>
<td><code>NumIpTables_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Number of current IP table entries</td>
</tr>
<tr>
<td><code>LastCommTime_dt</code></td>
<td><code>Date</code></td>
<td>Last communication date and time</td>
</tr>
<tr>
<td><code>LastLoginTime_dt</code></td>
<td><code>Date</code></td>
<td>Last login date and time</td>
</tr>
<tr>
<td><code>CreatedTime_dt</code></td>
<td><code>Date</code></td>
<td>Creation date and time</td>
</tr>
<tr>
<td><code>NumLogin_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Number of accumulated logins</td>
</tr>
<tr>
<td><code>IsTrafficFilled_bool</code></td>
<td><code>boolean</code></td>
<td>Whether the traffic information is provided</td>
</tr>
<tr>
<td><code>Ex.Recv.BroadcastBytes_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Number of broadcast packets (Recv)</td>
</tr>
<tr>
<td><code>Ex.Recv.BroadcastCount_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Broadcast bytes (Recv)</td>
</tr>
<tr>
<td><code>Ex.Recv.UnicastBytes_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Unicast count (Recv)</td>
</tr>
<tr>
<td><code>Ex.Recv.UnicastCount_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Unicast bytes (Recv)</td>
</tr>
<tr>
<td><code>Ex.Send.BroadcastBytes_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Number of broadcast packets (Send)</td>
</tr>
<tr>
<td><code>Ex.Send.BroadcastCount_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Broadcast bytes (Send)</td>
</tr>
<tr>
<td><code>Ex.Send.UnicastBytes_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Unicast bytes (Send)</td>
</tr>
<tr>
<td><code>Ex.Send.UnicastCount_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Unicast bytes (Send)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="deletehub"></a></p>
<h2id="deletehub-rpc-api-delete-virtual-hub">"DeleteHub" RPC API - Delete Virtual Hub</h2>
<p>Delete Virtual Hub. Use this to delete an existing Virtual Hub on the VPN Server. If you delete the Virtual Hub, all sessions that are currently connected to the Virtual Hub will be disconnected and new sessions will be unable to connect to the Virtual Hub. Also, this will also delete all the Hub settings, user objects, group objects, certificates and Cascade Connections. Once you delete the Virtual Hub, it cannot be recovered. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Servers that are operating as a VPN Bridge or cluster member.</p>
<h2id="gethubradius-rpc-api-get-setting-of-radius-server-used-for-user-authentication">"GetHubRadius" RPC API - Get Setting of RADIUS Server Used for User Authentication</h2>
<p>Get Setting of RADIUS Server Used for User Authentication. Use this to get the current settings for the RADIUS server used when a user connects to the currently managed Virtual Hub using RADIUS Server Authentication Mode. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<h2id="sethubradius-rpc-api-set-radius-server-to-use-for-user-authentication">"SetHubRadius" RPC API - Set RADIUS Server to use for User Authentication</h2>
<p>Set RADIUS Server to use for User Authentication. To accept users to the currently managed Virtual Hub in RADIUS server authentication mode, you can specify an external RADIUS server that confirms the user name and password. (You can specify multiple hostname by splitting with comma or semicolon.) The RADIUS server must be set to receive requests from IP addresses of this VPN Server. Also, authentication by Password Authentication Protocol (PAP) must be enabled. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<h2id="enumconnection-rpc-api-get-list-of-tcp-connections-connecting-to-the-vpn-server">"EnumConnection" RPC API - Get List of TCP Connections Connecting to the VPN Server</h2>
<p>Get List of TCP Connections Connecting to the VPN Server. Use this to get a list of TCP/IP connections that are currently connecting to the VPN Server. It does not display the TCP connections that have been established as VPN sessions. To get the list of TCP/IP connections that have been established as VPN sessions, you can use the EnumSession API. You can get the following: Connection Name, Connection Source, Connection Start and Type. To call this API, you must have VPN Server administrator privileges.</p>
<td>Connection type<BR>Values:<BR><code>0</code>: VPN Client<BR><code>1</code>: During initialization<BR><code>2</code>: Login connection<BR><code>3</code>: Additional connection<BR><code>4</code>: RPC for server farm<BR><code>5</code>: RPC for Management<BR><code>6</code>: HUB enumeration<BR><code>7</code>: Password change<BR><code>8</code>: SSTP<BR><code>9</code>: OpenVPN</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="disconnectconnection"></a></p>
<h2id="disconnectconnection-rpc-api-disconnect-tcp-connections-connecting-to-the-vpn-server">"DisconnectConnection" RPC API - Disconnect TCP Connections Connecting to the VPN Server</h2>
<p>Disconnect TCP Connections Connecting to the VPN Server. Use this to forcefully disconnect specific TCP/IP connections that are connecting to the VPN Server. To call this API, you must have VPN Server administrator privileges.</p>
<h2id="getconnectioninfo-rpc-api-get-information-of-tcp-connections-connecting-to-the-vpn-server">"GetConnectionInfo" RPC API - Get Information of TCP Connections Connecting to the VPN Server</h2>
<p>Get Information of TCP Connections Connecting to the VPN Server. Use this to get detailed information of a specific TCP/IP connection that is connecting to the VPN Server. You can get the following information: Connection Name, Connection Type, Source Hostname, Source IP Address, Source Port Number (TCP), Connection Start, Server Product Name, Server Version, Server Build Number, Client Product Name, Client Version, and Client Build Number. To call this API, you must have VPN Server administrator privileges.</p>
<p>Switch Virtual Hub to Online or Offline. Use this to set the Virtual Hub to online or offline. A Virtual Hub with an offline status cannot receive VPN connections from clients. When you set the Virtual Hub offline, all sessions will be disconnected. A Virtual Hub with an offline status cannot receive VPN connections from clients. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Get Current Status of Virtual Hub. Use this to get the current status of the Virtual Hub currently being managed. You can get the following information: Virtual Hub Type, Number of Sessions, Number of Each Type of Object, Number of Logins, Last Login, Last Communication, and Communication Statistical Data.</p>
<h2id="sethublog-rpc-api-set-the-logging-configuration-of-the-virtual-hub">"SetHubLog" RPC API - Set the logging configuration of the Virtual Hub</h2>
<p>Set the logging configuration of the Virtual Hub. Use this to enable or disable a security log or packet logs of the Virtual Hub currently being managed, set the save contents of the packet log for each type of packet to be saved, and set the log file switch cycle for the security log or packet log that the currently managed Virtual Hub saves. There are the following packet types: TCP Connection Log, TCP Packet Log, DHCP Packet Log, UDP Packet Log, ICMP Packet Log, IP Packet Log, ARP Packet Log, and Ethernet Packet Log. To get the current setting, you can use the LogGet API. The log file switch cycle can be changed to switch in every second, every minute, every hour, every day, every month or not switch. To get the current setting, you can use the GetHubLog API.</p>
<td>The flag to enable / disable saving the security log</td>
</tr>
<tr>
<td><code>SecurityLogSwitchType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>The log filename switching setting of the security log<BR>Values:<BR><code>0</code>: No switching<BR><code>1</code>: Secondly basis<BR><code>2</code>: Minutely basis<BR><code>3</code>: Hourly basis<BR><code>4</code>: Daily basis<BR><code>5</code>: Monthly basis</td>
</tr>
<tr>
<td><code>SavePacketLog_bool</code></td>
<td><code>boolean</code></td>
<td>The flag to enable / disable saving the security log</td>
</tr>
<tr>
<td><code>PacketLogSwitchType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>The log filename switching settings of the packet logs<BR>Values:<BR><code>0</code>: No switching<BR><code>1</code>: Secondly basis<BR><code>2</code>: Minutely basis<BR><code>3</code>: Hourly basis<BR><code>4</code>: Daily basis<BR><code>5</code>: Monthly basis</td>
</tr>
<tr>
<td><code>PacketLogConfig_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Specify the save contents of the packet logs (uint * 16 array). The index numbers: TcpConnection = 0, TcpAll = 1, DHCP = 2, UDP = 3, ICMP = 4, IP = 5, ARP = 6, Ethernet = 7.<BR>Values:<BR><code>0</code>: Not save<BR><code>1</code>: Only header<BR><code>2</code>: All payloads</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="gethublog"></a></p>
<h2id="gethublog-rpc-api-get-the-logging-configuration-of-the-virtual-hub">"GetHubLog" RPC API - Get the logging configuration of the Virtual Hub</h2>
<p>Get the logging configuration of the Virtual Hub. Use this to get the configuration for a security log or packet logs of the Virtual Hub currently being managed, get the setting for save contents of the packet log for each type of packet to be saved, and get the log file switch cycle for the security log or packet log that the currently managed Virtual Hub saves. To set the current setting, you can use the SetHubLog API.</p>
<td>The flag to enable / disable saving the security log</td>
</tr>
<tr>
<td><code>SecurityLogSwitchType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>The log filename switching setting of the security log<BR>Values:<BR><code>0</code>: No switching<BR><code>1</code>: Secondly basis<BR><code>2</code>: Minutely basis<BR><code>3</code>: Hourly basis<BR><code>4</code>: Daily basis<BR><code>5</code>: Monthly basis</td>
</tr>
<tr>
<td><code>SavePacketLog_bool</code></td>
<td><code>boolean</code></td>
<td>The flag to enable / disable saving the security log</td>
</tr>
<tr>
<td><code>PacketLogSwitchType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>The log filename switching settings of the packet logs<BR>Values:<BR><code>0</code>: No switching<BR><code>1</code>: Secondly basis<BR><code>2</code>: Minutely basis<BR><code>3</code>: Hourly basis<BR><code>4</code>: Daily basis<BR><code>5</code>: Monthly basis</td>
</tr>
<tr>
<td><code>PacketLogConfig_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Specify the save contents of the packet logs (uint * 16 array). The index numbers: TcpConnection = 0, TcpAll = 1, DHCP = 2, UDP = 3, ICMP = 4, IP = 5, ARP = 6, Ethernet = 7.<BR>Values:<BR><code>0</code>: Not save<BR><code>1</code>: Only header<BR><code>2</code>: All payloads</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="addca"></a></p>
<h2id="addca-rpc-api-add-trusted-ca-certificate">"AddCa" RPC API - Add Trusted CA Certificate</h2>
<p>Add Trusted CA Certificate. Use this to add a new certificate to a list of CA certificates trusted by the currently managed Virtual Hub. The list of certificate authority certificates that are registered is used to verify certificates when a VPN Client is connected in signed certificate authentication mode. To get a list of the current certificates you can use the EnumCa API. The certificate you add must be saved in the X.509 file format. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<p>Get List of Trusted CA Certificates. Here you can manage the certificate authority certificates that are trusted by this currently managed Virtual Hub. The list of certificate authority certificates that are registered is used to verify certificates when a VPN Client is connected in signed certificate authentication mode. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<p>Get Trusted CA Certificate. Use this to get an existing certificate from the list of CA certificates trusted by the currently managed Virtual Hub and save it as a file in X.509 format. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<p>Delete Trusted CA Certificate. Use this to delete an existing certificate from the list of CA certificates trusted by the currently managed Virtual Hub. To get a list of the current certificates you can use the EnumCa API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<p>Create New Cascade Connection. Use this to create a new Cascade Connection on the currently managed Virtual Hub. By using a Cascade Connection, you can connect this Virtual Hub by Cascade Connection to another Virtual Hub that is operating on the same or a different computer. To create a Cascade Connection, you must specify the name of the Cascade Connection, destination server and destination Virtual Hub and user name. When a new Cascade Connection is created, the type of user authentication is initially set as Anonymous Authentication and the proxy server setting and the verification options of the server certificate is not set. To change these settings and other advanced settings after a Cascade Connection has been created, use the other APIs that include the name "Link". [Warning About Cascade Connections] By connecting using a Cascade Connection you can create a Layer 2 bridge between multiple Virtual Hubs but if the connection is incorrectly configured, a loopback Cascade Connection could inadvertently be created. When using a Cascade Connection function please design the network topology with care. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>The flag to enable validation for the server certificate</td>
</tr>
<tr>
<td><code>ServerCert_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>The body of server X.509 certificate to compare. Valid only if the CheckServerCert_bool flag is true.</td>
</tr>
<tr>
<td><code>AccountName_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Client Option Parameters: Specify the name of the Cascade Connection</td>
</tr>
<tr>
<td><code>Hostname_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: Specify the hostname of the destination VPN Server. You can also specify by IP address.</td>
</tr>
<tr>
<td><code>Port_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Client Option Parameters: Specify the port number of the destination VPN Server.</td>
</tr>
<tr>
<td><code>ProxyType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Client Option Parameters: The type of the proxy server<BR>Values:<BR><code>0</code>: Direct TCP connection<BR><code>1</code>: Connection via HTTP proxy server<BR><code>2</code>: Connection via SOCKS proxy server</td>
</tr>
<tr>
<td><code>ProxyName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The hostname or IP address of the proxy server name</td>
</tr>
<tr>
<td><code>ProxyPort_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Client Option Parameters: The port number of the proxy server</td>
</tr>
<tr>
<td><code>ProxyUsername_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The username to connect to the proxy server</td>
</tr>
<tr>
<td><code>ProxyPassword_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The password to connect to the proxy server</td>
</tr>
<tr>
<td><code>HubName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The Virtual Hub on the destination VPN Server</td>
</tr>
<tr>
<td><code>MaxConnection_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Client Option Parameters: Number of TCP Connections to Use in VPN Communication</td>
</tr>
<tr>
<td><code>UseEncrypt_bool</code></td>
<td><code>boolean</code></td>
<td>Client Option Parameters: The flag to enable the encryption on the communication</td>
</tr>
<tr>
<td><code>UseCompress_bool</code></td>
<td><code>boolean</code></td>
<td>Client Option Parameters: Enable / Disable Data Compression when Communicating by Cascade Connection</td>
</tr>
<tr>
<td><code>HalfConnection_bool</code></td>
<td><code>boolean</code></td>
<td>Client Option Parameters: Specify true when enabling half duplex mode. When using two or more TCP connections for VPN communication, it is possible to use Half Duplex Mode. By enabling half duplex mode it is possible to automatically fix data transmission direction as half and half for each TCP connection. In the case where a VPN using 8 TCP connections is established, for example, when half-duplex is enabled, communication can be fixes so that 4 TCP connections are dedicated to the upload direction and the other 4 connections are dedicated to the download direction.</td>
<td>SHA-0 Hashed password. Valid only if ClientAuth_AuthType_u32 == SHA0_Hashed_Password (1). The SHA-0 hashed password must be caluclated by the SHA0(UpperCase(username_ascii_string) + password_ascii_string).</td>
</tr>
<tr>
<td><code>PlainPassword_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Plaintext Password. Valid only if ClientAuth_AuthType_u32 == PlainPassword (2).</td>
</tr>
<tr>
<td><code>ClientX_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Client certificate. Valid only if ClientAuth_AuthType_u32 == Cert (3).</td>
</tr>
<tr>
<td><code>ClientK_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Client private key of the certificate. Valid only if ClientAuth_AuthType_u32 == Cert (3).</td>
</tr>
<tr>
<td><code>policy:DHCPFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv4). All IPv4 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPNoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv4). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv4 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:DHCPForce_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Enforce DHCP Allocated IP Addresses (IPv4). Computers in sessions that have this policy setting will only be able to use IPv4 addresses allocated by a DHCP server on the virtual network side.</td>
</tr>
<tr>
<td><code>SecPol_CheckMac_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Prohibit the duplicate MAC address</td>
</tr>
<tr>
<td><code>SecPol_CheckIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Prohibit a duplicate IP address (IPv4)</td>
</tr>
<tr>
<td><code>policy:ArpDhcpOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Non-ARP / Non-DHCP / Non-ICMPv6 broadcasts. The sending or receiving of broadcast packets that are not ARP protocol, DHCP protocol, nor ICMPv6 on the virtual network will not be allowed for sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:PrivacyFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Privacy Filter Mode. All direct communication between sessions with the privacy filter mode policy setting will be filtered.</td>
</tr>
<tr>
<td><code>policy:NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv4). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv4.</td>
<td>Security policy: Unlimited Number of Broadcasts. If a computer of a session with this policy setting sends broadcast packets of a number unusually larger than what would be considered normal on the virtual network, there will be no automatic limiting.</td>
</tr>
<tr>
<td><code>policy:MaxMac_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of MAC Addresses. For sessions with this policy setting, this limits the number of MAC addresses per session.</td>
</tr>
<tr>
<td><code>policy:MaxIP_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv4). For sessions with this policy setting, this specifies the number of IPv4 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:MaxUpload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Upload Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the inwards direction from outside to inside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxDownload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Download Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the outwards direction from inside the Virtual Hub to outside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:RSandRAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RS / RA Packets (IPv6). All ICMPv6 packets which the message-type is 133 (Router Solicitation) or 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, an IPv6 client will be unable to use IPv6 address prefix auto detection and IPv6 default gateway auto detection.</td>
</tr>
<tr>
<td><code>SecPol_RAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter the router advertisement packet (IPv6)</td>
</tr>
<tr>
<td><code>policy:DHCPv6Filter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv6). All IPv6 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPv6NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv6). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv6 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>SecPol_CheckIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Prohibit the duplicate IP address (IPv6)</td>
</tr>
<tr>
<td><code>policy:NoServerV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv6). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv6.</td>
</tr>
<tr>
<td><code>policy:MaxIPv6_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv6). For sessions with this policy setting, this specifies the number of IPv6 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:FilterIPv4_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv4 Packets. All IPv4 and ARP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv6 Packets. All IPv6 packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterNonIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All Non-IP Packets. All non-IP packets in sessions defined this policy will be filtered. "Non-IP packet" mean a packet which is not IPv4, ARP nor IPv6. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets.</td>
<td>Security policy: No Default-Router on IPv6 RA. In all VPN Sessions defines this policy, any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
</tr>
<tr>
<td><code>policy:VLanId_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VLAN ID (IEEE802.1Q). You can specify the VLAN ID on the security policy. All VPN Sessions defines this policy, all Ethernet packets toward the Virtual Hub from the user will be inserted a VLAN tag (IEEE 802.1Q) with the VLAN ID. The user can also receive only packets with a VLAN tag which has the same VLAN ID. (Receiving process removes the VLAN tag automatically.) Any Ethernet packets with any other VLAN IDs or non-VLAN packets will not be received. All VPN Sessions without this policy definition can send / receive any kinds of Ethernet packets regardless of VLAN tags, and VLAN tags are not inserted or removed automatically. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets. Therefore, tagged-VLAN packets are not subjects for IPv4 / IPv6 security policies, access lists nor other IPv4 / IPv6 specific deep processing.</td>
</tr>
<tr>
<td><code>policy:Ver3_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Whether version 3.0 (must be true)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getlink"></a></p>
<h2id="getlink-rpc-api-get-the-cascade-connection-setting">"GetLink" RPC API - Get the Cascade Connection Setting</h2>
<p>Get the Cascade Connection Setting. Use this to get the Connection Setting of a Cascade Connection that is registered on the currently managed Virtual Hub. To change the Connection Setting contents of the Cascade Connection, use the APIs that include the name "Link" after creating the Cascade Connection. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>The flag to enable validation for the server certificate</td>
</tr>
<tr>
<td><code>ServerCert_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>The body of server X.509 certificate to compare. Valid only if the CheckServerCert_bool flag is true.</td>
</tr>
<tr>
<td><code>AccountName_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Client Option Parameters: Specify the name of the Cascade Connection</td>
</tr>
<tr>
<td><code>Hostname_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: Specify the hostname of the destination VPN Server. You can also specify by IP address.</td>
</tr>
<tr>
<td><code>Port_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Client Option Parameters: Specify the port number of the destination VPN Server.</td>
</tr>
<tr>
<td><code>ProxyType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Client Option Parameters: The type of the proxy server<BR>Values:<BR><code>0</code>: Direct TCP connection<BR><code>1</code>: Connection via HTTP proxy server<BR><code>2</code>: Connection via SOCKS proxy server</td>
</tr>
<tr>
<td><code>ProxyName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The hostname or IP address of the proxy server name</td>
</tr>
<tr>
<td><code>ProxyPort_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Client Option Parameters: The port number of the proxy server</td>
</tr>
<tr>
<td><code>ProxyUsername_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The username to connect to the proxy server</td>
</tr>
<tr>
<td><code>ProxyPassword_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The password to connect to the proxy server</td>
</tr>
<tr>
<td><code>HubName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The Virtual Hub on the destination VPN Server</td>
</tr>
<tr>
<td><code>MaxConnection_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Client Option Parameters: Number of TCP Connections to Use in VPN Communication</td>
</tr>
<tr>
<td><code>UseEncrypt_bool</code></td>
<td><code>boolean</code></td>
<td>Client Option Parameters: The flag to enable the encryption on the communication</td>
</tr>
<tr>
<td><code>UseCompress_bool</code></td>
<td><code>boolean</code></td>
<td>Client Option Parameters: Enable / Disable Data Compression when Communicating by Cascade Connection</td>
</tr>
<tr>
<td><code>HalfConnection_bool</code></td>
<td><code>boolean</code></td>
<td>Client Option Parameters: Specify true when enabling half duplex mode. When using two or more TCP connections for VPN communication, it is possible to use Half Duplex Mode. By enabling half duplex mode it is possible to automatically fix data transmission direction as half and half for each TCP connection. In the case where a VPN using 8 TCP connections is established, for example, when half-duplex is enabled, communication can be fixes so that 4 TCP connections are dedicated to the upload direction and the other 4 connections are dedicated to the download direction.</td>
<td>SHA-0 Hashed password. Valid only if ClientAuth_AuthType_u32 == SHA0_Hashed_Password (1). The SHA-0 hashed password must be caluclated by the SHA0(UpperCase(username_ascii_string) + password_ascii_string).</td>
</tr>
<tr>
<td><code>PlainPassword_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Plaintext Password. Valid only if ClientAuth_AuthType_u32 == PlainPassword (2).</td>
</tr>
<tr>
<td><code>ClientX_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Client certificate. Valid only if ClientAuth_AuthType_u32 == Cert (3).</td>
</tr>
<tr>
<td><code>ClientK_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Client private key of the certificate. Valid only if ClientAuth_AuthType_u32 == Cert (3).</td>
</tr>
<tr>
<td><code>policy:DHCPFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv4). All IPv4 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPNoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv4). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv4 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:DHCPForce_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Enforce DHCP Allocated IP Addresses (IPv4). Computers in sessions that have this policy setting will only be able to use IPv4 addresses allocated by a DHCP server on the virtual network side.</td>
</tr>
<tr>
<td><code>SecPol_CheckMac_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Prohibit the duplicate MAC address</td>
</tr>
<tr>
<td><code>SecPol_CheckIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Prohibit a duplicate IP address (IPv4)</td>
</tr>
<tr>
<td><code>policy:ArpDhcpOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Non-ARP / Non-DHCP / Non-ICMPv6 broadcasts. The sending or receiving of broadcast packets that are not ARP protocol, DHCP protocol, nor ICMPv6 on the virtual network will not be allowed for sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:PrivacyFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Privacy Filter Mode. All direct communication between sessions with the privacy filter mode policy setting will be filtered.</td>
</tr>
<tr>
<td><code>policy:NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv4). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv4.</td>
<td>Security policy: Unlimited Number of Broadcasts. If a computer of a session with this policy setting sends broadcast packets of a number unusually larger than what would be considered normal on the virtual network, there will be no automatic limiting.</td>
</tr>
<tr>
<td><code>policy:MaxMac_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of MAC Addresses. For sessions with this policy setting, this limits the number of MAC addresses per session.</td>
</tr>
<tr>
<td><code>policy:MaxIP_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv4). For sessions with this policy setting, this specifies the number of IPv4 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:MaxUpload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Upload Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the inwards direction from outside to inside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxDownload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Download Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the outwards direction from inside the Virtual Hub to outside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:RSandRAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RS / RA Packets (IPv6). All ICMPv6 packets which the message-type is 133 (Router Solicitation) or 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, an IPv6 client will be unable to use IPv6 address prefix auto detection and IPv6 default gateway auto detection.</td>
</tr>
<tr>
<td><code>SecPol_RAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter the router advertisement packet (IPv6)</td>
</tr>
<tr>
<td><code>policy:DHCPv6Filter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv6). All IPv6 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPv6NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv6). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv6 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>SecPol_CheckIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Prohibit the duplicate IP address (IPv6)</td>
</tr>
<tr>
<td><code>policy:NoServerV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv6). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv6.</td>
</tr>
<tr>
<td><code>policy:MaxIPv6_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv6). For sessions with this policy setting, this specifies the number of IPv6 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:FilterIPv4_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv4 Packets. All IPv4 and ARP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv6 Packets. All IPv6 packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterNonIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All Non-IP Packets. All non-IP packets in sessions defined this policy will be filtered. "Non-IP packet" mean a packet which is not IPv4, ARP nor IPv6. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets.</td>
<td>Security policy: No Default-Router on IPv6 RA. In all VPN Sessions defines this policy, any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
</tr>
<tr>
<td><code>policy:VLanId_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VLAN ID (IEEE802.1Q). You can specify the VLAN ID on the security policy. All VPN Sessions defines this policy, all Ethernet packets toward the Virtual Hub from the user will be inserted a VLAN tag (IEEE 802.1Q) with the VLAN ID. The user can also receive only packets with a VLAN tag which has the same VLAN ID. (Receiving process removes the VLAN tag automatically.) Any Ethernet packets with any other VLAN IDs or non-VLAN packets will not be received. All VPN Sessions without this policy definition can send / receive any kinds of Ethernet packets regardless of VLAN tags, and VLAN tags are not inserted or removed automatically. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets. Therefore, tagged-VLAN packets are not subjects for IPv4 / IPv6 security policies, access lists nor other IPv4 / IPv6 specific deep processing.</td>
</tr>
<tr>
<td><code>policy:Ver3_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Whether version 3.0 (must be true)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="setlink"></a></p>
<h2id="setlink-rpc-api-change-existing-cascade-connection">"SetLink" RPC API - Change Existing Cascade Connection</h2>
<td>The flag to enable validation for the server certificate</td>
</tr>
<tr>
<td><code>ServerCert_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>The body of server X.509 certificate to compare. Valid only if the CheckServerCert_bool flag is true.</td>
</tr>
<tr>
<td><code>AccountName_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Client Option Parameters: Specify the name of the Cascade Connection</td>
</tr>
<tr>
<td><code>Hostname_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: Specify the hostname of the destination VPN Server. You can also specify by IP address.</td>
</tr>
<tr>
<td><code>Port_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Client Option Parameters: Specify the port number of the destination VPN Server.</td>
</tr>
<tr>
<td><code>ProxyType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Client Option Parameters: The type of the proxy server<BR>Values:<BR><code>0</code>: Direct TCP connection<BR><code>1</code>: Connection via HTTP proxy server<BR><code>2</code>: Connection via SOCKS proxy server</td>
</tr>
<tr>
<td><code>ProxyName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The hostname or IP address of the proxy server name</td>
</tr>
<tr>
<td><code>ProxyPort_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Client Option Parameters: The port number of the proxy server</td>
</tr>
<tr>
<td><code>ProxyUsername_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The username to connect to the proxy server</td>
</tr>
<tr>
<td><code>ProxyPassword_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The password to connect to the proxy server</td>
</tr>
<tr>
<td><code>HubName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Client Option Parameters: The Virtual Hub on the destination VPN Server</td>
</tr>
<tr>
<td><code>MaxConnection_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Client Option Parameters: Number of TCP Connections to Use in VPN Communication</td>
</tr>
<tr>
<td><code>UseEncrypt_bool</code></td>
<td><code>boolean</code></td>
<td>Client Option Parameters: The flag to enable the encryption on the communication</td>
</tr>
<tr>
<td><code>UseCompress_bool</code></td>
<td><code>boolean</code></td>
<td>Client Option Parameters: Enable / Disable Data Compression when Communicating by Cascade Connection</td>
</tr>
<tr>
<td><code>HalfConnection_bool</code></td>
<td><code>boolean</code></td>
<td>Client Option Parameters: Specify true when enabling half duplex mode. When using two or more TCP connections for VPN communication, it is possible to use Half Duplex Mode. By enabling half duplex mode it is possible to automatically fix data transmission direction as half and half for each TCP connection. In the case where a VPN using 8 TCP connections is established, for example, when half-duplex is enabled, communication can be fixes so that 4 TCP connections are dedicated to the upload direction and the other 4 connections are dedicated to the download direction.</td>
<td>SHA-0 Hashed password. Valid only if ClientAuth_AuthType_u32 == SHA0_Hashed_Password (1). The SHA-0 hashed password must be caluclated by the SHA0(UpperCase(username_ascii_string) + password_ascii_string).</td>
</tr>
<tr>
<td><code>PlainPassword_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Plaintext Password. Valid only if ClientAuth_AuthType_u32 == PlainPassword (2).</td>
</tr>
<tr>
<td><code>ClientX_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Client certificate. Valid only if ClientAuth_AuthType_u32 == Cert (3).</td>
</tr>
<tr>
<td><code>ClientK_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Client private key of the certificate. Valid only if ClientAuth_AuthType_u32 == Cert (3).</td>
</tr>
<tr>
<td><code>policy:DHCPFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv4). All IPv4 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPNoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv4). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv4 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:DHCPForce_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Enforce DHCP Allocated IP Addresses (IPv4). Computers in sessions that have this policy setting will only be able to use IPv4 addresses allocated by a DHCP server on the virtual network side.</td>
</tr>
<tr>
<td><code>SecPol_CheckMac_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Prohibit the duplicate MAC address</td>
</tr>
<tr>
<td><code>SecPol_CheckIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Prohibit a duplicate IP address (IPv4)</td>
</tr>
<tr>
<td><code>policy:ArpDhcpOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Non-ARP / Non-DHCP / Non-ICMPv6 broadcasts. The sending or receiving of broadcast packets that are not ARP protocol, DHCP protocol, nor ICMPv6 on the virtual network will not be allowed for sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:PrivacyFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Privacy Filter Mode. All direct communication between sessions with the privacy filter mode policy setting will be filtered.</td>
</tr>
<tr>
<td><code>policy:NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv4). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv4.</td>
<td>Security policy: Unlimited Number of Broadcasts. If a computer of a session with this policy setting sends broadcast packets of a number unusually larger than what would be considered normal on the virtual network, there will be no automatic limiting.</td>
</tr>
<tr>
<td><code>policy:MaxMac_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of MAC Addresses. For sessions with this policy setting, this limits the number of MAC addresses per session.</td>
</tr>
<tr>
<td><code>policy:MaxIP_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv4). For sessions with this policy setting, this specifies the number of IPv4 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:MaxUpload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Upload Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the inwards direction from outside to inside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxDownload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Download Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the outwards direction from inside the Virtual Hub to outside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:RSandRAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RS / RA Packets (IPv6). All ICMPv6 packets which the message-type is 133 (Router Solicitation) or 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, an IPv6 client will be unable to use IPv6 address prefix auto detection and IPv6 default gateway auto detection.</td>
</tr>
<tr>
<td><code>SecPol_RAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter the router advertisement packet (IPv6)</td>
</tr>
<tr>
<td><code>policy:DHCPv6Filter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv6). All IPv6 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPv6NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv6). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv6 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>SecPol_CheckIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Prohibit the duplicate IP address (IPv6)</td>
</tr>
<tr>
<td><code>policy:NoServerV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv6). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv6.</td>
</tr>
<tr>
<td><code>policy:MaxIPv6_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv6). For sessions with this policy setting, this specifies the number of IPv6 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:FilterIPv4_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv4 Packets. All IPv4 and ARP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv6 Packets. All IPv6 packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterNonIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All Non-IP Packets. All non-IP packets in sessions defined this policy will be filtered. "Non-IP packet" mean a packet which is not IPv4, ARP nor IPv6. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets.</td>
<td>Security policy: No Default-Router on IPv6 RA. In all VPN Sessions defines this policy, any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
</tr>
<tr>
<td><code>policy:VLanId_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VLAN ID (IEEE802.1Q). You can specify the VLAN ID on the security policy. All VPN Sessions defines this policy, all Ethernet packets toward the Virtual Hub from the user will be inserted a VLAN tag (IEEE 802.1Q) with the VLAN ID. The user can also receive only packets with a VLAN tag which has the same VLAN ID. (Receiving process removes the VLAN tag automatically.) Any Ethernet packets with any other VLAN IDs or non-VLAN packets will not be received. All VPN Sessions without this policy definition can send / receive any kinds of Ethernet packets regardless of VLAN tags, and VLAN tags are not inserted or removed automatically. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets. Therefore, tagged-VLAN packets are not subjects for IPv4 / IPv6 security policies, access lists nor other IPv4 / IPv6 specific deep processing.</td>
</tr>
<tr>
<td><code>policy:Ver3_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Whether version 3.0 (must be true)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="enumlink"></a></p>
<h2id="enumlink-rpc-api-get-list-of-cascade-connections">"EnumLink" RPC API - Get List of Cascade Connections</h2>
<p>Get List of Cascade Connections. Use this to get a list of Cascade Connections that are registered on the currently managed Virtual Hub. By using a Cascade Connection, you can connect this Virtual Hub by Layer 2 Cascade Connection to another Virtual Hub that is operating on the same or a different computer. [Warning About Cascade Connections] By connecting using a Cascade Connection you can create a Layer 2 bridge between multiple Virtual Hubs but if the connection is incorrectly configured, a loopback Cascade Connection could inadvertently be created. When using a Cascade Connection function please design the network topology with care. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>The flag indicates whether the cascade connection is established</td>
</tr>
<tr>
<td><code>LastError_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The error last occurred if the cascade connection is in the fail state</td>
</tr>
<tr>
<td><code>ConnectedTime_dt</code></td>
<td><code>Date</code></td>
<td>Connection completion time</td>
</tr>
<tr>
<td><code>Hostname_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Host name of the destination VPN server</td>
</tr>
<tr>
<td><code>TargetHubName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>The Virtual Hub name</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="setlinkonline"></a></p>
<h2id="setlinkonline-rpc-api-switch-cascade-connection-to-online-status">"SetLinkOnline" RPC API - Switch Cascade Connection to Online Status</h2>
<p>Switch Cascade Connection to Online Status. When a Cascade Connection registered on the currently managed Virtual Hub is specified, use this to switch that Cascade Connection to online status. The Cascade Connection that is switched to online status begins the process of connecting to the destination VPN Server in accordance with the Connection Setting. The Cascade Connection that is switched to online status will establish normal connection to the VPN Server or continue to attempt connection until it is switched to offline status. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<h2id="setlinkoffline-rpc-api-switch-cascade-connection-to-offline-status">"SetLinkOffline" RPC API - Switch Cascade Connection to Offline Status</h2>
<p>Switch Cascade Connection to Offline Status. When a Cascade Connection registered on the currently managed Virtual Hub is specified, use this to switch that Cascade Connection to offline status. The Cascade Connection that is switched to offline will not connect to the VPN Server until next time it is switched to the online status using the SetLinkOnline API You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Delete Cascade Connection Setting. Use this to delete a Cascade Connection that is registered on the currently managed Virtual Hub. If the specified Cascade Connection has a status of online, the connections will be automatically disconnected and then the Cascade Connection will be deleted. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Change Name of Cascade Connection. When a Cascade Connection registered on the currently managed Virtual Hub is specified, use this to change the name of that Cascade Connection. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Get Current Cascade Connection Status. When a Cascade Connection registered on the currently managed Virtual Hub is specified and that Cascade Connection is currently online, use this to get its connection status and other information. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>The flag whether the cascade connection is enabled</td>
</tr>
<tr>
<td><code>Connected_bool</code></td>
<td><code>boolean</code></td>
<td>The flag whether the cascade connection is established</td>
</tr>
<tr>
<td><code>SessionStatus_u32</code></td>
<td><code>number</code> (enum)</td>
<td>The session status<BR>Values:<BR><code>0</code>: Connecting<BR><code>1</code>: Negotiating<BR><code>2</code>: During user authentication<BR><code>3</code>: Connection complete<BR><code>4</code>: Wait to retry<BR><code>5</code>: Idle state</td>
<p>Add Access List Rule. Use this to add a new rule to the access list of the currently managed Virtual Hub. The access list is a set of packet file rules that are applied to packets that flow through the Virtual Hub. You can register multiple rules in an access list and you can also define an priority for each rule. All packets are checked for the conditions specified by the rules registered in the access list and based on the operation that is stipulated by the first matching rule, they either pass or are discarded. Packets that do not match any rule are implicitly allowed to pass. You can also use the access list to generate delays, jitters and packet losses. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<td>Specify a description (note) for this rule</td>
</tr>
<tr>
<td><code>Active_bool</code></td>
<td><code>boolean</code></td>
<td>Enabled flag (true: enabled, false: disabled)</td>
</tr>
<tr>
<td><code>Priority_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Specify an integer of 1 or higher to indicate the priority of the rule. Higher priority is given to rules with the lower priority values.</td>
</tr>
<tr>
<td><code>Discard_bool</code></td>
<td><code>boolean</code></td>
<td>The flag if the rule is DISCARD operation or PASS operation. When a packet matches this rule condition, this operation is decided. When the operation of the rule is PASS, the packet is allowed to pass, otherwise the packet will be discarded.</td>
</tr>
<tr>
<td><code>IsIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>The flag if the rule is for IPv6. Specify false for IPv4, or specify true for IPv6.</td>
</tr>
<tr>
<td><code>SrcIpAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a source IPv4 address as a rule condition. You must also specify the SrcSubnetMask_ip field.</td>
</tr>
<tr>
<td><code>SrcSubnetMask_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a source IPv4 subnet mask as a rule condition. "0.0.0.0" means all hosts. "255.255.255.255" means one single host.</td>
</tr>
<tr>
<td><code>DestIpAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a destination IPv4 address as a rule condition. You must also specify the DestSubnetMask_ip field.</td>
</tr>
<tr>
<td><code>DestSubnetMask_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a destination IPv4 subnet mask as a rule condition. "0.0.0.0" means all hosts. "255.255.255.255" means one single host.</td>
</tr>
<tr>
<td><code>SrcIpAddress6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a source IPv6 address as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 address in binary form. You must also specify the SrcSubnetMask6_bin field.</td>
</tr>
<tr>
<td><code>SrcSubnetMask6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a source IPv6 subnet mask as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 subnet mask in binary form.</td>
</tr>
<tr>
<td><code>DestIpAddress6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a destination IPv6 address as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 address in binary form. You must also specify the DestSubnetMask6_bin field.</td>
</tr>
<tr>
<td><code>DestSubnetMask6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a destination IPv6 subnet mask as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 subnet mask in binary form.</td>
</tr>
<tr>
<td><code>Protocol_u32</code></td>
<td><code>number</code> (enum)</td>
<td>The IP protocol number<BR>Values:<BR><code>1</code>: ICMP for IPv4<BR><code>6</code>: TCP<BR><code>17</code>: UDP<BR><code>58</code>: ICMP for IPv6</td>
</tr>
<tr>
<td><code>SrcPortStart_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The Start Value of the Source Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the source port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>SrcPortEnd_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The End Value of the Source Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the source port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>DestPortStart_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The Start Value of the Destination Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the destination port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>DestPortEnd_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The End Value of the Destination Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the destination port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>SrcUsername_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Source user name. You can apply this rule to only the packets sent by a user session of a user name that has been specified as a rule condition. In this case, specify the user name.</td>
</tr>
<tr>
<td><code>DestUsername_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Destination user name. You can apply this rule to only the packets received by a user session of a user name that has been specified as a rule condition. In this case, specify the user name.</td>
</tr>
<tr>
<td><code>CheckSrcMac_bool</code></td>
<td><code>boolean</code></td>
<td>Specify true if you want to check the source MAC address.</td>
</tr>
<tr>
<td><code>SrcMacAddress_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Source MAC address (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>SrcMacMask_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Source MAC address mask (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>CheckDstMac_bool</code></td>
<td><code>boolean</code></td>
<td>Specify true if you want to check the destination MAC address.</td>
</tr>
<tr>
<td><code>DstMacAddress_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Destination MAC address (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>DstMacMask_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Destination MAC address mask (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>CheckTcpState_bool</code></td>
<td><code>boolean</code></td>
<td>Specify true if you want to check the state of the TCP connection.</td>
</tr>
<tr>
<td><code>Established_bool</code></td>
<td><code>boolean</code></td>
<td>Valid only if CheckTcpState_bool == true. Set this field true to match only TCP-established packets. Set this field false to match only TCP-non established packets.</td>
</tr>
<tr>
<td><code>Delay_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Set this value to generate delays when packets is passing. Specify the delay period in milliseconds. Specify 0 means no delays to generate. The delays must be 10000 milliseconds at most.</td>
</tr>
<tr>
<td><code>Jitter_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Set this value to generate jitters when packets is passing. Specify the ratio of fluctuation of jitters within 0% to 100% range. Specify 0 means no jitters to generate.</td>
</tr>
<tr>
<td><code>Loss_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Set this value to generate packet losses when packets is passing. Specify the ratio of packet losses within 0% to 100% range. Specify 0 means no packet losses to generate.</td>
</tr>
<tr>
<td><code>RedirectUrl_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>The specified URL will be mandatory replied to the client as a response for TCP connecting request packets which matches the conditions of this access list entry via this Virtual Hub. To use this setting, you can enforce the web browser of the VPN Client computer to show the specified web site when that web browser tries to access the specific IP address.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="deleteaccess"></a></p>
<h2id="deleteaccess-rpc-api-delete-rule-from-access-list">"DeleteAccess" RPC API - Delete Rule from Access List</h2>
<p>Delete Rule from Access List. Use this to specify a packet filter rule registered on the access list of the currently managed Virtual Hub and delete it. To delete a rule, you must specify that rule's ID. You can display the ID by using the EnumAccess API. If you wish not to delete the rule but to only temporarily disable it, use the SetAccessList API to set the rule status to disable. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<p>Get Access List Rule List. Use this to get a list of packet filter rules that are registered on access list of the currently managed Virtual Hub. The access list is a set of packet file rules that are applied to packets that flow through the Virtual Hub. You can register multiple rules in an access list and you can also define a priority for each rule. All packets are checked for the conditions specified by the rules registered in the access list and based on the operation that is stipulated by the first matching rule, they either pass or are discarded. Packets that do not match any rule are implicitly allowed to pass. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<td>Specify a description (note) for this rule</td>
</tr>
<tr>
<td><code>Active_bool</code></td>
<td><code>boolean</code></td>
<td>Enabled flag (true: enabled, false: disabled)</td>
</tr>
<tr>
<td><code>Priority_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Specify an integer of 1 or higher to indicate the priority of the rule. Higher priority is given to rules with the lower priority values.</td>
</tr>
<tr>
<td><code>Discard_bool</code></td>
<td><code>boolean</code></td>
<td>The flag if the rule is DISCARD operation or PASS operation. When a packet matches this rule condition, this operation is decided. When the operation of the rule is PASS, the packet is allowed to pass, otherwise the packet will be discarded.</td>
</tr>
<tr>
<td><code>IsIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>The flag if the rule is for IPv6. Specify false for IPv4, or specify true for IPv6.</td>
</tr>
<tr>
<td><code>SrcIpAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a source IPv4 address as a rule condition. You must also specify the SrcSubnetMask_ip field.</td>
</tr>
<tr>
<td><code>SrcSubnetMask_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a source IPv4 subnet mask as a rule condition. "0.0.0.0" means all hosts. "255.255.255.255" means one single host.</td>
</tr>
<tr>
<td><code>DestIpAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a destination IPv4 address as a rule condition. You must also specify the DestSubnetMask_ip field.</td>
</tr>
<tr>
<td><code>DestSubnetMask_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a destination IPv4 subnet mask as a rule condition. "0.0.0.0" means all hosts. "255.255.255.255" means one single host.</td>
</tr>
<tr>
<td><code>SrcIpAddress6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a source IPv6 address as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 address in binary form. You must also specify the SrcSubnetMask6_bin field.</td>
</tr>
<tr>
<td><code>SrcSubnetMask6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a source IPv6 subnet mask as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 subnet mask in binary form.</td>
</tr>
<tr>
<td><code>DestIpAddress6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a destination IPv6 address as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 address in binary form. You must also specify the DestSubnetMask6_bin field.</td>
</tr>
<tr>
<td><code>DestSubnetMask6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a destination IPv6 subnet mask as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 subnet mask in binary form.</td>
</tr>
<tr>
<td><code>Protocol_u32</code></td>
<td><code>number</code> (enum)</td>
<td>The IP protocol number<BR>Values:<BR><code>1</code>: ICMP for IPv4<BR><code>6</code>: TCP<BR><code>17</code>: UDP<BR><code>58</code>: ICMP for IPv6</td>
</tr>
<tr>
<td><code>SrcPortStart_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The Start Value of the Source Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the source port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>SrcPortEnd_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The End Value of the Source Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the source port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>DestPortStart_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The Start Value of the Destination Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the destination port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>DestPortEnd_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The End Value of the Destination Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the destination port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>SrcUsername_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Source user name. You can apply this rule to only the packets sent by a user session of a user name that has been specified as a rule condition. In this case, specify the user name.</td>
</tr>
<tr>
<td><code>DestUsername_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Destination user name. You can apply this rule to only the packets received by a user session of a user name that has been specified as a rule condition. In this case, specify the user name.</td>
</tr>
<tr>
<td><code>CheckSrcMac_bool</code></td>
<td><code>boolean</code></td>
<td>Specify true if you want to check the source MAC address.</td>
</tr>
<tr>
<td><code>SrcMacAddress_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Source MAC address (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>SrcMacMask_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Source MAC address mask (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>CheckDstMac_bool</code></td>
<td><code>boolean</code></td>
<td>Specify true if you want to check the destination MAC address.</td>
</tr>
<tr>
<td><code>DstMacAddress_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Destination MAC address (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>DstMacMask_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Destination MAC address mask (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>CheckTcpState_bool</code></td>
<td><code>boolean</code></td>
<td>Specify true if you want to check the state of the TCP connection.</td>
</tr>
<tr>
<td><code>Established_bool</code></td>
<td><code>boolean</code></td>
<td>Valid only if CheckTcpState_bool == true. Set this field true to match only TCP-established packets. Set this field false to match only TCP-non established packets.</td>
</tr>
<tr>
<td><code>Delay_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Set this value to generate delays when packets is passing. Specify the delay period in milliseconds. Specify 0 means no delays to generate. The delays must be 10000 milliseconds at most.</td>
</tr>
<tr>
<td><code>Jitter_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Set this value to generate jitters when packets is passing. Specify the ratio of fluctuation of jitters within 0% to 100% range. Specify 0 means no jitters to generate.</td>
</tr>
<tr>
<td><code>Loss_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Set this value to generate packet losses when packets is passing. Specify the ratio of packet losses within 0% to 100% range. Specify 0 means no packet losses to generate.</td>
</tr>
<tr>
<td><code>RedirectUrl_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>The specified URL will be mandatory replied to the client as a response for TCP connecting request packets which matches the conditions of this access list entry via this Virtual Hub. To use this setting, you can enforce the web browser of the VPN Client computer to show the specified web site when that web browser tries to access the specific IP address.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="setaccesslist"></a></p>
<h2id="setaccesslist-rpc-api-replace-all-access-lists-on-a-single-bulk-api-call">"SetAccessList" RPC API - Replace all access lists on a single bulk API call</h2>
<p>Replace all access lists on a single bulk API call. This API removes all existing access list rules on the Virtual Hub, and replace them by new access list rules specified by the parameter.</p>
<td>Specify a description (note) for this rule</td>
</tr>
<tr>
<td><code>Active_bool</code></td>
<td><code>boolean</code></td>
<td>Enabled flag (true: enabled, false: disabled)</td>
</tr>
<tr>
<td><code>Priority_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Specify an integer of 1 or higher to indicate the priority of the rule. Higher priority is given to rules with the lower priority values.</td>
</tr>
<tr>
<td><code>Discard_bool</code></td>
<td><code>boolean</code></td>
<td>The flag if the rule is DISCARD operation or PASS operation. When a packet matches this rule condition, this operation is decided. When the operation of the rule is PASS, the packet is allowed to pass, otherwise the packet will be discarded.</td>
</tr>
<tr>
<td><code>IsIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>The flag if the rule is for IPv6. Specify false for IPv4, or specify true for IPv6.</td>
</tr>
<tr>
<td><code>SrcIpAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a source IPv4 address as a rule condition. You must also specify the SrcSubnetMask_ip field.</td>
</tr>
<tr>
<td><code>SrcSubnetMask_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a source IPv4 subnet mask as a rule condition. "0.0.0.0" means all hosts. "255.255.255.255" means one single host.</td>
</tr>
<tr>
<td><code>DestIpAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a destination IPv4 address as a rule condition. You must also specify the DestSubnetMask_ip field.</td>
</tr>
<tr>
<td><code>DestSubnetMask_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Valid only if the rule is IPv4 mode (IsIPv6_bool == false). Specify a destination IPv4 subnet mask as a rule condition. "0.0.0.0" means all hosts. "255.255.255.255" means one single host.</td>
</tr>
<tr>
<td><code>SrcIpAddress6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a source IPv6 address as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 address in binary form. You must also specify the SrcSubnetMask6_bin field.</td>
</tr>
<tr>
<td><code>SrcSubnetMask6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a source IPv6 subnet mask as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 subnet mask in binary form.</td>
</tr>
<tr>
<td><code>DestIpAddress6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a destination IPv6 address as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 address in binary form. You must also specify the DestSubnetMask6_bin field.</td>
</tr>
<tr>
<td><code>DestSubnetMask6_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Valid only if the rule is IPv6 mode (IsIPv6_bool == true). Specify a destination IPv6 subnet mask as a rule condition. The field must be a byte array of 16 bytes (128 bits) to contain the IPv6 subnet mask in binary form.</td>
</tr>
<tr>
<td><code>Protocol_u32</code></td>
<td><code>number</code> (enum)</td>
<td>The IP protocol number<BR>Values:<BR><code>1</code>: ICMP for IPv4<BR><code>6</code>: TCP<BR><code>17</code>: UDP<BR><code>58</code>: ICMP for IPv6</td>
</tr>
<tr>
<td><code>SrcPortStart_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The Start Value of the Source Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the source port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>SrcPortEnd_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The End Value of the Source Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the source port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>DestPortStart_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The Start Value of the Destination Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the destination port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>DestPortEnd_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>The End Value of the Destination Port Number Range. If the specified protocol is TCP/IP or UDP/IP, specify the destination port number as the rule condition. Protocols other than this will be ignored. When this parameter is not specified, the rules will apply to all port numbers.</td>
</tr>
<tr>
<td><code>SrcUsername_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Source user name. You can apply this rule to only the packets sent by a user session of a user name that has been specified as a rule condition. In this case, specify the user name.</td>
</tr>
<tr>
<td><code>DestUsername_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Destination user name. You can apply this rule to only the packets received by a user session of a user name that has been specified as a rule condition. In this case, specify the user name.</td>
</tr>
<tr>
<td><code>CheckSrcMac_bool</code></td>
<td><code>boolean</code></td>
<td>Specify true if you want to check the source MAC address.</td>
</tr>
<tr>
<td><code>SrcMacAddress_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Source MAC address (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>SrcMacMask_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Source MAC address mask (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>CheckDstMac_bool</code></td>
<td><code>boolean</code></td>
<td>Specify true if you want to check the destination MAC address.</td>
</tr>
<tr>
<td><code>DstMacAddress_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Destination MAC address (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>DstMacMask_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Destination MAC address mask (6 bytes), valid only if CheckSrcMac_bool == true.</td>
</tr>
<tr>
<td><code>CheckTcpState_bool</code></td>
<td><code>boolean</code></td>
<td>Specify true if you want to check the state of the TCP connection.</td>
</tr>
<tr>
<td><code>Established_bool</code></td>
<td><code>boolean</code></td>
<td>Valid only if CheckTcpState_bool == true. Set this field true to match only TCP-established packets. Set this field false to match only TCP-non established packets.</td>
</tr>
<tr>
<td><code>Delay_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Set this value to generate delays when packets is passing. Specify the delay period in milliseconds. Specify 0 means no delays to generate. The delays must be 10000 milliseconds at most.</td>
</tr>
<tr>
<td><code>Jitter_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Set this value to generate jitters when packets is passing. Specify the ratio of fluctuation of jitters within 0% to 100% range. Specify 0 means no jitters to generate.</td>
</tr>
<tr>
<td><code>Loss_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Set this value to generate packet losses when packets is passing. Specify the ratio of packet losses within 0% to 100% range. Specify 0 means no packet losses to generate.</td>
</tr>
<tr>
<td><code>RedirectUrl_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>The specified URL will be mandatory replied to the client as a response for TCP connecting request packets which matches the conditions of this access list entry via this Virtual Hub. To use this setting, you can enforce the web browser of the VPN Client computer to show the specified web site when that web browser tries to access the specific IP address.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="createuser"></a></p>
<h2id="createuser-rpc-api-create-a-user">"CreateUser" RPC API - Create a user</h2>
<p>Create a user. Use this to create a new user in the security account database of the currently managed Virtual Hub. By creating a user, the VPN Client can connect to the Virtual Hub by using the authentication information of that user. Note that a user whose user name has been created as "<em>" (a single asterisk character) will automatically be registered as a RADIUS authentication user. For cases where there are users with "</em>" as the name, when a user, whose user name that has been provided when a client connected to a VPN Server does not match existing user names, is able to be authenticated by a RADIUS server or NT domain controller by inputting a user name and password, the authentication settings and security policy settings will follow the setting for the user "*". To change the user information of a user that has been created, use the SetUser API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<td>Optional real name (full name) of the user, allow using any Unicode characters</td>
</tr>
<tr>
<td><code>Note_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Optional User Description</td>
</tr>
<tr>
<td><code>CreatedTime_dt</code></td>
<td><code>Date</code></td>
<td>Creation date and time</td>
</tr>
<tr>
<td><code>UpdatedTime_dt</code></td>
<td><code>Date</code></td>
<td>Last modified date and time</td>
</tr>
<tr>
<td><code>ExpireTime_dt</code></td>
<td><code>Date</code></td>
<td>Expiration date and time</td>
</tr>
<tr>
<td><code>AuthType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Authentication method of the user<BR>Values:<BR><code>0</code>: Anonymous authentication<BR><code>1</code>: Password authentication<BR><code>2</code>: User certificate authentication<BR><code>3</code>: Root certificate which is issued by trusted Certificate Authority<BR><code>4</code>: Radius authentication<BR><code>5</code>: Windows NT authentication</td>
</tr>
<tr>
<td><code>Auth_Password_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>User password, valid only if AuthType_u32 == Password(1). Valid only to create or set operations.</td>
</tr>
<tr>
<td><code>UserX_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>User certificate, valid only if AuthType_u32 == UserCert(2).</td>
</tr>
<tr>
<td><code>Serial_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Certificate Serial Number, optional, valid only if AuthType_u32 == RootCert(3).</td>
</tr>
<tr>
<td><code>CommonName_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Certificate Common Name, optional, valid only if AuthType_u32 == RootCert(3).</td>
</tr>
<tr>
<td><code>RadiusUsername_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Username in RADIUS server, optional, valid only if AuthType_u32 == Radius(4).</td>
</tr>
<tr>
<td><code>NtUsername_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Username in NT Domain server, optional, valid only if AuthType_u32 == NT(5).</td>
<td>Security policy: Allow Access. The users, which this policy value is true, have permission to make VPN connection to VPN Server.</td>
</tr>
<tr>
<td><code>policy:DHCPFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv4). All IPv4 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPNoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv4). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv4 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:DHCPForce_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Enforce DHCP Allocated IP Addresses (IPv4). Computers in sessions that have this policy setting will only be able to use IPv4 addresses allocated by a DHCP server on the virtual network side.</td>
</tr>
<tr>
<td><code>policy:NoBridge_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Bridge Operation. Bridge-mode connections are denied for user sessions that have this policy setting. Even in cases when the Ethernet Bridge is configured in the client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:NoRouting_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv4). IPv4 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckMac_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny MAC Addresses Duplication. The use of duplicating MAC addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:CheckIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv4). The use of duplicating IPv4 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:ArpDhcpOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Non-ARP / Non-DHCP / Non-ICMPv6 broadcasts. The sending or receiving of broadcast packets that are not ARP protocol, DHCP protocol, nor ICMPv6 on the virtual network will not be allowed for sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:PrivacyFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Privacy Filter Mode. All direct communication between sessions with the privacy filter mode policy setting will be filtered.</td>
</tr>
<tr>
<td><code>policy:NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv4). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv4.</td>
<td>Security policy: Unlimited Number of Broadcasts. If a computer of a session with this policy setting sends broadcast packets of a number unusually larger than what would be considered normal on the virtual network, there will be no automatic limiting.</td>
</tr>
<tr>
<td><code>policy:MonitorPort_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Allow Monitoring Mode. Users with this policy setting will be granted to connect to the Virtual Hub in Monitoring Mode. Sessions in Monitoring Mode are able to monitor (tap) all packets flowing through the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxConnection_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of TCP Connections. For sessions with this policy setting, this sets the maximum number of physical TCP connections consists in a physical VPN session.</td>
</tr>
<tr>
<td><code>policy:TimeOut_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Time-out Period. For sessions with this policy setting, this sets, in seconds, the time-out period to wait before disconnecting a session when communication trouble occurs between the VPN Client / VPN Server.</td>
</tr>
<tr>
<td><code>policy:MaxMac_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of MAC Addresses. For sessions with this policy setting, this limits the number of MAC addresses per session.</td>
</tr>
<tr>
<td><code>policy:MaxIP_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv4). For sessions with this policy setting, this specifies the number of IPv4 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:MaxUpload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Upload Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the inwards direction from outside to inside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxDownload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Download Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the outwards direction from inside the Virtual Hub to outside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:FixPassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Changing Password. The users which use password authentication with this policy setting are not allowed to change their own password from the VPN Client Manager or similar.</td>
</tr>
<tr>
<td><code>policy:MultiLogins_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of Multiple Logins. Users with this policy setting are unable to have more than this number of concurrent logins. Bridge Mode sessions are not subjects to this policy.</td>
</tr>
<tr>
<td><code>policy:NoQoS_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny VoIP / QoS Function. Users with this security policy are unable to use VoIP / QoS functions in VPN connection sessions.</td>
</tr>
<tr>
<td><code>policy:RSandRAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RS / RA Packets (IPv6). All ICMPv6 packets which the message-type is 133 (Router Solicitation) or 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, an IPv6 client will be unable to use IPv6 address prefix auto detection and IPv6 default gateway auto detection.</td>
</tr>
<tr>
<td><code>policy:RAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RA Packets (IPv6). All ICMPv6 packets which the message-type is 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, a malicious users will be unable to spread illegal IPv6 prefix or default gateway advertisements on the network.</td>
</tr>
<tr>
<td><code>policy:DHCPv6Filter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv6). All IPv6 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPv6NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv6). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv6 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:NoRoutingV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv6). IPv6 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv6). The use of duplicating IPv6 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:NoServerV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv6). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv6.</td>
</tr>
<tr>
<td><code>policy:MaxIPv6_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv6). For sessions with this policy setting, this specifies the number of IPv6 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:NoSavePassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow Password Save in VPN Client. For users with this policy setting, when the user is using <em>standard</em> password authentication, the user will be unable to save the password in VPN Client. The user will be required to input passwords for every time to connect a VPN. This will improve the security. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:AutoDisconnect_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VPN Client Automatic Disconnect. For users with this policy setting, a user's VPN session will be disconnected automatically after the specific period will elapse. In this case no automatic re-connection will be performed. This can prevent a lot of inactive VPN Sessions. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:FilterIPv4_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv4 Packets. All IPv4 and ARP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv6 Packets. All IPv6 packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterNonIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All Non-IP Packets. All non-IP packets in sessions defined this policy will be filtered. "Non-IP packet" mean a packet which is not IPv4, ARP nor IPv6. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets.</td>
<td>Security policy: No Default-Router on IPv6 RA. In all VPN Sessions defines this policy, any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
<td>Security policy: No Default-Router on IPv6 RA (physical IPv6). In all VPN Sessions defines this policy (only when the physical communication protocol between VPN Client / VPN Bridge and VPN Server is IPv6), any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
</tr>
<tr>
<td><code>policy:VLanId_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VLAN ID (IEEE802.1Q). You can specify the VLAN ID on the security policy. All VPN Sessions defines this policy, all Ethernet packets toward the Virtual Hub from the user will be inserted a VLAN tag (IEEE 802.1Q) with the VLAN ID. The user can also receive only packets with a VLAN tag which has the same VLAN ID. (Receiving process removes the VLAN tag automatically.) Any Ethernet packets with any other VLAN IDs or non-VLAN packets will not be received. All VPN Sessions without this policy definition can send / receive any kinds of Ethernet packets regardless of VLAN tags, and VLAN tags are not inserted or removed automatically. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets. Therefore, tagged-VLAN packets are not subjects for IPv4 / IPv6 security policies, access lists nor other IPv4 / IPv6 specific deep processing.</td>
</tr>
<tr>
<td><code>policy:Ver3_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Whether version 3.0 (must be true)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="setuser"></a></p>
<h2id="setuser-rpc-api-change-user-settings">"SetUser" RPC API - Change User Settings</h2>
<p>Change User Settings. Use this to change user settings that is registered on the security account database of the currently managed Virtual Hub. The user settings that can be changed using this API are the three items that are specified when a new user is created using the CreateUser API: Group Name, Full Name, and Description. To get the list of currently registered users, use the EnumUser API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<td>Optional real name (full name) of the user, allow using any Unicode characters</td>
</tr>
<tr>
<td><code>Note_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Optional User Description</td>
</tr>
<tr>
<td><code>CreatedTime_dt</code></td>
<td><code>Date</code></td>
<td>Creation date and time</td>
</tr>
<tr>
<td><code>UpdatedTime_dt</code></td>
<td><code>Date</code></td>
<td>Last modified date and time</td>
</tr>
<tr>
<td><code>ExpireTime_dt</code></td>
<td><code>Date</code></td>
<td>Expiration date and time</td>
</tr>
<tr>
<td><code>AuthType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Authentication method of the user<BR>Values:<BR><code>0</code>: Anonymous authentication<BR><code>1</code>: Password authentication<BR><code>2</code>: User certificate authentication<BR><code>3</code>: Root certificate which is issued by trusted Certificate Authority<BR><code>4</code>: Radius authentication<BR><code>5</code>: Windows NT authentication</td>
</tr>
<tr>
<td><code>Auth_Password_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>User password, valid only if AuthType_u32 == Password(1). Valid only to create or set operations.</td>
</tr>
<tr>
<td><code>UserX_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>User certificate, valid only if AuthType_u32 == UserCert(2).</td>
</tr>
<tr>
<td><code>Serial_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Certificate Serial Number, optional, valid only if AuthType_u32 == RootCert(3).</td>
</tr>
<tr>
<td><code>CommonName_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Certificate Common Name, optional, valid only if AuthType_u32 == RootCert(3).</td>
</tr>
<tr>
<td><code>RadiusUsername_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Username in RADIUS server, optional, valid only if AuthType_u32 == Radius(4).</td>
</tr>
<tr>
<td><code>NtUsername_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Username in NT Domain server, optional, valid only if AuthType_u32 == NT(5).</td>
<td>Security policy: Allow Access. The users, which this policy value is true, have permission to make VPN connection to VPN Server.</td>
</tr>
<tr>
<td><code>policy:DHCPFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv4). All IPv4 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPNoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv4). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv4 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:DHCPForce_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Enforce DHCP Allocated IP Addresses (IPv4). Computers in sessions that have this policy setting will only be able to use IPv4 addresses allocated by a DHCP server on the virtual network side.</td>
</tr>
<tr>
<td><code>policy:NoBridge_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Bridge Operation. Bridge-mode connections are denied for user sessions that have this policy setting. Even in cases when the Ethernet Bridge is configured in the client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:NoRouting_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv4). IPv4 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckMac_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny MAC Addresses Duplication. The use of duplicating MAC addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:CheckIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv4). The use of duplicating IPv4 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:ArpDhcpOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Non-ARP / Non-DHCP / Non-ICMPv6 broadcasts. The sending or receiving of broadcast packets that are not ARP protocol, DHCP protocol, nor ICMPv6 on the virtual network will not be allowed for sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:PrivacyFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Privacy Filter Mode. All direct communication between sessions with the privacy filter mode policy setting will be filtered.</td>
</tr>
<tr>
<td><code>policy:NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv4). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv4.</td>
<td>Security policy: Unlimited Number of Broadcasts. If a computer of a session with this policy setting sends broadcast packets of a number unusually larger than what would be considered normal on the virtual network, there will be no automatic limiting.</td>
</tr>
<tr>
<td><code>policy:MonitorPort_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Allow Monitoring Mode. Users with this policy setting will be granted to connect to the Virtual Hub in Monitoring Mode. Sessions in Monitoring Mode are able to monitor (tap) all packets flowing through the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxConnection_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of TCP Connections. For sessions with this policy setting, this sets the maximum number of physical TCP connections consists in a physical VPN session.</td>
</tr>
<tr>
<td><code>policy:TimeOut_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Time-out Period. For sessions with this policy setting, this sets, in seconds, the time-out period to wait before disconnecting a session when communication trouble occurs between the VPN Client / VPN Server.</td>
</tr>
<tr>
<td><code>policy:MaxMac_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of MAC Addresses. For sessions with this policy setting, this limits the number of MAC addresses per session.</td>
</tr>
<tr>
<td><code>policy:MaxIP_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv4). For sessions with this policy setting, this specifies the number of IPv4 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:MaxUpload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Upload Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the inwards direction from outside to inside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxDownload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Download Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the outwards direction from inside the Virtual Hub to outside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:FixPassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Changing Password. The users which use password authentication with this policy setting are not allowed to change their own password from the VPN Client Manager or similar.</td>
</tr>
<tr>
<td><code>policy:MultiLogins_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of Multiple Logins. Users with this policy setting are unable to have more than this number of concurrent logins. Bridge Mode sessions are not subjects to this policy.</td>
</tr>
<tr>
<td><code>policy:NoQoS_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny VoIP / QoS Function. Users with this security policy are unable to use VoIP / QoS functions in VPN connection sessions.</td>
</tr>
<tr>
<td><code>policy:RSandRAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RS / RA Packets (IPv6). All ICMPv6 packets which the message-type is 133 (Router Solicitation) or 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, an IPv6 client will be unable to use IPv6 address prefix auto detection and IPv6 default gateway auto detection.</td>
</tr>
<tr>
<td><code>policy:RAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RA Packets (IPv6). All ICMPv6 packets which the message-type is 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, a malicious users will be unable to spread illegal IPv6 prefix or default gateway advertisements on the network.</td>
</tr>
<tr>
<td><code>policy:DHCPv6Filter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv6). All IPv6 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPv6NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv6). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv6 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:NoRoutingV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv6). IPv6 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv6). The use of duplicating IPv6 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:NoServerV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv6). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv6.</td>
</tr>
<tr>
<td><code>policy:MaxIPv6_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv6). For sessions with this policy setting, this specifies the number of IPv6 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:NoSavePassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow Password Save in VPN Client. For users with this policy setting, when the user is using <em>standard</em> password authentication, the user will be unable to save the password in VPN Client. The user will be required to input passwords for every time to connect a VPN. This will improve the security. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:AutoDisconnect_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VPN Client Automatic Disconnect. For users with this policy setting, a user's VPN session will be disconnected automatically after the specific period will elapse. In this case no automatic re-connection will be performed. This can prevent a lot of inactive VPN Sessions. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:FilterIPv4_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv4 Packets. All IPv4 and ARP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv6 Packets. All IPv6 packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterNonIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All Non-IP Packets. All non-IP packets in sessions defined this policy will be filtered. "Non-IP packet" mean a packet which is not IPv4, ARP nor IPv6. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets.</td>
<td>Security policy: No Default-Router on IPv6 RA. In all VPN Sessions defines this policy, any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
<td>Security policy: No Default-Router on IPv6 RA (physical IPv6). In all VPN Sessions defines this policy (only when the physical communication protocol between VPN Client / VPN Bridge and VPN Server is IPv6), any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
</tr>
<tr>
<td><code>policy:VLanId_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VLAN ID (IEEE802.1Q). You can specify the VLAN ID on the security policy. All VPN Sessions defines this policy, all Ethernet packets toward the Virtual Hub from the user will be inserted a VLAN tag (IEEE 802.1Q) with the VLAN ID. The user can also receive only packets with a VLAN tag which has the same VLAN ID. (Receiving process removes the VLAN tag automatically.) Any Ethernet packets with any other VLAN IDs or non-VLAN packets will not be received. All VPN Sessions without this policy definition can send / receive any kinds of Ethernet packets regardless of VLAN tags, and VLAN tags are not inserted or removed automatically. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets. Therefore, tagged-VLAN packets are not subjects for IPv4 / IPv6 security policies, access lists nor other IPv4 / IPv6 specific deep processing.</td>
</tr>
<tr>
<td><code>policy:Ver3_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Whether version 3.0 (must be true)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getuser"></a></p>
<h2id="getuser-rpc-api-get-user-settings">"GetUser" RPC API - Get User Settings</h2>
<p>Get User Settings. Use this to get user settings information that is registered on the security account database of the currently managed Virtual Hub. The information that you can get using this API are User Name, Full Name, Group Name, Expiration Date, Security Policy, and Auth Type, as well as parameters that are specified as auth type attributes and the statistical data of that user. To get the list of currently registered users, use the EnumUser API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<td>Optional real name (full name) of the user, allow using any Unicode characters</td>
</tr>
<tr>
<td><code>Note_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Optional User Description</td>
</tr>
<tr>
<td><code>CreatedTime_dt</code></td>
<td><code>Date</code></td>
<td>Creation date and time</td>
</tr>
<tr>
<td><code>UpdatedTime_dt</code></td>
<td><code>Date</code></td>
<td>Last modified date and time</td>
</tr>
<tr>
<td><code>ExpireTime_dt</code></td>
<td><code>Date</code></td>
<td>Expiration date and time</td>
</tr>
<tr>
<td><code>AuthType_u32</code></td>
<td><code>number</code> (enum)</td>
<td>Authentication method of the user<BR>Values:<BR><code>0</code>: Anonymous authentication<BR><code>1</code>: Password authentication<BR><code>2</code>: User certificate authentication<BR><code>3</code>: Root certificate which is issued by trusted Certificate Authority<BR><code>4</code>: Radius authentication<BR><code>5</code>: Windows NT authentication</td>
</tr>
<tr>
<td><code>Auth_Password_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>User password, valid only if AuthType_u32 == Password(1). Valid only to create or set operations.</td>
</tr>
<tr>
<td><code>UserX_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>User certificate, valid only if AuthType_u32 == UserCert(2).</td>
</tr>
<tr>
<td><code>Serial_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Certificate Serial Number, optional, valid only if AuthType_u32 == RootCert(3).</td>
</tr>
<tr>
<td><code>CommonName_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Certificate Common Name, optional, valid only if AuthType_u32 == RootCert(3).</td>
</tr>
<tr>
<td><code>RadiusUsername_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Username in RADIUS server, optional, valid only if AuthType_u32 == Radius(4).</td>
</tr>
<tr>
<td><code>NtUsername_utf</code></td>
<td><code>string</code> (UTF8)</td>
<td>Username in NT Domain server, optional, valid only if AuthType_u32 == NT(5).</td>
<td>Security policy: Allow Access. The users, which this policy value is true, have permission to make VPN connection to VPN Server.</td>
</tr>
<tr>
<td><code>policy:DHCPFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv4). All IPv4 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPNoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv4). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv4 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:DHCPForce_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Enforce DHCP Allocated IP Addresses (IPv4). Computers in sessions that have this policy setting will only be able to use IPv4 addresses allocated by a DHCP server on the virtual network side.</td>
</tr>
<tr>
<td><code>policy:NoBridge_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Bridge Operation. Bridge-mode connections are denied for user sessions that have this policy setting. Even in cases when the Ethernet Bridge is configured in the client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:NoRouting_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv4). IPv4 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckMac_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny MAC Addresses Duplication. The use of duplicating MAC addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:CheckIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv4). The use of duplicating IPv4 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:ArpDhcpOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Non-ARP / Non-DHCP / Non-ICMPv6 broadcasts. The sending or receiving of broadcast packets that are not ARP protocol, DHCP protocol, nor ICMPv6 on the virtual network will not be allowed for sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:PrivacyFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Privacy Filter Mode. All direct communication between sessions with the privacy filter mode policy setting will be filtered.</td>
</tr>
<tr>
<td><code>policy:NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv4). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv4.</td>
<td>Security policy: Unlimited Number of Broadcasts. If a computer of a session with this policy setting sends broadcast packets of a number unusually larger than what would be considered normal on the virtual network, there will be no automatic limiting.</td>
</tr>
<tr>
<td><code>policy:MonitorPort_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Allow Monitoring Mode. Users with this policy setting will be granted to connect to the Virtual Hub in Monitoring Mode. Sessions in Monitoring Mode are able to monitor (tap) all packets flowing through the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxConnection_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of TCP Connections. For sessions with this policy setting, this sets the maximum number of physical TCP connections consists in a physical VPN session.</td>
</tr>
<tr>
<td><code>policy:TimeOut_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Time-out Period. For sessions with this policy setting, this sets, in seconds, the time-out period to wait before disconnecting a session when communication trouble occurs between the VPN Client / VPN Server.</td>
</tr>
<tr>
<td><code>policy:MaxMac_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of MAC Addresses. For sessions with this policy setting, this limits the number of MAC addresses per session.</td>
</tr>
<tr>
<td><code>policy:MaxIP_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv4). For sessions with this policy setting, this specifies the number of IPv4 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:MaxUpload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Upload Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the inwards direction from outside to inside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxDownload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Download Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the outwards direction from inside the Virtual Hub to outside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:FixPassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Changing Password. The users which use password authentication with this policy setting are not allowed to change their own password from the VPN Client Manager or similar.</td>
</tr>
<tr>
<td><code>policy:MultiLogins_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of Multiple Logins. Users with this policy setting are unable to have more than this number of concurrent logins. Bridge Mode sessions are not subjects to this policy.</td>
</tr>
<tr>
<td><code>policy:NoQoS_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny VoIP / QoS Function. Users with this security policy are unable to use VoIP / QoS functions in VPN connection sessions.</td>
</tr>
<tr>
<td><code>policy:RSandRAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RS / RA Packets (IPv6). All ICMPv6 packets which the message-type is 133 (Router Solicitation) or 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, an IPv6 client will be unable to use IPv6 address prefix auto detection and IPv6 default gateway auto detection.</td>
</tr>
<tr>
<td><code>policy:RAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RA Packets (IPv6). All ICMPv6 packets which the message-type is 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, a malicious users will be unable to spread illegal IPv6 prefix or default gateway advertisements on the network.</td>
</tr>
<tr>
<td><code>policy:DHCPv6Filter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv6). All IPv6 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPv6NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv6). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv6 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:NoRoutingV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv6). IPv6 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv6). The use of duplicating IPv6 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:NoServerV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv6). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv6.</td>
</tr>
<tr>
<td><code>policy:MaxIPv6_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv6). For sessions with this policy setting, this specifies the number of IPv6 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:NoSavePassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow Password Save in VPN Client. For users with this policy setting, when the user is using <em>standard</em> password authentication, the user will be unable to save the password in VPN Client. The user will be required to input passwords for every time to connect a VPN. This will improve the security. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:AutoDisconnect_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VPN Client Automatic Disconnect. For users with this policy setting, a user's VPN session will be disconnected automatically after the specific period will elapse. In this case no automatic re-connection will be performed. This can prevent a lot of inactive VPN Sessions. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:FilterIPv4_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv4 Packets. All IPv4 and ARP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv6 Packets. All IPv6 packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterNonIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All Non-IP Packets. All non-IP packets in sessions defined this policy will be filtered. "Non-IP packet" mean a packet which is not IPv4, ARP nor IPv6. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets.</td>
<td>Security policy: No Default-Router on IPv6 RA. In all VPN Sessions defines this policy, any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
<td>Security policy: No Default-Router on IPv6 RA (physical IPv6). In all VPN Sessions defines this policy (only when the physical communication protocol between VPN Client / VPN Bridge and VPN Server is IPv6), any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
</tr>
<tr>
<td><code>policy:VLanId_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VLAN ID (IEEE802.1Q). You can specify the VLAN ID on the security policy. All VPN Sessions defines this policy, all Ethernet packets toward the Virtual Hub from the user will be inserted a VLAN tag (IEEE 802.1Q) with the VLAN ID. The user can also receive only packets with a VLAN tag which has the same VLAN ID. (Receiving process removes the VLAN tag automatically.) Any Ethernet packets with any other VLAN IDs or non-VLAN packets will not be received. All VPN Sessions without this policy definition can send / receive any kinds of Ethernet packets regardless of VLAN tags, and VLAN tags are not inserted or removed automatically. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets. Therefore, tagged-VLAN packets are not subjects for IPv4 / IPv6 security policies, access lists nor other IPv4 / IPv6 specific deep processing.</td>
</tr>
<tr>
<td><code>policy:Ver3_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Whether version 3.0 (must be true)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="deleteuser"></a></p>
<h2id="deleteuser-rpc-api-delete-a-user">"DeleteUser" RPC API - Delete a user</h2>
<p>Delete a user. Use this to delete a user that is registered on the security account database of the currently managed Virtual Hub. By deleting the user, that user will no long be able to connect to the Virtual Hub. You can use the SetUser API to set the user's security policy to deny access instead of deleting a user, set the user to be temporarily denied from logging in. To get the list of currently registered users, use the EnumUser API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<p>Get List of Users. Use this to get a list of users that are registered on the security account database of the currently managed Virtual Hub. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<td>Authentication method<BR>Values:<BR><code>0</code>: Anonymous authentication<BR><code>1</code>: Password authentication<BR><code>2</code>: User certificate authentication<BR><code>3</code>: Root certificate which is issued by trusted Certificate Authority<BR><code>4</code>: Radius authentication<BR><code>5</code>: Windows NT authentication</td>
</tr>
<tr>
<td><code>NumLogin_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Number of logins</td>
</tr>
<tr>
<td><code>LastLoginTime_dt</code></td>
<td><code>Date</code></td>
<td>Last login date and time</td>
</tr>
<tr>
<td><code>DenyAccess_bool</code></td>
<td><code>boolean</code></td>
<td>Access denied</td>
</tr>
<tr>
<td><code>IsTrafficFilled_bool</code></td>
<td><code>boolean</code></td>
<td>Flag of whether the traffic variable is set</td>
</tr>
<tr>
<td><code>IsExpiresFilled_bool</code></td>
<td><code>boolean</code></td>
<td>Flag of whether expiration date variable is set</td>
</tr>
<tr>
<td><code>Expires_dt</code></td>
<td><code>Date</code></td>
<td>Expiration date</td>
</tr>
<tr>
<td><code>Ex.Recv.BroadcastBytes_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Number of broadcast packets (Recv)</td>
</tr>
<tr>
<td><code>Ex.Recv.BroadcastCount_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Broadcast bytes (Recv)</td>
</tr>
<tr>
<td><code>Ex.Recv.UnicastBytes_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Unicast count (Recv)</td>
</tr>
<tr>
<td><code>Ex.Recv.UnicastCount_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Unicast bytes (Recv)</td>
</tr>
<tr>
<td><code>Ex.Send.BroadcastBytes_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Number of broadcast packets (Send)</td>
</tr>
<tr>
<td><code>Ex.Send.BroadcastCount_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Broadcast bytes (Send)</td>
</tr>
<tr>
<td><code>Ex.Send.UnicastBytes_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Unicast bytes (Send)</td>
</tr>
<tr>
<td><code>Ex.Send.UnicastCount_u64</code></td>
<td><code>number</code> (uint64)</td>
<td>Unicast bytes (Send)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="creategroup"></a></p>
<h2id="creategroup-rpc-api-create-group">"CreateGroup" RPC API - Create Group</h2>
<p>Create Group. Use this to create a new group in the security account database of the currently managed Virtual Hub. You can register multiple users in a group. To register users in a group use the SetUser API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<td>Security policy: Allow Access. The users, which this policy value is true, have permission to make VPN connection to VPN Server.</td>
</tr>
<tr>
<td><code>policy:DHCPFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv4). All IPv4 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPNoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv4). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv4 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:DHCPForce_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Enforce DHCP Allocated IP Addresses (IPv4). Computers in sessions that have this policy setting will only be able to use IPv4 addresses allocated by a DHCP server on the virtual network side.</td>
</tr>
<tr>
<td><code>policy:NoBridge_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Bridge Operation. Bridge-mode connections are denied for user sessions that have this policy setting. Even in cases when the Ethernet Bridge is configured in the client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:NoRouting_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv4). IPv4 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckMac_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny MAC Addresses Duplication. The use of duplicating MAC addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:CheckIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv4). The use of duplicating IPv4 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:ArpDhcpOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Non-ARP / Non-DHCP / Non-ICMPv6 broadcasts. The sending or receiving of broadcast packets that are not ARP protocol, DHCP protocol, nor ICMPv6 on the virtual network will not be allowed for sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:PrivacyFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Privacy Filter Mode. All direct communication between sessions with the privacy filter mode policy setting will be filtered.</td>
</tr>
<tr>
<td><code>policy:NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv4). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv4.</td>
<td>Security policy: Unlimited Number of Broadcasts. If a computer of a session with this policy setting sends broadcast packets of a number unusually larger than what would be considered normal on the virtual network, there will be no automatic limiting.</td>
</tr>
<tr>
<td><code>policy:MonitorPort_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Allow Monitoring Mode. Users with this policy setting will be granted to connect to the Virtual Hub in Monitoring Mode. Sessions in Monitoring Mode are able to monitor (tap) all packets flowing through the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxConnection_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of TCP Connections. For sessions with this policy setting, this sets the maximum number of physical TCP connections consists in a physical VPN session.</td>
</tr>
<tr>
<td><code>policy:TimeOut_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Time-out Period. For sessions with this policy setting, this sets, in seconds, the time-out period to wait before disconnecting a session when communication trouble occurs between the VPN Client / VPN Server.</td>
</tr>
<tr>
<td><code>policy:MaxMac_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of MAC Addresses. For sessions with this policy setting, this limits the number of MAC addresses per session.</td>
</tr>
<tr>
<td><code>policy:MaxIP_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv4). For sessions with this policy setting, this specifies the number of IPv4 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:MaxUpload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Upload Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the inwards direction from outside to inside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxDownload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Download Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the outwards direction from inside the Virtual Hub to outside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:FixPassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Changing Password. The users which use password authentication with this policy setting are not allowed to change their own password from the VPN Client Manager or similar.</td>
</tr>
<tr>
<td><code>policy:MultiLogins_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of Multiple Logins. Users with this policy setting are unable to have more than this number of concurrent logins. Bridge Mode sessions are not subjects to this policy.</td>
</tr>
<tr>
<td><code>policy:NoQoS_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny VoIP / QoS Function. Users with this security policy are unable to use VoIP / QoS functions in VPN connection sessions.</td>
</tr>
<tr>
<td><code>policy:RSandRAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RS / RA Packets (IPv6). All ICMPv6 packets which the message-type is 133 (Router Solicitation) or 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, an IPv6 client will be unable to use IPv6 address prefix auto detection and IPv6 default gateway auto detection.</td>
</tr>
<tr>
<td><code>policy:RAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RA Packets (IPv6). All ICMPv6 packets which the message-type is 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, a malicious users will be unable to spread illegal IPv6 prefix or default gateway advertisements on the network.</td>
</tr>
<tr>
<td><code>policy:DHCPv6Filter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv6). All IPv6 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPv6NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv6). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv6 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:NoRoutingV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv6). IPv6 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv6). The use of duplicating IPv6 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:NoServerV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv6). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv6.</td>
</tr>
<tr>
<td><code>policy:MaxIPv6_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv6). For sessions with this policy setting, this specifies the number of IPv6 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:NoSavePassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow Password Save in VPN Client. For users with this policy setting, when the user is using <em>standard</em> password authentication, the user will be unable to save the password in VPN Client. The user will be required to input passwords for every time to connect a VPN. This will improve the security. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:AutoDisconnect_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VPN Client Automatic Disconnect. For users with this policy setting, a user's VPN session will be disconnected automatically after the specific period will elapse. In this case no automatic re-connection will be performed. This can prevent a lot of inactive VPN Sessions. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:FilterIPv4_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv4 Packets. All IPv4 and ARP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv6 Packets. All IPv6 packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterNonIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All Non-IP Packets. All non-IP packets in sessions defined this policy will be filtered. "Non-IP packet" mean a packet which is not IPv4, ARP nor IPv6. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets.</td>
<td>Security policy: No Default-Router on IPv6 RA. In all VPN Sessions defines this policy, any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
<td>Security policy: No Default-Router on IPv6 RA (physical IPv6). In all VPN Sessions defines this policy (only when the physical communication protocol between VPN Client / VPN Bridge and VPN Server is IPv6), any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
</tr>
<tr>
<td><code>policy:VLanId_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VLAN ID (IEEE802.1Q). You can specify the VLAN ID on the security policy. All VPN Sessions defines this policy, all Ethernet packets toward the Virtual Hub from the user will be inserted a VLAN tag (IEEE 802.1Q) with the VLAN ID. The user can also receive only packets with a VLAN tag which has the same VLAN ID. (Receiving process removes the VLAN tag automatically.) Any Ethernet packets with any other VLAN IDs or non-VLAN packets will not be received. All VPN Sessions without this policy definition can send / receive any kinds of Ethernet packets regardless of VLAN tags, and VLAN tags are not inserted or removed automatically. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets. Therefore, tagged-VLAN packets are not subjects for IPv4 / IPv6 security policies, access lists nor other IPv4 / IPv6 specific deep processing.</td>
</tr>
<tr>
<td><code>policy:Ver3_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Whether version 3.0 (must be true)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="setgroup"></a></p>
<h2id="setgroup-rpc-api-set-group-settings">"SetGroup" RPC API - Set group settings</h2>
<p>Set group settings. Use this to set group settings that is registered on the security account database of the currently managed Virtual Hub. To get the list of currently registered groups, use the EnumGroup API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<td>Security policy: Allow Access. The users, which this policy value is true, have permission to make VPN connection to VPN Server.</td>
</tr>
<tr>
<td><code>policy:DHCPFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv4). All IPv4 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPNoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv4). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv4 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:DHCPForce_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Enforce DHCP Allocated IP Addresses (IPv4). Computers in sessions that have this policy setting will only be able to use IPv4 addresses allocated by a DHCP server on the virtual network side.</td>
</tr>
<tr>
<td><code>policy:NoBridge_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Bridge Operation. Bridge-mode connections are denied for user sessions that have this policy setting. Even in cases when the Ethernet Bridge is configured in the client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:NoRouting_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv4). IPv4 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckMac_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny MAC Addresses Duplication. The use of duplicating MAC addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:CheckIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv4). The use of duplicating IPv4 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:ArpDhcpOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Non-ARP / Non-DHCP / Non-ICMPv6 broadcasts. The sending or receiving of broadcast packets that are not ARP protocol, DHCP protocol, nor ICMPv6 on the virtual network will not be allowed for sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:PrivacyFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Privacy Filter Mode. All direct communication between sessions with the privacy filter mode policy setting will be filtered.</td>
</tr>
<tr>
<td><code>policy:NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv4). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv4.</td>
<td>Security policy: Unlimited Number of Broadcasts. If a computer of a session with this policy setting sends broadcast packets of a number unusually larger than what would be considered normal on the virtual network, there will be no automatic limiting.</td>
</tr>
<tr>
<td><code>policy:MonitorPort_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Allow Monitoring Mode. Users with this policy setting will be granted to connect to the Virtual Hub in Monitoring Mode. Sessions in Monitoring Mode are able to monitor (tap) all packets flowing through the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxConnection_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of TCP Connections. For sessions with this policy setting, this sets the maximum number of physical TCP connections consists in a physical VPN session.</td>
</tr>
<tr>
<td><code>policy:TimeOut_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Time-out Period. For sessions with this policy setting, this sets, in seconds, the time-out period to wait before disconnecting a session when communication trouble occurs between the VPN Client / VPN Server.</td>
</tr>
<tr>
<td><code>policy:MaxMac_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of MAC Addresses. For sessions with this policy setting, this limits the number of MAC addresses per session.</td>
</tr>
<tr>
<td><code>policy:MaxIP_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv4). For sessions with this policy setting, this specifies the number of IPv4 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:MaxUpload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Upload Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the inwards direction from outside to inside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxDownload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Download Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the outwards direction from inside the Virtual Hub to outside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:FixPassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Changing Password. The users which use password authentication with this policy setting are not allowed to change their own password from the VPN Client Manager or similar.</td>
</tr>
<tr>
<td><code>policy:MultiLogins_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of Multiple Logins. Users with this policy setting are unable to have more than this number of concurrent logins. Bridge Mode sessions are not subjects to this policy.</td>
</tr>
<tr>
<td><code>policy:NoQoS_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny VoIP / QoS Function. Users with this security policy are unable to use VoIP / QoS functions in VPN connection sessions.</td>
</tr>
<tr>
<td><code>policy:RSandRAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RS / RA Packets (IPv6). All ICMPv6 packets which the message-type is 133 (Router Solicitation) or 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, an IPv6 client will be unable to use IPv6 address prefix auto detection and IPv6 default gateway auto detection.</td>
</tr>
<tr>
<td><code>policy:RAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RA Packets (IPv6). All ICMPv6 packets which the message-type is 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, a malicious users will be unable to spread illegal IPv6 prefix or default gateway advertisements on the network.</td>
</tr>
<tr>
<td><code>policy:DHCPv6Filter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv6). All IPv6 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPv6NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv6). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv6 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:NoRoutingV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv6). IPv6 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv6). The use of duplicating IPv6 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:NoServerV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv6). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv6.</td>
</tr>
<tr>
<td><code>policy:MaxIPv6_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv6). For sessions with this policy setting, this specifies the number of IPv6 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:NoSavePassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow Password Save in VPN Client. For users with this policy setting, when the user is using <em>standard</em> password authentication, the user will be unable to save the password in VPN Client. The user will be required to input passwords for every time to connect a VPN. This will improve the security. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:AutoDisconnect_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VPN Client Automatic Disconnect. For users with this policy setting, a user's VPN session will be disconnected automatically after the specific period will elapse. In this case no automatic re-connection will be performed. This can prevent a lot of inactive VPN Sessions. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:FilterIPv4_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv4 Packets. All IPv4 and ARP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv6 Packets. All IPv6 packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterNonIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All Non-IP Packets. All non-IP packets in sessions defined this policy will be filtered. "Non-IP packet" mean a packet which is not IPv4, ARP nor IPv6. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets.</td>
<td>Security policy: No Default-Router on IPv6 RA. In all VPN Sessions defines this policy, any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
<td>Security policy: No Default-Router on IPv6 RA (physical IPv6). In all VPN Sessions defines this policy (only when the physical communication protocol between VPN Client / VPN Bridge and VPN Server is IPv6), any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
</tr>
<tr>
<td><code>policy:VLanId_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VLAN ID (IEEE802.1Q). You can specify the VLAN ID on the security policy. All VPN Sessions defines this policy, all Ethernet packets toward the Virtual Hub from the user will be inserted a VLAN tag (IEEE 802.1Q) with the VLAN ID. The user can also receive only packets with a VLAN tag which has the same VLAN ID. (Receiving process removes the VLAN tag automatically.) Any Ethernet packets with any other VLAN IDs or non-VLAN packets will not be received. All VPN Sessions without this policy definition can send / receive any kinds of Ethernet packets regardless of VLAN tags, and VLAN tags are not inserted or removed automatically. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets. Therefore, tagged-VLAN packets are not subjects for IPv4 / IPv6 security policies, access lists nor other IPv4 / IPv6 specific deep processing.</td>
</tr>
<tr>
<td><code>policy:Ver3_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Whether version 3.0 (must be true)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getgroup"></a></p>
<h2id="getgroup-rpc-api-get-group-setting-sync-mode">"GetGroup" RPC API - Get Group Setting (Sync mode)</h2>
<p>Get Group Setting (Sync mode). Use this to get the setting of a group that is registered on the security account database of the currently managed Virtual Hub. To get the list of currently registered groups, use the EnumGroup API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<td>Security policy: Allow Access. The users, which this policy value is true, have permission to make VPN connection to VPN Server.</td>
</tr>
<tr>
<td><code>policy:DHCPFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv4). All IPv4 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPNoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv4). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv4 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:DHCPForce_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Enforce DHCP Allocated IP Addresses (IPv4). Computers in sessions that have this policy setting will only be able to use IPv4 addresses allocated by a DHCP server on the virtual network side.</td>
</tr>
<tr>
<td><code>policy:NoBridge_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Bridge Operation. Bridge-mode connections are denied for user sessions that have this policy setting. Even in cases when the Ethernet Bridge is configured in the client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:NoRouting_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv4). IPv4 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckMac_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny MAC Addresses Duplication. The use of duplicating MAC addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:CheckIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv4). The use of duplicating IPv4 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:ArpDhcpOnly_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Non-ARP / Non-DHCP / Non-ICMPv6 broadcasts. The sending or receiving of broadcast packets that are not ARP protocol, DHCP protocol, nor ICMPv6 on the virtual network will not be allowed for sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:PrivacyFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Privacy Filter Mode. All direct communication between sessions with the privacy filter mode policy setting will be filtered.</td>
</tr>
<tr>
<td><code>policy:NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv4). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv4.</td>
<td>Security policy: Unlimited Number of Broadcasts. If a computer of a session with this policy setting sends broadcast packets of a number unusually larger than what would be considered normal on the virtual network, there will be no automatic limiting.</td>
</tr>
<tr>
<td><code>policy:MonitorPort_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Allow Monitoring Mode. Users with this policy setting will be granted to connect to the Virtual Hub in Monitoring Mode. Sessions in Monitoring Mode are able to monitor (tap) all packets flowing through the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxConnection_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of TCP Connections. For sessions with this policy setting, this sets the maximum number of physical TCP connections consists in a physical VPN session.</td>
</tr>
<tr>
<td><code>policy:TimeOut_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Time-out Period. For sessions with this policy setting, this sets, in seconds, the time-out period to wait before disconnecting a session when communication trouble occurs between the VPN Client / VPN Server.</td>
</tr>
<tr>
<td><code>policy:MaxMac_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of MAC Addresses. For sessions with this policy setting, this limits the number of MAC addresses per session.</td>
</tr>
<tr>
<td><code>policy:MaxIP_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv4). For sessions with this policy setting, this specifies the number of IPv4 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:MaxUpload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Upload Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the inwards direction from outside to inside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:MaxDownload_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Download Bandwidth. For sessions with this policy setting, this limits the traffic bandwidth that is in the outwards direction from inside the Virtual Hub to outside the Virtual Hub.</td>
</tr>
<tr>
<td><code>policy:FixPassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Changing Password. The users which use password authentication with this policy setting are not allowed to change their own password from the VPN Client Manager or similar.</td>
</tr>
<tr>
<td><code>policy:MultiLogins_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of Multiple Logins. Users with this policy setting are unable to have more than this number of concurrent logins. Bridge Mode sessions are not subjects to this policy.</td>
</tr>
<tr>
<td><code>policy:NoQoS_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny VoIP / QoS Function. Users with this security policy are unable to use VoIP / QoS functions in VPN connection sessions.</td>
</tr>
<tr>
<td><code>policy:RSandRAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RS / RA Packets (IPv6). All ICMPv6 packets which the message-type is 133 (Router Solicitation) or 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, an IPv6 client will be unable to use IPv6 address prefix auto detection and IPv6 default gateway auto detection.</td>
</tr>
<tr>
<td><code>policy:RAFilter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter RA Packets (IPv6). All ICMPv6 packets which the message-type is 134 (Router Advertisement) in sessions defined this policy will be filtered. As a result, a malicious users will be unable to spread illegal IPv6 prefix or default gateway advertisements on the network.</td>
</tr>
<tr>
<td><code>policy:DHCPv6Filter_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter DHCP Packets (IPv6). All IPv6 DHCP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:DHCPv6NoServer_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow DHCP Server Operation (IPv6). Computers connected to sessions that have this policy setting will not be allowed to become a DHCP server and distribute IPv6 addresses to DHCP clients.</td>
</tr>
<tr>
<td><code>policy:NoRoutingV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Routing Operation (IPv6). IPv6 routing will be denied for sessions that have this policy setting. Even in the case where the IP router is operating on the user client side, communication will not be possible.</td>
</tr>
<tr>
<td><code>policy:CheckIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny IP Address Duplication (IPv6). The use of duplicating IPv6 addresses that are in use by computers of different sessions cannot be used by sessions with this policy setting.</td>
</tr>
<tr>
<td><code>policy:NoServerV6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Deny Operation as TCP/IP Server (IPv6). Computers of sessions with this policy setting can't listen and accept TCP/IP connections in IPv6.</td>
</tr>
<tr>
<td><code>policy:MaxIPv6_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: Maximum Number of IP Addresses (IPv6). For sessions with this policy setting, this specifies the number of IPv6 addresses that can be registered for a single session.</td>
</tr>
<tr>
<td><code>policy:NoSavePassword_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Disallow Password Save in VPN Client. For users with this policy setting, when the user is using <em>standard</em> password authentication, the user will be unable to save the password in VPN Client. The user will be required to input passwords for every time to connect a VPN. This will improve the security. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:AutoDisconnect_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VPN Client Automatic Disconnect. For users with this policy setting, a user's VPN session will be disconnected automatically after the specific period will elapse. In this case no automatic re-connection will be performed. This can prevent a lot of inactive VPN Sessions. If this policy is enabled, VPN Client Version 2.0 will be denied to access.</td>
</tr>
<tr>
<td><code>policy:FilterIPv4_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv4 Packets. All IPv4 and ARP packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterIPv6_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All IPv6 Packets. All IPv6 packets in sessions defined this policy will be filtered.</td>
</tr>
<tr>
<td><code>policy:FilterNonIP_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Filter All Non-IP Packets. All non-IP packets in sessions defined this policy will be filtered. "Non-IP packet" mean a packet which is not IPv4, ARP nor IPv6. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets.</td>
<td>Security policy: No Default-Router on IPv6 RA. In all VPN Sessions defines this policy, any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
<td>Security policy: No Default-Router on IPv6 RA (physical IPv6). In all VPN Sessions defines this policy (only when the physical communication protocol between VPN Client / VPN Bridge and VPN Server is IPv6), any IPv6 RA (Router Advertisement) packet with non-zero value in the router-lifetime will set to zero-value. This is effective to avoid the horrible behavior from the IPv6 routing confusion which is caused by the VPN client's attempts to use the remote-side IPv6 router as its local IPv6 router.</td>
</tr>
<tr>
<td><code>policy:VLanId_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Security policy: VLAN ID (IEEE802.1Q). You can specify the VLAN ID on the security policy. All VPN Sessions defines this policy, all Ethernet packets toward the Virtual Hub from the user will be inserted a VLAN tag (IEEE 802.1Q) with the VLAN ID. The user can also receive only packets with a VLAN tag which has the same VLAN ID. (Receiving process removes the VLAN tag automatically.) Any Ethernet packets with any other VLAN IDs or non-VLAN packets will not be received. All VPN Sessions without this policy definition can send / receive any kinds of Ethernet packets regardless of VLAN tags, and VLAN tags are not inserted or removed automatically. Any tagged-VLAN packets via the Virtual Hub will be regarded as non-IP packets. Therefore, tagged-VLAN packets are not subjects for IPv4 / IPv6 security policies, access lists nor other IPv4 / IPv6 specific deep processing.</td>
</tr>
<tr>
<td><code>policy:Ver3_bool</code></td>
<td><code>boolean</code></td>
<td>Security policy: Whether version 3.0 (must be true)</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="deletegroup"></a></p>
<h2id="deletegroup-rpc-api-delete-user-from-group">"DeleteGroup" RPC API - Delete User from Group</h2>
<p>Delete User from Group. Use this to delete a specified user from the group that is registered on the security account database of the currently managed Virtual Hub. By deleting a user from the group, that user becomes unassigned. To get the list of currently registered groups, use the EnumGroup API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<p>Get List of Groups. Use this to get a list of groups that are registered on the security account database of the currently managed Virtual Hub. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a member server on a cluster.</p>
<p>Get List of Connected VPN Sessions. Use this to get a list of the sessions connected to the Virtual Hub currently being managed. In the list of sessions, the following information will be obtained for each connection: Session Name, Session Site, User Name, Source Host Name, TCP Connection, Transfer Bytes and Transfer Packets. If the currently connected VPN Server is a cluster controller and the currently managed Virtual Hub is a static Virtual Hub, you can get an all-linked-together list of all sessions connected to that Virtual Hub on all cluster members. In all other cases, only the list of sessions that are actually connected to the currently managed VPN Server will be obtained.</p>
<p>Get Session Status. Use this to specify a session currently connected to the currently managed Virtual Hub and get the session information. The session status includes the following: source host name and user name, version information, time information, number of TCP connections, communication parameters, session key, statistical information on data transferred, and other client and server information. To get the list of currently connected sessions, use the EnumSession API.</p>
<td>State of the client session<BR>Values:<BR><code>0</code>: Connecting<BR><code>1</code>: Negotiating<BR><code>2</code>: During user authentication<BR><code>3</code>: Connection complete<BR><code>4</code>: Wait to retry<BR><code>5</code>: Idle state</td>
<p>Disconnect Session. Use this to specify a session currently connected to the currently managed Virtual Hub and forcefully disconnect that session using manager privileges. Note that when communication is disconnected by settings on the source client side and the automatically reconnect option is enabled, it is possible that the client will reconnect. To get the list of currently connected sessions, use the EnumSession API.</p>
<p>Get the MAC Address Table Database. Use this to get the MAC address table database that is held by the currently managed Virtual Hub. The MAC address table database is a table that the Virtual Hub requires to perform the action of switching Ethernet frames and the Virtual Hub decides the sorting destination session of each Ethernet frame based on the MAC address table database. The MAC address database is built by the Virtual Hub automatically analyzing the contents of the communication.</p>
<p>Delete MAC Address Table Entry. Use this API to operate the MAC address table database held by the currently managed Virtual Hub and delete a specified MAC address table entry from the database. To get the contents of the current MAC address table database use the EnumMacTable API.</p>
<p>Get the IP Address Table Database. Use this to get the IP address table database that is held by the currently managed Virtual Hub. The IP address table database is a table that is automatically generated by analyzing the contents of communication so that the Virtual Hub can always know which session is using which IP address and it is frequently used by the engine that applies the Virtual Hub security policy. By specifying the session name you can get the IP address table entry that has been associated with that session.</p>
<p>Delete IP Address Table Entry. Use this API to operate the IP address table database held by the currently managed Virtual Hub and delete a specified IP address table entry from the database. To get the contents of the current IP address table database use the EnumIpTable API.</p>
<h2id="setkeep-rpc-api-set-the-keep-alive-internet-connection-function">"SetKeep" RPC API - Set the Keep Alive Internet Connection Function</h2>
<p>Set the Keep Alive Internet Connection Function. Use this to set the destination host name etc. of the Keep Alive Internet Connection Function. For network connection environments where connections will automatically be disconnected where there are periods of no communication that are longer than a set period, by using the Keep Alive Internet Connection Function, it is possible to keep alive the Internet connection by sending packets to a nominated server on the Internet at set intervals. When using this API, you can specify the following: Host Name, Port Number, Packet Send Interval, and Protocol. Packets sent to keep alive the Internet connection will have random content and personal information that could identify a computer or user is not sent. You can use the SetKeep API to enable/disable the Keep Alive Internet Connection Function. To execute this API on a VPN Server or VPN Bridge, you must have administrator privileges.</p>
<h2id="getkeep-rpc-api-get-the-keep-alive-internet-connection-function">"GetKeep" RPC API - Get the Keep Alive Internet Connection Function</h2>
<p>Get the Keep Alive Internet Connection Function. Use this to get the current setting contents of the Keep Alive Internet Connection Function. In addition to the destination's Host Name, Port Number, Packet Send Interval and Protocol, you can obtain the current enabled/disabled status of the Keep Alive Internet Connection Function.</p>
<h2id="enablesecurenat-rpc-api-enable-the-virtual-nat-and-dhcp-server-function-securenat-function">"EnableSecureNAT" RPC API - Enable the Virtual NAT and DHCP Server Function (SecureNAT Function)</h2>
<p>Enable the Virtual NAT and DHCP Server Function (SecureNAT Function). Use this to enable the Virtual NAT and DHCP Server function (SecureNAT Function) on the currently managed Virtual Hub and begin its operation. Before executing this API, you must first check the setting contents of the current Virtual NAT function and DHCP Server function using the SetSecureNATOption API and GetSecureNATOption API. By enabling the SecureNAT function, you can virtually operate a NAT router (IP masquerade) and the DHCP Server function on a virtual network on the Virtual Hub. [Warning about SecureNAT Function] The SecureNAT function is recommended only for system administrators and people with a detailed knowledge of networks. If you use the SecureNAT function correctly, it is possible to achieve a safe form of remote access via a VPN. However when used in the wrong way, it can put the entire network in danger. Anyone who does not have a thorough knowledge of networks and anyone who does not have the network administrator's permission must not enable the SecureNAT function. For a detailed explanation of the SecureNAT function, please refer to the VPN Server's manual and online documentation. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<h2id="disablesecurenat-rpc-api-disable-the-virtual-nat-and-dhcp-server-function-securenat-function">"DisableSecureNAT" RPC API - Disable the Virtual NAT and DHCP Server Function (SecureNAT Function)</h2>
<p>Disable the Virtual NAT and DHCP Server Function (SecureNAT Function). Use this to disable the Virtual NAT and DHCP Server function (SecureNAT Function) on the currently managed Virtual Hub. By executing this API the Virtual NAT function immediately stops operating and the Virtual DHCP Server function deletes the DHCP lease database and stops the service. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<h2id="setsecurenatoption-rpc-api-change-settings-of-securenat-function">"SetSecureNATOption" RPC API - Change Settings of SecureNAT Function</h2>
<p>Change Settings of SecureNAT Function. Use this to change and save the virtual host network interface settings, virtual NAT function settings and virtual DHCP server settings of the Virtual NAT and DHCP Server function (SecureNAT function) on the currently managed Virtual Hub. The SecureNAT function holds one virtual network adapter on the L2 segment inside the Virtual Hub and it has been assigned a MAC address and an IP address. By doing this, another host connected to the same L2 segment is able to communicate with the SecureNAT virtual host as if it is an actual IP host existing on the network. [Warning about SecureNAT Function] The SecureNAT function is recommended only for system administrators and people with a detailed knowledge of networks. If you use the SecureNAT function correctly, it is possible to achieve a safe form of remote access via a VPN. However when used in the wrong way, it can put the entire network in danger. Anyone who does not have a thorough knowledge of networks and anyone who does not have the network administrators permission must not enable the SecureNAT function. For a detailed explanation of the SecureNAT function, please refer to the VPN Server's manual and online documentation. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Specify the start point of the address band to be distributed to the client. (Example: 192.168.30.10)</td>
</tr>
<tr>
<td><code>DhcpLeaseIPEnd_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Specify the end point of the address band to be distributed to the client. (Example: 192.168.30.200)</td>
</tr>
<tr>
<td><code>DhcpSubnetMask_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Specify the subnet mask to be specified for the client. (Example: 255.255.255.0)</td>
</tr>
<tr>
<td><code>DhcpExpireTimeSpan_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Specify the expiration date in second units for leasing an IP address to a client.</td>
</tr>
<tr>
<td><code>DhcpGatewayAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Specify the IP address of the default gateway to be notified to the client. You can specify a SecureNAT Virtual Host IP address for this when the SecureNAT Function's Virtual NAT Function has been enabled and is being used also. If you specify 0 or none, then the client will not be notified of the default gateway.</td>
</tr>
<tr>
<td><code>DhcpDnsServerAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Specify the IP address of the primary DNS Server to be notified to the client. You can specify a SecureNAT Virtual Host IP address for this when the SecureNAT Function's Virtual NAT Function has been enabled and is being used also. If you specify empty, then the client will not be notified of the DNS Server address.</td>
</tr>
<tr>
<td><code>DhcpDnsServerAddress2_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Specify the IP address of the secondary DNS Server to be notified to the client. You can specify a SecureNAT Virtual Host IP address for this when the SecureNAT Function's Virtual NAT Function has been enabled and is being used also. If you specify empty, then the client will not be notified of the DNS Server address.</td>
</tr>
<tr>
<td><code>DhcpDomainName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the domain name to be notified to the client. If you specify none, then the client will not be notified of the domain name.</td>
</tr>
<tr>
<td><code>SaveLog_bool</code></td>
<td><code>boolean</code></td>
<td>Specify whether or not to save the Virtual DHCP Server operation in the Virtual Hub security log. Specify true to save it. This value is interlinked with the Virtual NAT Function log save setting.</td>
</tr>
<tr>
<td><code>ApplyDhcpPushRoutes_bool</code></td>
<td><code>boolean</code></td>
<td>The flag to enable the DhcpPushRoutes_str field.</td>
</tr>
<tr>
<td><code>DhcpPushRoutes_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the static routing table to push. Example: "192.168.5.0/255.255.255.0/192.168.4.254, 10.0.0.0/255.0.0.0/192.168.4.253" Split multiple entries (maximum: 64 entries) by comma or space characters. Each entry must be specified in the "IP network address/subnet mask/gateway IP address" format. This Virtual DHCP Server can push the classless static routes (RFC 3442) with DHCP reply messages to VPN clients. Whether or not a VPN client can recognize the classless static routes (RFC 3442) depends on the target VPN client software. SoftEther VPN Client and OpenVPN Client are supporting the classless static routes. On L2TP/IPsec and MS-SSTP protocols, the compatibility depends on the implementation of the client software. You can realize the split tunneling if you clear the default gateway field on the Virtual DHCP Server options. On the client side, L2TP/IPsec and MS-SSTP clients need to be configured not to set up the default gateway for the split tunneling usage. You can also push the classless static routes (RFC 3442) by your existing external DHCP server. In that case, disable the Virtual DHCP Server function on SecureNAT, and you need not to set up the classless routes on this API. See the RFC 3442 to understand the classless routes.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getsecurenatoption"></a></p>
<h2id="getsecurenatoption-rpc-api-get-settings-of-securenat-function">"GetSecureNATOption" RPC API - Get Settings of SecureNAT Function</h2>
<td>Specify the start point of the address band to be distributed to the client. (Example: 192.168.30.10)</td>
</tr>
<tr>
<td><code>DhcpLeaseIPEnd_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Specify the end point of the address band to be distributed to the client. (Example: 192.168.30.200)</td>
</tr>
<tr>
<td><code>DhcpSubnetMask_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Specify the subnet mask to be specified for the client. (Example: 255.255.255.0)</td>
</tr>
<tr>
<td><code>DhcpExpireTimeSpan_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Specify the expiration date in second units for leasing an IP address to a client.</td>
</tr>
<tr>
<td><code>DhcpGatewayAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Specify the IP address of the default gateway to be notified to the client. You can specify a SecureNAT Virtual Host IP address for this when the SecureNAT Function's Virtual NAT Function has been enabled and is being used also. If you specify 0 or none, then the client will not be notified of the default gateway.</td>
</tr>
<tr>
<td><code>DhcpDnsServerAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Specify the IP address of the primary DNS Server to be notified to the client. You can specify a SecureNAT Virtual Host IP address for this when the SecureNAT Function's Virtual NAT Function has been enabled and is being used also. If you specify empty, then the client will not be notified of the DNS Server address.</td>
</tr>
<tr>
<td><code>DhcpDnsServerAddress2_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Specify the IP address of the secondary DNS Server to be notified to the client. You can specify a SecureNAT Virtual Host IP address for this when the SecureNAT Function's Virtual NAT Function has been enabled and is being used also. If you specify empty, then the client will not be notified of the DNS Server address.</td>
</tr>
<tr>
<td><code>DhcpDomainName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the domain name to be notified to the client. If you specify none, then the client will not be notified of the domain name.</td>
</tr>
<tr>
<td><code>SaveLog_bool</code></td>
<td><code>boolean</code></td>
<td>Specify whether or not to save the Virtual DHCP Server operation in the Virtual Hub security log. Specify true to save it. This value is interlinked with the Virtual NAT Function log save setting.</td>
</tr>
<tr>
<td><code>ApplyDhcpPushRoutes_bool</code></td>
<td><code>boolean</code></td>
<td>The flag to enable the DhcpPushRoutes_str field.</td>
</tr>
<tr>
<td><code>DhcpPushRoutes_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the static routing table to push. Example: "192.168.5.0/255.255.255.0/192.168.4.254, 10.0.0.0/255.0.0.0/192.168.4.253" Split multiple entries (maximum: 64 entries) by comma or space characters. Each entry must be specified in the "IP network address/subnet mask/gateway IP address" format. This Virtual DHCP Server can push the classless static routes (RFC 3442) with DHCP reply messages to VPN clients. Whether or not a VPN client can recognize the classless static routes (RFC 3442) depends on the target VPN client software. SoftEther VPN Client and OpenVPN Client are supporting the classless static routes. On L2TP/IPsec and MS-SSTP protocols, the compatibility depends on the implementation of the client software. You can realize the split tunneling if you clear the default gateway field on the Virtual DHCP Server options. On the client side, L2TP/IPsec and MS-SSTP clients need to be configured not to set up the default gateway for the split tunneling usage. You can also push the classless static routes (RFC 3442) by your existing external DHCP server. In that case, disable the Virtual DHCP Server function on SecureNAT, and you need not to set up the classless routes on this API. See the RFC 3442 to understand the classless routes.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="enumnat"></a></p>
<h2id="enumnat-rpc-api-get-virtual-nat-function-session-table-of-securenat-function">"EnumNAT" RPC API - Get Virtual NAT Function Session Table of SecureNAT Function</h2>
<p>Get Virtual NAT Function Session Table of SecureNAT Function. Use this to get the table of TCP and UDP sessions currently communicating via the Virtual NAT (NAT table) in cases when the Virtual NAT function is operating on the currently managed Virtual Hub. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>TCP state<BR>Values:<BR><code>0</code>: Connecting<BR><code>1</code>: Send the RST (Connection failure or disconnected)<BR><code>2</code>: Connection complete<BR><code>3</code>: Connection established<BR><code>4</code>: Wait for socket disconnection</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="enumdhcp"></a></p>
<h2id="enumdhcp-rpc-api-get-virtual-dhcp-server-function-lease-table-of-securenat-function">"EnumDHCP" RPC API - Get Virtual DHCP Server Function Lease Table of SecureNAT Function</h2>
<p>Get Virtual DHCP Server Function Lease Table of SecureNAT Function. Use this to get the lease table of IP addresses, held by the Virtual DHCP Server, that are assigned to clients in cases when the Virtual NAT function is operating on the currently managed Virtual Hub. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<h2id="getsecurenatstatus-rpc-api-get-the-operating-status-of-the-virtual-nat-and-dhcp-server-function-securenat-function">"GetSecureNATStatus" RPC API - Get the Operating Status of the Virtual NAT and DHCP Server Function (SecureNAT Function)</h2>
<p>Get the Operating Status of the Virtual NAT and DHCP Server Function (SecureNAT Function). Use this to get the operating status of the Virtual NAT and DHCP Server function (SecureNAT Function) when it is operating on the currently managed Virtual Hub. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Whether the NAT is operating in the Kernel Mode</td>
</tr>
<tr>
<td><code>IsRawIpMode_bool</code></td>
<td><code>boolean</code></td>
<td>Whether the NAT is operating in the Raw IP Mode</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="enumethernet"></a></p>
<h2id="enumethernet-rpc-api-get-list-of-network-adapters-usable-as-local-bridge">"EnumEthernet" RPC API - Get List of Network Adapters Usable as Local Bridge</h2>
<p>Get List of Network Adapters Usable as Local Bridge. Use this to get a list of Ethernet devices (network adapters) that can be used as a bridge destination device as part of a Local Bridge connection. If possible, network connection name is displayed. You can use a device displayed here by using the AddLocalBridge API. To call this API, you must have VPN Server administrator privileges.</p>
<p>Create Local Bridge Connection. Use this to create a new Local Bridge connection on the VPN Server. By using a Local Bridge, you can configure a Layer 2 bridge connection between a Virtual Hub operating on this VPN server and a physical Ethernet Device (Network Adapter). You can create a tap device (virtual network interface) on the system and connect a bridge between Virtual Hubs (the tap device is only supported by Linux versions). It is possible to establish a bridge to an operating network adapter of your choice for the bridge destination Ethernet device (network adapter), but in high load environments, we recommend you prepare a network adapter dedicated to serve as a bridge. To call this API, you must have VPN Server administrator privileges.</p>
<p>Delete Local Bridge Connection. Use this to delete an existing Local Bridge connection. To get a list of current Local Bridge connections use the EnumLocalBridge API. To call this API, you must have VPN Server administrator privileges.</p>
<p>Get List of Local Bridge Connection. Use this to get a list of the currently defined Local Bridge connections. You can get the Local Bridge connection Virtual Hub name and the bridge destination Ethernet device (network adapter) name or tap device name, as well as the operating status.</p>
<td>Specify true if you are using a tap device rather than a network adapter for the bridge destination (only supported for Linux versions).</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getbridgesupport"></a></p>
<h2id="getbridgesupport-rpc-api-get-whether-the-localbridge-function-is-supported-on-the-current-system">"GetBridgeSupport" RPC API - Get whether the localbridge function is supported on the current system</h2>
<p>Reboot VPN Server Service. Use this to restart the VPN Server service. When you restart the VPN Server, all currently connected sessions and TCP connections will be disconnected and no new connections will be accepted until the restart process has completed. By using this API, only the VPN Server service program will be restarted and the physical computer that VPN Server is operating on does not restart. This management session will also be disconnected, so you will need to reconnect to continue management. Also, by specifying the "IntValue" parameter to "1", the contents of the configuration file (.config) held by the current VPN Server will be initialized. To call this API, you must have VPN Server administrator privileges.</p>
<p>Get List of Server Functions / Capability. Use this get a list of functions and capability of the VPN Server currently connected and being managed. The function and capability of VPN Servers are different depending on the operating VPN server's edition and version. Using this API, you can find out the capability of the target VPN Server and report it.</p>
<h2id="getconfig-rpc-api-get-the-current-configuration-of-the-vpn-server">"GetConfig" RPC API - Get the current configuration of the VPN Server</h2>
<p>Get the current configuration of the VPN Server. Use this to get a text file (.config file) that contains the current configuration contents of the VPN server. You can get the status on the VPN Server at the instant this API is executed. You can edit the configuration file by using a regular text editor. To write an edited configuration to the VPN Server, use the SetConfig API. To call this API, you must have VPN Server administrator privileges.</p>
<p>Write Configuration File to VPN Server. Use this to write the configuration file to the VPN Server. By executing this API, the contents of the specified configuration file will be applied to the VPN Server and the VPN Server program will automatically restart and upon restart, operate according to the new configuration contents. Because it is difficult for an administrator to write all the contents of a configuration file, we recommend you use the GetConfig API to get the current contents of the VPN Server configuration and save it to file. You can then edit these contents in a regular text editor and then use the SetConfig API to rewrite the contents to the VPN Server. This API is for people with a detailed knowledge of the VPN Server and if an incorrectly configured configuration file is written to the VPN Server, it not only could cause errors, it could also result in the lost of the current setting data. Take special care when carrying out this action. To call this API, you must have VPN Server administrator privileges.</p>
<h2id="gethubadminoptions-rpc-api-get-list-of-virtual-hub-administration-options">"GetHubAdminOptions" RPC API - Get List of Virtual Hub Administration Options</h2>
<p>Get List of Virtual Hub Administration Options. Use this to get a list of Virtual Hub administration options that are set on the currently managed Virtual Hub. The purpose of the Virtual Hub administration options is for the VPN Server Administrator to set limits for the setting ranges when the administration of the Virtual Hub is to be trusted to each Virtual Hub administrator. Only an administrator with administration privileges for this entire VPN Server is able to add, edit and delete the Virtual Hub administration options. The Virtual Hub administrators are unable to make changes to the administration options, however they are able to view them. There is an exception however. If allow_hub_admin_change_option is set to "1", even Virtual Hub administrators are able to edit the administration options. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster member.</p>
<h2id="sethubadminoptions-rpc-api-set-values-of-virtual-hub-administration-options">"SetHubAdminOptions" RPC API - Set Values of Virtual Hub Administration Options</h2>
<p>Set Values of Virtual Hub Administration Options. Use this to change the values of Virtual Hub administration options that are set on the currently managed Virtual Hub. The purpose of the Virtual Hub administration options is for the VPN Server Administrator to set limits for the setting ranges when the administration of the Virtual Hub is to be trusted to each Virtual Hub administrator. Only an administrator with administration privileges for this entire VPN Server is able to add, edit and delete the Virtual Hub administration options. The Virtual Hub administrators are unable to make changes to the administration options, however they are able to view them. There is an exception however. If allow_hub_admin_change_option is set to "1", even Virtual Hub administrators are able to edit the administration options. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster member.</p>
<h2id="gethubextoptions-rpc-api-get-list-of-virtual-hub-extended-options">"GetHubExtOptions" RPC API - Get List of Virtual Hub Extended Options</h2>
<p>Get List of Virtual Hub Extended Options. Use this to get a Virtual Hub Extended Options List that is set on the currently managed Virtual Hub. Virtual Hub Extended Option enables you to configure more detail settings of the Virtual Hub. By default, both VPN Server's global administrators and individual Virtual Hub's administrators can modify the Virtual Hub Extended Options. However, if the deny_hub_admin_change_ext_option is set to 1 on the Virtual Hub Admin Options, the individual Virtual Hub's administrators cannot modify the Virtual Hub Extended Options. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster member.</p>
<h2id="sethubextoptions-rpc-api-set-a-value-of-virtual-hub-extended-options">"SetHubExtOptions" RPC API - Set a Value of Virtual Hub Extended Options</h2>
<p>Set a Value of Virtual Hub Extended Options. Use this to set a value in the Virtual Hub Extended Options List that is set on the currently managed Virtual Hub. Virtual Hub Extended Option enables you to configure more detail settings of the Virtual Hub. By default, both VPN Server's global administrators and individual Virtual Hub's administrators can modify the Virtual Hub Extended Options. However, if the deny_hub_admin_change_ext_option is set to 1 on the Virtual Hub Admin Options, the individual Virtual Hub's administrators cannot modify the Virtual Hub Extended Options. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster member.</p>
<p>Define New Virtual Layer 3 Switch. Use this to define a new Virtual Layer 3 Switch on the VPN Server. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Bridge. [Explanation on Virtual Layer 3 Switch Function] You can define Virtual Layer 3 Switches between multiple Virtual Hubs operating on this VPN Server and configure routing between different IP networks. [Caution about the Virtual Layer 3 Switch Function] The Virtual Layer 3 Switch functions are provided for network administrators and other people who know a lot about networks and IP routing. If you are using the regular VPN functions, you do not need to use the Virtual Layer 3 Switch functions. If the Virtual Layer 3 Switch functions are to be used, the person who configures them must have sufficient knowledge of IP routing and be perfectly capable of not impacting the network.</p>
<p>Delete Virtual Layer 3 Switch. Use this to delete an existing Virtual Layer 3 Switch that is defined on the VPN Server. When the specified Virtual Layer 3 Switch is operating, it will be automatically deleted after operation stops. To get a list of existing Virtual Layer 3 Switches, use the EnumL3Switch API. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Bridge.</p>
<p>Get List of Virtual Layer 3 Switches. Use this to define a new Virtual Layer 3 Switch on the VPN Server. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Bridge. [Explanation on Virtual Layer 3 Switch Function] You can define Virtual Layer 3 Switches between multiple Virtual Hubs operating on this VPN Server and configure routing between different IP networks. [Caution about the Virtual Layer 3 Switch Function] The Virtual Layer 3 Switch functions are provided for network administrators and other people who know a lot about networks and IP routing. If you are using the regular VPN functions, you do not need to use the Virtual Layer 3 Switch functions. If the Virtual Layer 3 Switch functions are to be used, the person who configures them must have sufficient knowledge of IP routing and be perfectly capable of not impacting the network.</p>
<p>Start Virtual Layer 3 Switch Operation. Use this to start the operation of an existing Virtual Layer 3 Switch defined on the VPN Server whose operation is currently stopped. To get a list of existing Virtual Layer 3 Switches, use the EnumL3Switch API. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Bridge. [Explanation on Virtual Layer 3 Switch Function] You can define Virtual Layer 3 Switches between multiple Virtual Hubs operating on this VPN Server and configure routing between different IP networks. [Caution about the Virtual Layer 3 Switch Function] The Virtual Layer 3 Switch functions are provided for network administrators and other people who know a lot about networks and IP routing. If you are using the regular VPN functions, you do not need to use the Virtual Layer 3 Switch functions. If the Virtual Layer 3 Switch functions are to be used, the person who configures them must have sufficient knowledge of IP routing and be perfectly capable of not impacting the network.</p>
<p>Stop Virtual Layer 3 Switch Operation. Use this to stop the operation of an existing Virtual Layer 3 Switch defined on the VPN Server whose operation is currently operating. To get a list of existing Virtual Layer 3 Switches, use the EnumL3Switch API. To call this API, you must have VPN Server administrator privileges.</p>
<p>Add Virtual Interface to Virtual Layer 3 Switch. Use this to add to a specified Virtual Layer 3 Switch, a virtual interface that connects to a Virtual Hub operating on the same VPN Server. You can define multiple virtual interfaces and routing tables for a single Virtual Layer 3 Switch. A virtual interface is associated to a virtual Hub and operates as a single IP host on the Virtual Hub when that Virtual Hub is operating. When multiple virtual interfaces that respectively belong to a different IP network of a different Virtual Hub are defined, IP routing will be automatically performed between these interfaces. You must define the IP network space that the virtual interface belongs to and the IP address of the interface itself. Also, you must specify the name of the Virtual Hub that the interface will connect to. You can specify a Virtual Hub that currently doesn't exist for the Virtual Hub name. The virtual interface must have one IP address in the Virtual Hub. You also must specify the subnet mask of an IP network that the IP address belongs to. Routing via the Virtual Layer 3 Switches of IP spaces of multiple virtual Hubs operates based on the IP address is specified here. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Bridge. To execute this API, the target Virtual Layer 3 Switch must be stopped. If it is not stopped, first use the StopL3Switch API to stop it and then execute this API.</p>
<p>Delete Virtual Interface of Virtual Layer 3 Switch. Use this to delete a virtual interface already defined in the specified Virtual Layer 3 Switch. You can get a list of the virtual interfaces currently defined, by using the EnumL3If API. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Bridge. To execute this API, the target Virtual Layer 3 Switch must be stopped. If it is not stopped, first use the StopL3Switch API to stop it and then execute this API.</p>
<h2id="enuml3if-rpc-api-get-list-of-interfaces-registered-on-the-virtual-layer-3-switch">"EnumL3If" RPC API - Get List of Interfaces Registered on the Virtual Layer 3 Switch</h2>
<p>Get List of Interfaces Registered on the Virtual Layer 3 Switch. Use this to get a list of virtual interfaces when virtual interfaces have been defined on a specified Virtual Layer 3 Switch. You can define multiple virtual interfaces and routing tables for a single Virtual Layer 3 Switch. A virtual interface is associated to a virtual Hub and operates as a single IP host on the Virtual Hub when that Virtual Hub is operating. When multiple virtual interfaces that respectively belong to a different IP network of a different Virtual Hub are defined, IP routing will be automatically performed between these interfaces. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Bridge.</p>
<p>Add Routing Table Entry for Virtual Layer 3 Switch. Here you can add a new routing table entry to the routing table of the specified Virtual Layer 3 Switch. If the destination IP address of the IP packet does not belong to any IP network that belongs to a virtual interface, the IP routing engine of the Virtual Layer 3 Switch will reference the routing table and execute routing. You must specify the contents of the routing table entry to be added to the Virtual Layer 3 Switch. You must specify any IP address that belongs to the same IP network in the virtual interface of this Virtual Layer 3 Switch as the gateway address. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Bridge. To execute this API, the target Virtual Layer 3 Switch must be stopped. If it is not stopped, first use the StopL3Switch API to stop it and then execute this API.</p>
<p>Delete Routing Table Entry of Virtual Layer 3 Switch. Use this to delete a routing table entry that is defined in the specified Virtual Layer 3 Switch. You can get a list of the already defined routing table entries by using the EnumL3Table API. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Bridge. To execute this API, the target Virtual Layer 3 Switch must be stopped. If it is not stopped, first use the StopL3Switch API to stop it and then execute this API.</p>
<h2id="enuml3table-rpc-api-get-list-of-routing-tables-of-virtual-layer-3-switch">"EnumL3Table" RPC API - Get List of Routing Tables of Virtual Layer 3 Switch</h2>
<p>Get List of Routing Tables of Virtual Layer 3 Switch. Use this to get a list of routing tables when routing tables have been defined on a specified Virtual Layer 3 Switch. If the destination IP address of the IP packet does not belong to any IP network that belongs to a virtual interface, the IP routing engine of the Virtual Layer 3 Switch will reference this routing table and execute routing. To call this API, you must have VPN Server administrator privileges. Also, this API does not operate on VPN Bridge.</p>
<p>Get List of Certificates Revocation List. Use this to get a Certificates Revocation List that is set on the currently managed Virtual Hub. By registering certificates in the Certificates Revocation List, the clients who provide these certificates will be unable to connect to this Virtual Hub using certificate authentication mode. Normally with this function, in cases where the security of a private key has been compromised or where a person holding a certificate has been stripped of their privileges, by registering that certificate as invalid on the Virtual Hub, it is possible to deny user authentication when that certificate is used by a client to connect to the Virtual Hub. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Add a Revoked Certificate. Use this to add a new revoked certificate definition in the Certificate Revocation List that is set on the currently managed Virtual Hub. Specify the contents to be registered in the Certificate Revocation List by using the parameters of this API. When a user connects to a Virtual Hub in certificate authentication mode and that certificate matches 1 or more of the contents registered in the certificates revocation list, the user is denied connection. A certificate that matches all the conditions that are defined by the parameters specified by this API will be judged as invalid. The items that can be set are as follows: Name (CN), Organization (O), Organization Unit (OU), Country (C), State (ST), Locale (L), Serial Number (hexadecimal), MD5 Digest Value (hexadecimal, 128 bit), and SHA-1 Digest Value (hexadecimal, 160 bit). For the specification of a digest value (hash value) a certificate is optionally specified depending on the circumstances. Normally when a MD5 or SHA-1 digest value is input, it is not necessary to input the other items. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Delete a Revoked Certificate. Use this to specify and delete a revoked certificate definition from the certificate revocation list that is set on the currently managed Virtual Hub. To get the list of currently registered revoked certificate definitions, use the EnumCrl API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Get a Revoked Certificate. Use this to specify and get the contents of a revoked certificate definition from the Certificates Revocation List that is set on the currently managed Virtual Hub. To get the list of currently registered revoked certificate definitions, use the EnumCrl API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Change Existing CRL (Certificate Revocation List) Entry. Use this to alter an existing revoked certificate definition in the Certificate Revocation List that is set on the currently managed Virtual Hub. Specify the contents to be registered in the Certificate Revocation List by using the parameters of this API. When a user connects to a Virtual Hub in certificate authentication mode and that certificate matches 1 or more of the contents registered in the certificates revocation list, the user is denied connection. A certificate that matches all the conditions that are defined by the parameters specified by this API will be judged as invalid. The items that can be set are as follows: Name (CN), Organization (O), Organization Unit (OU), Country (C), State (ST), Locale (L), Serial Number (hexadecimal), MD5 Digest Value (hexadecimal, 128 bit), and SHA-1 Digest Value (hexadecimal, 160 bit). For the specification of a digest value (hash value) a certificate is optionally specified depending on the circumstances. Normally when a MD5 or SHA-1 digest value is input, it is not necessary to input the other items. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Add Rule to Source IP Address Limit List. Use this to add a new rule to the Source IP Address Limit List that is set on the currently managed Virtual Hub. The items set here will be used to decide whether to allow or deny connection from a VPN Client when this client attempts connection to the Virtual Hub. You can specify a client IP address, or IP address or mask to match the rule as the contents of the rule item. By specifying an IP address only, there will only be one specified computer that will match the rule, but by specifying an IP net mask address or subnet mask address, all the computers in the range of that subnet will match the rule. You can specify the priority for the rule. You can specify an integer of 1 or greater for the priority and the smaller the number, the higher the priority. To get a list of the currently registered Source IP Address Limit List, use the GetAcList API. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Set true if you want to specify the SubnetMask_ip item.</td>
</tr>
<tr>
<td><code>IpAddress_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>IP address</td>
</tr>
<tr>
<td><code>SubnetMask_ip</code></td>
<td><code>string</code> (IP address)</td>
<td>Subnet mask, valid only if Masked_bool == true</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getaclist"></a></p>
<h2id="getaclist-rpc-api-get-list-of-rule-items-of-source-ip-address-limit-list">"GetAcList" RPC API - Get List of Rule Items of Source IP Address Limit List</h2>
<p>Get List of Rule Items of Source IP Address Limit List. Use this to get a list of Source IP Address Limit List rules that is set on the currently managed Virtual Hub. You can allow or deny VPN connections to this Virtual Hub according to the client computer's source IP address. You can define multiple rules and set a priority for each rule. The search proceeds from the rule with the highest order or priority and based on the action of the rule that the IP address first matches, the connection from the client is either allowed or denied. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Get List of Log Files. Use this to display a list of log files outputted by the VPN Server that have been saved on the VPN Server computer. By specifying a log file file name displayed here and calling it using the ReadLogFile API you can download the contents of the log file. If you are connected to the VPN Server in server admin mode, you can display or download the packet logs and security logs of all Virtual Hubs and the server log of the VPN Server. When connected in Virtual Hub Admin Mode, you are able to view or download only the packet log and security log of the Virtual Hub that is the target of management.</p>
<p>Download a part of Log File. Use this to download the log file that is saved on the VPN Server computer. To download the log file first get the list of log files using the EnumLogFile API and then download the log file using the ReadLogFile API. If you are connected to the VPN Server in server admin mode, you can display or download the packet logs and security logs of all Virtual Hubs and the server log of the VPN Server. When connected in Virtual Hub Admin Mode, you are able to view or download only the packet log and security log of the Virtual Hub that is the target of management.</p>
<td>Offset to download. You have to call the ReadLogFile API multiple times to download the entire log file with requesting a part of the file by specifying the Offset_u32 field.</td>
</tr>
<tr>
<td><code>Buffer_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Received buffer</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="setsyslog"></a></p>
<h2id="setsyslog-rpc-api-set-syslog-send-function">"SetSysLog" RPC API - Set syslog Send Function</h2>
<td>The behavior of the syslog function<BR>Values:<BR><code>0</code>: Do not use syslog<BR><code>1</code>: Only server log<BR><code>2</code>: Server and Virtual HUB security log<BR><code>3</code>: Server, Virtual HUB security, and packet log</td>
</tr>
<tr>
<td><code>Hostname_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the host name or IP address of the syslog server</td>
</tr>
<tr>
<td><code>Port_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Specify the port number of the syslog server</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getsyslog"></a></p>
<h2id="getsyslog-rpc-api-get-syslog-send-function">"GetSysLog" RPC API - Get syslog Send Function</h2>
<p>Get syslog Send Function. This allows you to get the current setting contents of the syslog send function. You can get the usage setting of the syslog function and the host name and port number of the syslog server to use.</p>
<td>The behavior of the syslog function<BR>Values:<BR><code>0</code>: Do not use syslog<BR><code>1</code>: Only server log<BR><code>2</code>: Server and Virtual HUB security log<BR><code>3</code>: Server, Virtual HUB security, and packet log</td>
</tr>
<tr>
<td><code>Hostname_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the host name or IP address of the syslog server</td>
</tr>
<tr>
<td><code>Port_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Specify the port number of the syslog server</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="sethubmsg"></a></p>
<h2id="sethubmsg-rpc-api-set-todays-message-of-virtual-hub">"SetHubMsg" RPC API - Set Today's Message of Virtual Hub</h2>
<h2id="crash-rpc-api-raise-a-vital-error-on-the-vpn-server-bridge-to-terminate-the-process-forcefully">"Crash" RPC API - Raise a vital error on the VPN Server / Bridge to terminate the process forcefully</h2>
<p>Raise a vital error on the VPN Server / Bridge to terminate the process forcefully. This API will raise a fatal error (memory access violation) on the VPN Server / Bridge running process in order to crash the process. As the result, VPN Server / Bridge will be terminated and restarted if it is running as a service mode. If the VPN Server is running as a user mode, the process will not automatically restarted. This API is for a situation when the VPN Server / Bridge is under a non-recoverable error or the process is in an infinite loop. This API will disconnect all VPN Sessions on the VPN Server / Bridge. All unsaved settings in the memory of VPN Server / Bridge will be lost. Before run this API, call the Flush API to try to save volatile data to the configuration file. To execute this API, you must have VPN Server / VPN Bridge administrator privileges.</p>
<h2id="flush-rpc-api-save-all-volatile-data-of-vpn-server-bridge-to-the-configuration-file">"Flush" RPC API - Save All Volatile Data of VPN Server / Bridge to the Configuration File</h2>
<p>Save All Volatile Data of VPN Server / Bridge to the Configuration File. The number of configuration file bytes will be returned as the "IntValue" parameter. Normally, the VPN Server / VPN Bridge retains the volatile configuration data in memory. It is flushed to the disk as vpn_server.config or vpn_bridge.config periodically. The period is 300 seconds (5 minutes) by default. (The period can be altered by modifying the AutoSaveConfigSpan item in the configuration file.) The data will be saved on the timing of shutting down normally of the VPN Server / Bridge. Execute the Flush API to make the VPN Server / Bridge save the settings to the file immediately. The setting data will be stored on the disk drive of the server computer. Use the Flush API in a situation that you do not have an enough time to shut down the server process normally. To call this API, you must have VPN Server administrator privileges. To execute this API, you must have VPN Server / VPN Bridge administrator privileges.</p>
<h2id="setipsecservices-rpc-api-enable-or-disable-ipsec-vpn-server-function">"SetIPsecServices" RPC API - Enable or Disable IPsec VPN Server Function</h2>
<p>Enable or Disable IPsec VPN Server Function. Enable or Disable IPsec VPN Server Function on the VPN Server. If you enable this function, Virtual Hubs on the VPN Server will be able to accept Remote-Access VPN connections from L2TP-compatible PCs, Mac OS X and Smartphones, and also can accept EtherIP Site-to-Site VPN Connection. VPN Connections from Smartphones suchlike iPhone, iPad and Android, and also from native VPN Clients on Mac OS X and Windows can be accepted. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Enable or Disable the L2TP Server Function (Raw L2TP with No Encryptions). To accept special VPN clients, enable this option.</td>
</tr>
<tr>
<td><code>L2TP_IPsec_bool</code></td>
<td><code>boolean</code></td>
<td>Enable or Disable the L2TP over IPsec Server Function. To accept VPN connections from iPhone, iPad, Android, Windows or Mac OS X, enable this option.</td>
</tr>
<tr>
<td><code>EtherIP_IPsec_bool</code></td>
<td><code>boolean</code></td>
<td>Enable or Disable the EtherIP / L2TPv3 over IPsec Server Function (for site-to-site VPN Server function). Router Products which are compatible with EtherIP over IPsec can connect to Virtual Hubs on the VPN Server and establish Layer-2 (Ethernet) Bridging.</td>
</tr>
<tr>
<td><code>IPsec_Secret_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the IPsec Pre-Shared Key. An IPsec Pre-Shared Key is also called as "PSK" or "secret". Specify it equal or less than 8 letters, and distribute it to every users who will connect to the VPN Server. Please note: Google Android 4.0 has a bug which a Pre-Shared Key with 10 or more letters causes a unexpected behavior. For that reason, the letters of a Pre-Shared Key should be 9 or less characters.</td>
</tr>
<tr>
<td><code>L2TP_DefaultHub_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the default Virtual HUB in a case of omitting the name of HUB on the Username. Users should specify their username such as "Username@Target Virtual HUB Name" to connect this L2TP Server. If the designation of the Virtual Hub is omitted, the above HUB will be used as the target.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getipsecservices"></a></p>
<h2id="getipsecservices-rpc-api-get-the-current-ipsec-vpn-server-settings">"GetIPsecServices" RPC API - Get the Current IPsec VPN Server Settings</h2>
<p>Get the Current IPsec VPN Server Settings. Get and view the current IPsec VPN Server settings on the VPN Server. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Enable or Disable the L2TP Server Function (Raw L2TP with No Encryptions). To accept special VPN clients, enable this option.</td>
</tr>
<tr>
<td><code>L2TP_IPsec_bool</code></td>
<td><code>boolean</code></td>
<td>Enable or Disable the L2TP over IPsec Server Function. To accept VPN connections from iPhone, iPad, Android, Windows or Mac OS X, enable this option.</td>
</tr>
<tr>
<td><code>EtherIP_IPsec_bool</code></td>
<td><code>boolean</code></td>
<td>Enable or Disable the EtherIP / L2TPv3 over IPsec Server Function (for site-to-site VPN Server function). Router Products which are compatible with EtherIP over IPsec can connect to Virtual Hubs on the VPN Server and establish Layer-2 (Ethernet) Bridging.</td>
</tr>
<tr>
<td><code>IPsec_Secret_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the IPsec Pre-Shared Key. An IPsec Pre-Shared Key is also called as "PSK" or "secret". Specify it equal or less than 8 letters, and distribute it to every users who will connect to the VPN Server. Please note: Google Android 4.0 has a bug which a Pre-Shared Key with 10 or more letters causes a unexpected behavior. For that reason, the letters of a Pre-Shared Key should be 9 or less characters.</td>
</tr>
<tr>
<td><code>L2TP_DefaultHub_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the default Virtual HUB in a case of omitting the name of HUB on the Username. Users should specify their username such as "Username@Target Virtual HUB Name" to connect this L2TP Server. If the designation of the Virtual Hub is omitted, the above HUB will be used as the target.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="addetheripid"></a></p>
<h2id="addetheripid-rpc-api-add-new-etherip-l2tpv3-over-ipsec-client-setting-to-accept-ethreip-l2tpv3-client-devices">"AddEtherIpId" RPC API - Add New EtherIP / L2TPv3 over IPsec Client Setting to Accept EthreIP / L2TPv3 Client Devices</h2>
<p>Add New EtherIP / L2TPv3 over IPsec Client Setting to Accept EthreIP / L2TPv3 Client Devices. Add a new setting entry to enable the EtherIP / L2TPv3 over IPsec Server Function to accept client devices. In order to accept connections from routers by the EtherIP / L2TPv3 over IPsec Server Function, you have to define the relation table between an IPsec Phase 1 string which is presented by client devices of EtherIP / L2TPv3 over IPsec compatible router, and the designation of the destination Virtual Hub. After you add a definition entry by AddEtherIpId API, the defined connection setting to the Virtual Hub will be applied on the login-attepting session from an EtherIP / L2TPv3 over IPsec client device. The username and password in an entry must be registered on the Virtual Hub. An EtherIP / L2TPv3 client will be regarded as it connected the Virtual HUB with the identification of the above user information. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Specify an ISAKMP Phase 1 ID. The ID must be exactly same as a ID in the configuration of the EtherIP / L2TPv3 Client. You can specify IP address as well as characters as ID, if the EtherIP Client uses IP address as Phase 1 ID. If you specify '*' (asterisk), it will be a wildcard to match any clients which doesn't match other explicit rules.</td>
</tr>
<tr>
<td><code>HubName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the name of the Virtual Hub to connect.</td>
</tr>
<tr>
<td><code>UserName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the username to login to the destination Virtual Hub.</td>
</tr>
<tr>
<td><code>Password_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the password to login to the destination Virtual Hub.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getetheripid"></a></p>
<h2id="getetheripid-rpc-api-get-the-current-list-of-etherip-l2tpv3-client-device-entry-definitions">"GetEtherIpId" RPC API - Get the Current List of EtherIP / L2TPv3 Client Device Entry Definitions</h2>
<p>Get the Current List of EtherIP / L2TPv3 Client Device Entry Definitions. This API gets and shows the list of entries to accept VPN clients by EtherIP / L2TPv3 over IPsec Function. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Specify an ISAKMP Phase 1 ID. The ID must be exactly same as a ID in the configuration of the EtherIP / L2TPv3 Client. You can specify IP address as well as characters as ID, if the EtherIP Client uses IP address as Phase 1 ID. If you specify '*' (asterisk), it will be a wildcard to match any clients which doesn't match other explicit rules.</td>
</tr>
<tr>
<td><code>HubName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the name of the Virtual Hub to connect.</td>
</tr>
<tr>
<td><code>UserName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the username to login to the destination Virtual Hub.</td>
</tr>
<tr>
<td><code>Password_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the password to login to the destination Virtual Hub.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="deleteetheripid"></a></p>
<h2id="deleteetheripid-rpc-api-delete-an-etherip-l2tpv3-over-ipsec-client-setting">"DeleteEtherIpId" RPC API - Delete an EtherIP / L2TPv3 over IPsec Client Setting</h2>
<p>Delete an EtherIP / L2TPv3 over IPsec Client Setting. This API deletes an entry to accept VPN clients by EtherIP / L2TPv3 over IPsec Function. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Specify an ISAKMP Phase 1 ID. The ID must be exactly same as a ID in the configuration of the EtherIP / L2TPv3 Client. You can specify IP address as well as characters as ID, if the EtherIP Client uses IP address as Phase 1 ID. If you specify '*' (asterisk), it will be a wildcard to match any clients which doesn't match other explicit rules.</td>
</tr>
<tr>
<td><code>HubName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the name of the Virtual Hub to connect.</td>
</tr>
<tr>
<td><code>UserName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the username to login to the destination Virtual Hub.</td>
</tr>
<tr>
<td><code>Password_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the password to login to the destination Virtual Hub.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="enumetheripid"></a></p>
<h2id="enumetheripid-rpc-api-get-the-current-list-of-etherip-l2tpv3-client-device-entry-definitions">"EnumEtherIpId" RPC API - Get the Current List of EtherIP / L2TPv3 Client Device Entry Definitions</h2>
<p>Get the Current List of EtherIP / L2TPv3 Client Device Entry Definitions. This API gets and shows the list of entries to accept VPN clients by EtherIP / L2TPv3 over IPsec Function. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Specify an ISAKMP Phase 1 ID. The ID must be exactly same as a ID in the configuration of the EtherIP / L2TPv3 Client. You can specify IP address as well as characters as ID, if the EtherIP Client uses IP address as Phase 1 ID. If you specify '*' (asterisk), it will be a wildcard to match any clients which doesn't match other explicit rules.</td>
</tr>
<tr>
<td><code>HubName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the name of the Virtual Hub to connect.</td>
</tr>
<tr>
<td><code>UserName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the username to login to the destination Virtual Hub.</td>
</tr>
<tr>
<td><code>Password_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify the password to login to the destination Virtual Hub.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="setopenvpnsstpconfig"></a></p>
<h2id="setopenvpnsstpconfig-rpc-api-set-settings-for-openvpn-clone-server-function">"SetOpenVpnSstpConfig" RPC API - Set Settings for OpenVPN Clone Server Function</h2>
<p>Set Settings for OpenVPN Clone Server Function. The VPN Server has the clone functions of OpenVPN software products by OpenVPN Technologies, Inc. Any OpenVPN Clients can connect to this VPN Server. The manner to specify a username to connect to the Virtual Hub, and the selection rule of default Hub by using this clone server functions are same to the IPsec Server functions. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Specify true to enable the OpenVPN Clone Server Function. Specify false to disable.</td>
</tr>
<tr>
<td><code>OpenVPNPortList_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify UDP ports to listen for OpenVPN. Multiple UDP ports can be specified with splitting by space or comma letters, for example: "1194, 2001, 2010, 2012". The default port for OpenVPN is UDP 1194. You can specify any other UDP ports.</td>
</tr>
<tr>
<td><code>EnableSSTP_bool</code></td>
<td><code>boolean</code></td>
<td>pecify true to enable the Microsoft SSTP VPN Clone Server Function. Specify false to disable.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getopenvpnsstpconfig"></a></p>
<h2id="getopenvpnsstpconfig-rpc-api-get-the-current-settings-of-openvpn-clone-server-function">"GetOpenVpnSstpConfig" RPC API - Get the Current Settings of OpenVPN Clone Server Function</h2>
<p>Get the Current Settings of OpenVPN Clone Server Function. Get and show the current settings of OpenVPN Clone Server Function. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Specify true to enable the OpenVPN Clone Server Function. Specify false to disable.</td>
</tr>
<tr>
<td><code>OpenVPNPortList_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Specify UDP ports to listen for OpenVPN. Multiple UDP ports can be specified with splitting by space or comma letters, for example: "1194, 2001, 2010, 2012". The default port for OpenVPN is UDP 1194. You can specify any other UDP ports.</td>
</tr>
<tr>
<td><code>EnableSSTP_bool</code></td>
<td><code>boolean</code></td>
<td>pecify true to enable the Microsoft SSTP VPN Clone Server Function. Specify false to disable.</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getddnsclientstatus"></a></p>
<h2id="getddnsclientstatus-rpc-api-show-the-current-status-of-dynamic-dns-function">"GetDDnsClientStatus" RPC API - Show the Current Status of Dynamic DNS Function</h2>
<p>Show the Current Status of Dynamic DNS Function. Get and show the current status of the Dynamic DNS function. The Dynamic DNS assigns a unique and permanent DNS hostname for this VPN Server. You can use that hostname to specify this VPN Server on the settings for VPN Client and VPN Bridge. You need not to register and keep a domain name. Also, if your ISP assignes you a dynamic (not-fixed) IP address, the corresponding IP address of your Dynamic DNS hostname will be automatically changed. It enables you to keep running the VPN Server by using only a dynamic IP address. Therefore, you need not any longer to keep static global IP addresses with expenses monthly costs. [Caution] To disable the Dynamic DNS Function, modify the configuration file of VPN Server. The "declare root" directive has the "declare DDnsClient" directive. In this directive, you can switch "bool Disable" from false to true, and reboot the VPN Server, then the Dynamic DNS Function will be disabled. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge.</p>
<p>Set the Dynamic DNS Hostname. You must specify the new hostname on the StrValue_str field. You can use this API to change the hostname assigned by the Dynamic DNS function. The currently assigned hostname can be showen by the GetDDnsClientStatus API. The Dynamic DNS assigns a unique and permanent DNS hostname for this VPN Server. You can use that hostname to specify this VPN Server on the settings for VPN Client and VPN Bridge. You need not to register and keep a domain name. Also, if your ISP assignes you a dynamic (not-fixed) IP address, the corresponding IP address of your Dynamic DNS hostname will be automatically changed. It enables you to keep running the VPN Server by using only a dynamic IP address. Therefore, you need not any longer to keep static global IP addresses with expenses monthly costs. [Caution] To disable the Dynamic DNS Function, modify the configuration file of VPN Server. The "declare root" directive has the "declare DDnsClient" directive. In this directive, you can switch "bool Disable" from false to true, and reboot the VPN Server, then the Dynamic DNS Function will be disabled. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge.</p>
<h2id="regenerateservercert-rpc-api-generate-new-self-signed-certificate-with-specified-cn-common-name-and-register-on-vpn-server">"RegenerateServerCert" RPC API - Generate New Self-Signed Certificate with Specified CN (Common Name) and Register on VPN Server</h2>
<p>Generate New Self-Signed Certificate with Specified CN (Common Name) and Register on VPN Server. You can specify the new CN (common name) value on the StrValue_str field. You can use this API to replace the current certificate on the VPN Server to a new self-signed certificate which has the CN (Common Name) value in the fields. This API is convenient if you are planning to use Microsoft SSTP VPN Clone Server Function. Because of the value of CN (Common Name) on the SSL certificate of VPN Server must match to the hostname specified on the SSTP VPN client. This API will delete the existing SSL certificate of the VPN Server. It is recommended to backup the current SSL certificate and private key by using the GetServerCert API beforehand. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<h2id="makeopenvpnconfigfile-rpc-api-generate-a-sample-setting-file-for-openvpn-client">"MakeOpenVpnConfigFile" RPC API - Generate a Sample Setting File for OpenVPN Client</h2>
<p>Generate a Sample Setting File for OpenVPN Client. Originally, the OpenVPN Client requires a user to write a very difficult configuration file manually. This API helps you to make a useful configuration sample. What you need to generate the configuration file for the OpenVPN Client is to run this API. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Offset to download. You have to call the ReadLogFile API multiple times to download the entire log file with requesting a part of the file by specifying the Offset_u32 field.</td>
</tr>
<tr>
<td><code>Buffer_bin</code></td>
<td><code>string</code> (Base64 binary)</td>
<td>Received buffer</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="setspeciallistener"></a></p>
<h2id="setspeciallistener-rpc-api-enable-disable-the-vpn-over-icmp-vpn-over-dns-server-function">"SetSpecialListener" RPC API - Enable / Disable the VPN over ICMP / VPN over DNS Server Function</h2>
<p>Enable / Disable the VPN over ICMP / VPN over DNS Server Function. You can establish a VPN only with ICMP or DNS packets even if there is a firewall or routers which blocks TCP/IP communications. You have to enable the following functions beforehand. Warning: Use this function for emergency only. It is helpful when a firewall or router is misconfigured to blocks TCP/IP, but either ICMP or DNS is not blocked. It is not for long-term stable using. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge.</p>
<td>The flag to activate the VPN over ICMP server function</td>
</tr>
<tr>
<td><code>VpnOverDnsListener_bool</code></td>
<td><code>boolean</code></td>
<td>The flag to activate the VPN over DNS function</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getspeciallistener"></a></p>
<h2id="getspeciallistener-rpc-api-get-current-setting-of-the-vpn-over-icmp-vpn-over-dns-function">"GetSpecialListener" RPC API - Get Current Setting of the VPN over ICMP / VPN over DNS Function</h2>
<p>Get Current Setting of the VPN over ICMP / VPN over DNS Function. Get and show the current VPN over ICMP / VPN over DNS Function status. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge.</p>
<td>The flag to activate the VPN over ICMP server function</td>
</tr>
<tr>
<td><code>VpnOverDnsListener_bool</code></td>
<td><code>boolean</code></td>
<td>The flag to activate the VPN over DNS function</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getazurestatus"></a></p>
<h2id="getazurestatus-rpc-api-show-the-current-status-of-vpn-azure-function">"GetAzureStatus" RPC API - Show the current status of VPN Azure function</h2>
<p>Show the current status of VPN Azure function. Get and show the current status of the VPN Azure function. VPN Azure makes it easier to establish a VPN Session from your home PC to your office PC. While a VPN connection is established, you can access to any other servers on the private network of your company. You don't need a global IP address on the office PC (VPN Server). It can work behind firewalls or NATs. No network administrator's configuration required. You can use the built-in SSTP-VPN Client of Windows in your home PC. VPN Azure is a cloud VPN service operated by SoftEther Corporation. VPN Azure is free of charge and available to anyone. Visit <ahref="http://www.vpnazure.net/">http://www.vpnazure.net/</a> to see details and how-to-use instructions. The VPN Azure hostname is same to the hostname of the Dynamic DNS setting, but altering the domain suffix to "vpnazure.net". To change the hostname use the ChangeDDnsClientHostname API. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<p>Enable / Disable VPN Azure Function. Enable or disable the VPN Azure function. VPN Azure makes it easier to establish a VPN Session from your home PC to your office PC. While a VPN connection is established, you can access to any other servers on the private network of your company. You don't need a global IP address on the office PC (VPN Server). It can work behind firewalls or NATs. No network administrator's configuration required. You can use the built-in SSTP-VPN Client of Windows in your home PC. VPN Azure is a cloud VPN service operated by SoftEther Corporation. VPN Azure is free of charge and available to anyone. Visit <ahref="http://www.vpnazure.net/">http://www.vpnazure.net/</a> to see details and how-to-use instructions. The VPN Azure hostname is same to the hostname of the Dynamic DNS setting, but altering the domain suffix to "vpnazure.net". To change the hostname use the ChangeDDnsClientHostname API. To call this API, you must have VPN Server administrator privileges. This API cannot be invoked on VPN Bridge. You cannot execute this API for Virtual Hubs of VPN Servers operating as a cluster.</p>
<td>Whether connection to VPN Azure Cloud Server is established</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="getddnsinternetsettng"></a></p>
<h2id="getddnsinternetsettng-rpc-api-get-the-proxy-settings-for-connecting-to-the-ddns-server">"GetDDnsInternetSettng" RPC API - Get the Proxy Settings for Connecting to the DDNS server</h2>
<td>Type of proxy server<BR>Values:<BR><code>0</code>: Direct TCP connection<BR><code>1</code>: Connection via HTTP proxy server<BR><code>2</code>: Connection via SOCKS proxy server</td>
</tr>
<tr>
<td><code>ProxyHostName_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Proxy server host name</td>
</tr>
<tr>
<td><code>ProxyPort_u32</code></td>
<td><code>number</code> (uint32)</td>
<td>Proxy server port number</td>
</tr>
<tr>
<td><code>ProxyUsername_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Proxy server user name</td>
</tr>
<tr>
<td><code>ProxyPassword_str</code></td>
<td><code>string</code> (ASCII)</td>
<td>Proxy server password</td>
</tr>
</tbody>
</table>
<hr/>
<p><aid="setddnsinternetsettng"></a></p>
<h2id="setddnsinternetsettng-rpc-api-set-the-proxy-settings-for-connecting-to-the-ddns-server">"SetDDnsInternetSettng" RPC API - Set the Proxy Settings for Connecting to the DDNS server</h2>
<td>Type of proxy server<BR>Values:<BR><code>0</code>: Direct TCP connection<BR><code>1</code>: Connection via HTTP proxy server<BR><code>2</code>: Connection via SOCKS proxy server</td>
