10.9 Build a Large Scale Virtual Hub Hosting Service

Combined revision comparison

...

For example, if a small business wants to set up a remote access VPN system, but has a dynamic global IP address (an IP address that changes every time a connection to the Internet is made), they are unable to install a stable VPN Server within the company. (It is possible to install a VPN Server on this type of network using the DDNS service as explained in section 10.10.4 Adjusting Settings For Broadband Routers or Other Networking Hardware10.10 Your Home PC as VPN Relay for Protect WiFi Using, but this method is not recommended when stability is crucial.) There are also cases of small companies that have a static global IP address, but do not have the technical knowledge required for the daily management of a VPN Server. For these types of companies, a Virtual Hub hosting services provided by their ISP is a viable option. By making a permanent cascade connection from a VPN Bridge installed within the company to the Virtual Hub provided by the ISP, a company can provide a remote access VPN service as described in section 10.4 Build a Generic Remote Access VPN to their employees without running their own VPN Server. An illustration of this type of network is shown in the figure below. Employees wanting to use the remote access VPN connect to the Virtual Hub on the VPN Server provided by the ISP. Data is then routed through this Virtual Hub and to the VPN Bridge connected to the company network by a local bridge, granting remote access to the network.

...

The best one to use for a Virtual Hub hosting service is the dynamic Virtual Hub. (See section 3.9.8 Dynamic Virtual Hubs3.9 Clustering.)

...

Please refer to section 3.9.2 Cluster Controllers3.9 Clustering for more information on setting up a VPN Server as a cluster controller.

 

...

Each VPN Server installed after the first will connect to the cluster controller as a cluster member server. Please refer to section 3.9.3 Cluster Member Servers3.9 Clustering for more information on setting up a VPN Server as a cluster member server.

 

...

By connecting to the VPN Server with overall administrator rights you can manage or view the traffic volume of each Virtual Hub on the entire system. An ISP will need to use this to bill each user (Virtual Hub) appropriately according to the traffic volume of that individual user. You can get this information by retrieving the statistical data automatically created and managed by the VPN Server and each Virtual Hub. Also, this information is stored in the vpn_server.config configuration file generated by the cluster controller. By retrieving the data stored in this file you can measure the traffic volume for each user and bill them accordingly. Please refer to section 3.3.10 Administration of Statistical Information3.3 VPN Server Administration for more information on the statistical data generated by VPN Server and the Virtual Hubs. You could also make a simple program that process and records this information to automatically calculate billing for you.

 

...

This feature is referred to as the Virtual Hub management options and is a standard feature of VPN Server. Please refer to section 3.5.12 Virtual Hub Administration Options3.5 Virtual Hub Security Features for a list of items you can configure.

...

Other changes:

1. /body/p[13]/a/@href: "mks://localhost/4-docs/1-manual/A/10.A" ⇒ "mks://localhost/4-docs/1-manual/A/10.A#10.10.4_Adjusting_Settings_For_Broadband_Routers_or_Other_Networking_Hardware"
2. /body/p[13]/a/@title: "4-docs/1-manual/A/10.A" ⇒ "10.10.4 Adjusting Settings For Broadband Routers or Other Networking Hardware"
3. /body/p[24]/a/@href: "mks://localhost/4-docs/1-manual/3/3.9" ⇒ "mks://localhost/4-docs/1-manual/3/3.9#3.9.8_Dynamic_Virtual_Hubs"
4. /body/p[24]/a/@title: "4-docs/1-manual/3/3.9" ⇒ "3.9.8 Dynamic Virtual Hubs"
5. /body/p[33]/a/@href: "mks://localhost/4-docs/1-manual/3/3.9" ⇒ "mks://localhost/4-docs/1-manual/3/3.9#3.9.2_Cluster_Controllers"
6. /body/p[33]/a/@title: "4-docs/1-manual/3/3.9" ⇒ "3.9.2 Cluster Controllers"
7. /body/p[34]/a/@href: "mks://localhost/4-docs/1-manual/3/3.9" ⇒ "mks://localhost/4-docs/1-manual/3/3.9#3.9.3_Cluster_Member_Servers"
8. /body/p[34]/a/@title: "4-docs/1-manual/3/3.9" ⇒ "3.9.3 Cluster Member Servers"
9. /body/p[48]/a/@href: "mks://localhost/4-docs/1-manual/3/3.3" ⇒ "mks://localhost/4-docs/1-manual/3/3.3#3.3.10_Administration_of_Statistical_Information"
10. /body/p[48]/a/@title: "4-docs/1-manual/3/3.3" ⇒ "3.3.10 Administration of Statistical Information"
11. /body/p[50]/a/@href: "mks://localhost/4-docs/1-manual/3/3.5" ⇒ "mks://localhost/4-docs/1-manual/3/3.5#3.5.12_Virtual_Hub_Administration_Options"
12. /body/p[50]/a/@title: "4-docs/1-manual/3/3.5" ⇒ "3.5.12 Virtual Hub Administration Options"