Table of contents
Combined revision comparison
...
Fig. 1-4-1 Switching Hub and network adapter for Ethernet.
...
AFig. 1-4-2 Ethernet frame (MAC frame).)
...
The switching Hub used by Ethernet (layer 2 switch) constructs a network by Ethernet and is an important peripheral device for communication. Switching HubsHUBs have multiple ports (usually 8 ports, but can have from tens to hundreds. By connecting a compute to the Ethernet by network cable, etc., a physical network is connected between the switching Hub and computer's network adapter, thus enabling Ethernet communications by layer 2.
The ports of a switching Hub can also be connected to the ports of another switching Hub. Even though the connected switching HubsHUBs were originally separate Ethernet networks, by connecting them by network cable, they work like a single Ethernet network. This is called "cascade connection".
The computers connected to the switching HubsHUBs on the left and right in the following figure can communicate freely with each other.
...
Fig. 1-4-3 Segment junction by cascade connection of switching hubs.HUBs
...
Switching HubsHUBs constantly recognize in advance which computers with what sort of MAC address are connected to the respective ports and maintain the information in an internal database. This is called a "MAC address table".
...
As was previously mentioned, the method of connecting two segments configured of two switching HubsHUBs and using as a single segment is called "cascade connection". Cascade connection can consist of an unlimited number of cascades provided the physical limit established for Ethernet is not exceeded. The fact that cascade connection can be accomplished easily is one of the greatest features of using Ethernet. By cascade connecting another switching Hub to one for which the number of ports has become insufficient, you can increase the number of available ports and increase the number of computers that can be connected to the network.
...
Cascade connection and bridge connection are technically similar connection methods, but whereas cascade connection indicates connecting switching HubsHUBs to construct a single large segment from the beginning, bridge connection means connecting networks to be used as two segments that are physically separate and are administered separately.
...
Virtual Hub is one of the most important functions of SoftEther VPN. Virtual Hub implements the same level of functions as the existing common layer 2 switching Hub as software. Virtual Hub has a MAC address learning function and frame exchange/delivery functions based on learning. Whereas conventional switching HubsHUBs used to handle this processing as hardware, with Virtual Hub of SoftEther VPN, the processing is handled as software.
...
SoftEther VPN Server can create multiple Virtual HubsHUBs. You can create as many Virtual HubsHUBs as memory space, CPU speed and specifications will permit. Each respective Virtual Hub conducts MAC address learning for virtual Ethernet frames flowing through the VPN. As a result virtual layer 2 Ethernet segments are realized by sending Ethernet frames to computers participating in other VPNs.
...
Connection between Virtual HubsFig. 1-4-4 Connection between Virtual HUBs or between Virtual Network Adapters.
Creation and Administration of Multiple Virtual HubsHUBs
If multiple Virtual HubsHUBs are created within a single VPN server, those Virtual HubsHUBs cannot communicate with each other. Consequently if multiple Virtual HubsHUBs are created, it means multiple Ethernet segments are formed within the VPN Server.
...
Fig. 1-4-5 Segment separation by Virtual Hub within VPN Server.
...
These setting contents are completely independent for each Virtual Hub, and administration is divided into units so each individual administrator can administrate separately. Administrators of VPN Servers at large can manage all Virtual HubsHUBs, but administrators granted authority concerning some Virtual HubsHUBs from the VPN Server administrator can manage only those Virtual HubsHUBs and are unable to manage other Virtual HubsHUBs.
...
Method of Connecting Virtual HubsHUBs to each other
Virtual HubsHUBs can be cascade connected to Virtual HubsHUBs operating on the same VPN Server or VPN Server operating on another computer, and the cascade connected Virtual HubsHUBs that were originally separate segments are joined to work as a single segment.
For Virtual HubsHUBs operating on the same VPN Server, via virtual layer 3 switch by IP routing, network among Virtual HubsHUBs can be connected by layer 3.
...
Fig. 1-4-6 SoftEther VPN Virtual Network Adapter recognized as a network adapter by the operating system.
...
Fig. 1-4-7 Property window of Virtual Network Adapter
.
...
With SoftEther VPN Server, you can create multiple Virtual HubsHUBs and operate them together. In the initial state however Virtual HubsHUBs have only independent layer 2 segments, and although computers connected to the same Virtual Hub can communicate freely, computers connected to separate Virtual HubsHUBs cannot communicate with each other.
...
Using the virtual layer 3 switch function of SoftEther VPN Server enables IP routing among multiple Virtual HubsHUBs. If conducting IP routing among multiple Virtual HubsHUBs with the previous version of SoftEther 1.0, etc., you had to conduct IP routing with a physical layer 3 switch or special router by bridge connecting each respective Virtual Hub segment to a physical Ethernet segment. SoftEther VPN Server's support of virtual layer 3 switch function enables network administrators to easily realize communication among Virtual HubsHUBs by IP routing among multiple Virtual HubsHUBs.
...
Fig. 1-4-8 IP routing among Virtual HubsHUBs by virtual layer 3 switch.
...
By connecting Virtual Hub and physical existing LAN by multiple bases and by furthermore cascade connecting Virtual HubsHUBs existing physical LAN of multiple bases can be easily made a single segment via Internet to realize base-to-base VPN.
...
Fig. 1-4-9 Example of base-to-base connection by SoftEther VPN
.
...
Fig. 1-4-10 Computer-to-computer VPN
.
...
Fig. 1-4-11 Remote access VPN
.
...
Fig. 1-4-12 Base-to-base VPN of ordinary scale
.
...
Fig. 1-4-13 Base-to-base VPN of large scale.
Other changes:
- /body/p[6]/a/@class:
" external"⇒ nothing - /body/p[6]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-1.gif"⇒ "http://www.softether.org/@api/deki/files/107/=1-4-1.png" - /body/p[6]/a/@title: nothing ⇒ "1-4-1.png"
- /body/p[6]/a/img/@alt:
"Click to enlarge."⇒ "1-4-1.png" - /body/p[6]/a/img/@border:
"2"⇒ nothing - /body/p[6]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-1_small.jpg"⇒ "/@api/deki/files/107/=1-4-1.png?size=webview" - /body/p[6]/a/img/@class: nothing ⇒ "internal default"
- /body/p[6]/a/img/@style: nothing ⇒ "width: 550px; height: 304px;"
- /body/p[7]/@style: nothing ⇒ "text-align: center; "
- /body/p[10]/a/@class:
" external"⇒ nothing - /body/p[10]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-2.gif"⇒ "http://www.softether.org/@api/deki/files/108/=1-4-2.png" - /body/p[10]/a/@title: nothing ⇒ "1-4-2.png"
- /body/p[10]/a/img/@alt:
"Click to enlarge."⇒ "1-4-2.png" - /body/p[10]/a/img/@border:
"2"⇒ nothing - /body/p[10]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-2_small.jpg"⇒ "/@api/deki/files/108/=1-4-2.png?size=webview" - /body/p[10]/a/img/@class: nothing ⇒ "internal default"
- /body/p[10]/a/img/@style: nothing ⇒ "width: 550px; height: 81px;"
- /body/p[11]/@style: nothing ⇒ "text-align: center; "
- /body/p[21]/a/@class:
" external"⇒ nothing - /body/p[21]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-3.gif"⇒ "http://www.softether.org/@api/deki/files/109/=1-4-3.png" - /body/p[21]/a/@title: nothing ⇒ "1-4-3.png"
- /body/p[21]/a/img/@alt:
"Click to enlarge."⇒ "1-4-3.png" - /body/p[21]/a/img/@border:
"2"⇒ nothing - /body/p[21]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-3_small.jpg"⇒ "/@api/deki/files/109/=1-4-3.png?size=webview" - /body/p[21]/a/img/@class: nothing ⇒ "internal default"
- /body/p[21]/a/img/@style: nothing ⇒ "width: 550px; height: 217px;"
- /body/p[22]/@style: nothing ⇒ "text-align: center; "
- /body/p[36]/a/@class:
" external"⇒ nothing - /body/p[36]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-4.gif"⇒ "http://www.softether.org/@api/deki/files/110/=1-4-4.png" - /body/p[36]/a/@title: nothing ⇒ "1-4-4.png"
- /body/p[36]/a/img/@alt:
"Click to enlarge."⇒ "1-4-4.png" - /body/p[36]/a/img/@border:
"2"⇒ nothing - /body/p[36]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-4_small.jpg"⇒ "/@api/deki/files/110/=1-4-4.png?size=webview" - /body/p[36]/a/img/@class: nothing ⇒ "internal default"
- /body/p[36]/a/img/@style: nothing ⇒ "width: 550px; height: 262px;"
- /body/p[37]/@style: nothing ⇒ "text-align: center; "
- /body/p[40]/a/img/@alt:
"File:C:/TMP/130301vpn4man/VPN4_Manual_(English)/html/images/1-4-5.gif"⇒ "1-4-5.png" - /body/p[40]/a/img/@border:
"0"⇒ nothing - /body/p[40]/a/img/@height:
"272"⇒ nothing - /body/p[40]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-5.gif"⇒ "/@api/deki/files/111/=1-4-5.png?size=webview" - /body/p[40]/a/img/@width:
"377"⇒ nothing - /body/p[40]/a/img/@class: nothing ⇒ "internal default"
- /body/p[40]/a/img/@style: nothing ⇒ "width: 350px; height: 243px;"
- /body/p[41]/@style: nothing ⇒ "text-align: center; "
- /body/p[50]/a/@class:
" external"⇒ nothing - /body/p[50]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-6.gif"⇒ "http://www.softether.org/@api/deki/files/112/=1-4-6.png" - /body/p[50]/a/@title: nothing ⇒ "1-4-6.png"
- /body/p[50]/a/img/@alt:
"Click to enlarge."⇒ "1-4-6.png" - /body/p[50]/a/img/@border:
"2"⇒ nothing - /body/p[50]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-6_small.jpg"⇒ "/@api/deki/files/112/=1-4-6.png?size=webview" - /body/p[50]/a/img/@class: nothing ⇒ "internal default"
- /body/p[50]/a/img/@style: nothing ⇒ "width: 313px; height: 350px;"
- /body/p[51]/@style: nothing ⇒ "text-align: center; "
- /body/p[53]/a/@class:
" external"⇒ nothing - /body/p[53]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-7.gif"⇒ "http://www.softether.org/@api/deki/files/113/=1-4-7.png" - /body/p[53]/a/@title: nothing ⇒ "1-4-7.png"
- /body/p[53]/a/img/@alt:
"Click to enlarge."⇒ "1-4-7.png" - /body/p[53]/a/img/@border:
"2"⇒ nothing - /body/p[53]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-7_small.jpg"⇒ "/@api/deki/files/113/=1-4-7.png?size=webview" - /body/p[53]/a/img/@class: nothing ⇒ "internal default"
- /body/p[53]/a/img/@style: nothing ⇒ "width: 277px; height: 350px;"
- /body/p[54]/@style: nothing ⇒ "text-align: center; "
- /body/p[60]/a/@class:
" external"⇒ nothing - /body/p[60]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-8.gif"⇒ "http://www.softether.org/@api/deki/files/114/=1-4-8.png" - /body/p[60]/a/@title: nothing ⇒ "1-4-8.png"
- /body/p[60]/a/img/@alt:
"Click to enlarge."⇒ "1-4-8.png" - /body/p[60]/a/img/@border:
"2"⇒ nothing - /body/p[60]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-8_small.jpg"⇒ "/@api/deki/files/114/=1-4-8.png?size=webview" - /body/p[60]/a/img/@class: nothing ⇒ "internal default"
- /body/p[60]/a/img/@style: nothing ⇒ "width: 350px; height: 283px;"
- /body/p[61]/@style: nothing ⇒ "text-align: center; "
- /body/p[65]/a/@class:
" external"⇒ nothing - /body/p[65]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-9.gif"⇒ "http://www.softether.org/@api/deki/files/115/=1-4-9.png" - /body/p[65]/a/@title: nothing ⇒ "1-4-9.png"
- /body/p[65]/a/img/@alt:
"Click to enlarge."⇒ "1-4-9.png" - /body/p[65]/a/img/@border:
"2"⇒ nothing - /body/p[65]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-9_small.jpg"⇒ "/@api/deki/files/115/=1-4-9.png?size=webview" - /body/p[65]/a/img/@class: nothing ⇒ "internal default"
- /body/p[65]/a/img/@style: nothing ⇒ "width: 550px; height: 152px;"
- /body/p[66]/@style: nothing ⇒ "text-align: center; "
- /body/p[73]/a/@class:
" external"⇒ nothing - /body/p[73]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-10.gif"⇒ "http://www.softether.org/@api/deki/files/116/=1-4-10.png" - /body/p[73]/a/@title: nothing ⇒ "1-4-10.png"
- /body/p[73]/a/img/@alt:
"Click to enlarge."⇒ "1-4-10.png" - /body/p[73]/a/img/@border:
"2"⇒ nothing - /body/p[73]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-10_small.jpg"⇒ "/@api/deki/files/116/=1-4-10.png?size=webview" - /body/p[73]/a/img/@class: nothing ⇒ "internal default"
- /body/p[73]/a/img/@style: nothing ⇒ "width: 550px; height: 370px;"
- /body/p[74]/@style: nothing ⇒ "text-align: center; "
- /body/p[81]/a/@class:
" external"⇒ nothing - /body/p[81]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-11.gif"⇒ "http://www.softether.org/@api/deki/files/117/=1-4-11.png" - /body/p[81]/a/@title: nothing ⇒ "1-4-11.png"
- /body/p[81]/a/img/@alt:
"Click to enlarge."⇒ "1-4-11.png" - /body/p[81]/a/img/@border:
"2"⇒ nothing - /body/p[81]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-11_small.jpg"⇒ "/@api/deki/files/117/=1-4-11.png?size=webview" - /body/p[81]/a/img/@class: nothing ⇒ "internal default"
- /body/p[81]/a/img/@style: nothing ⇒ "width: 550px; height: 272px;"
- /body/p[82]/@style: nothing ⇒ "text-align: center; "
- /body/p[88]/a/@class:
" external"⇒ nothing - /body/p[88]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-12.gif"⇒ "http://www.softether.org/@api/deki/files/118/=1-4-12.png" - /body/p[88]/a/@title: nothing ⇒ "1-4-12.png"
- /body/p[88]/a/img/@alt:
"Click to enlarge."⇒ "1-4-12.png" - /body/p[88]/a/img/@border:
"2"⇒ nothing - /body/p[88]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-12_small.jpg"⇒ "/@api/deki/files/118/=1-4-12.png?size=webview" - /body/p[88]/a/img/@class: nothing ⇒ "internal default"
- /body/p[88]/a/img/@style: nothing ⇒ "width: 550px; height: 365px;"
- /body/p[89]/@style: nothing ⇒ "text-align: center; "
- /body/p[93]/a/@class:
" external"⇒ nothing - /body/p[93]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/1-4-13.gif"⇒ "http://www.softether.org/@api/deki/files/119/=1-4-13.png" - /body/p[93]/a/@title: nothing ⇒ "1-4-13.png"
- /body/p[93]/a/img/@alt:
"Click to enlarge."⇒ "1-4-13.png" - /body/p[93]/a/img/@border:
"2"⇒ nothing - /body/p[93]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/1-4-13_small.jpg"⇒ "/@api/deki/files/119/=1-4-13.png?size=webview" - /body/p[93]/a/img/@class: nothing ⇒ "internal default"
- /body/p[93]/a/img/@style: nothing ⇒ "width: 550px; height: 321px;"
- /body/p[94]/@style: nothing ⇒ "text-align: center; "
Version from 02:43, 2 Mar 2013
...
...
...
The switching Hub used by Ethernet (layer 2 switch) constructs a network by Ethernet and is an important peripheral device for communication. Switching HUBs have multiple ports (usually 8 ports, but can have from tens to hundreds. By connecting a compute to the Ethernet by network cable, etc., a physical network is connected between the switching Hub and computer's network adapter, thus enabling Ethernet communications by layer 2.
The ports of a switching Hub can also be connected to the ports of another switching Hub. Even though the connected switching HUBs were originally separate Ethernet networks, by connecting them by network cable, they work like a single Ethernet network. This is called "cascade connection".
The computers connected to the switching HUBs on the left and right in the following figure can communicate freely with each other.
...
Switching HUBs constantly recognize in advance which computers with what sort of MAC address are connected to the respective ports and maintain the information in an internal database. This is called a "MAC address table".
...
As was previously mentioned, the method of connecting two segments configured of two switching HUBs and using as a single segment is called "cascade connection". Cascade connection can consist of an unlimited number of cascades provided the physical limit established for Ethernet is not exceeded. The fact that cascade connection can be accomplished easily is one of the greatest features of using Ethernet. By cascade connecting another switching Hub to one for which the number of ports has become insufficient, you can increase the number of available ports and increase the number of computers that can be connected to the network.
...
Cascade connection and bridge connection are technically similar connection methods, but whereas cascade connection indicates connecting switching HUBs to construct a single large segment from the beginning, bridge connection means connecting networks to be used as two segments that are physically separate and are administered separately.
...
Virtual Hub is one of the most important functions of SoftEther VPN. Virtual Hub implements the same level of functions as the existing common layer 2 switching Hub as software. Virtual Hub has a MAC address learning function and frame exchange/delivery functions based on learning. Whereas conventional switching HUBs used to handle this processing as hardware, with Virtual Hub of SoftEther VPN, the processing is handled as software.
...
SoftEther VPN Server can create multiple Virtual HUBs. You can create as many Virtual HUBs as memory space, CPU speed and specifications will permit. Each respective Virtual Hub conducts MAC address learning for virtual Ethernet frames flowing through the VPN. As a result virtual layer 2 Ethernet segments are realized by sending Ethernet frames to computers participating in other VPNs.
Creation and Administration of Multiple Virtual HUBs
If multiple Virtual HUBs are created within a single VPN server, those Virtual HUBs cannot communicate with each other. Consequently if multiple Virtual HUBs are created, it means multiple Ethernet segments are formed within the VPN Server.
...
|
...
These setting contents are completely independent for each Virtual Hub, and administration is divided into units so each individual administrator can administrate separately. Administrators of VPN Servers at large can manage all Virtual HUBs, but administrators granted authority concerning some Virtual HUBs from the VPN Server administrator can manage only those Virtual HUBs and are unable to manage other Virtual HUBs.
...
Method of Connecting Virtual HUBs to each other
Virtual HUBs can be cascade connected to Virtual HUBs operating on the same VPN Server or VPN Server operating on another computer, and the cascade connected Virtual HUBs that were originally separate segments are joined to work as a single segment.
For Virtual HUBs operating on the same VPN Server, via virtual layer 3 switch by IP routing, network among Virtual HUBs can be connected by layer 3.
...
|
...
...
With SoftEther VPN Server, you can create multiple Virtual HUBs and operate them together. In the initial state however Virtual HUBs have only independent layer 2 segments, and although computers connected to the same Virtual Hub can communicate freely, computers connected to separate Virtual HUBs cannot communicate with each other.
...
Using the virtual layer 3 switch function of SoftEther VPN Server enables IP routing among multiple Virtual HUBs. If conducting IP routing among multiple Virtual HUBs with the previous version of SoftEther 1.0, etc., you had to conduct IP routing with a physical layer 3 switch or special router by bridge connecting each respective Virtual Hub segment to a physical Ethernet segment. SoftEther VPN Server's support of virtual layer 3 switch function enables network administrators to easily realize communication among Virtual HUBs by IP routing among multiple Virtual HUBs.
...
By connecting Virtual Hub and physical existing LAN by multiple bases and by furthermore cascade connecting Virtual HUBs existing physical LAN of multiple bases can be easily made a single segment via Internet to realize base-to-base VPN.
...
...
...
...
Version as of 02:58, 2 Mar 2013
...
Switching Hub and network adapter for Ethernet.
...
A Ethernet frame (MAC frame).
...
The switching Hub used by Ethernet (layer 2 switch) constructs a network by Ethernet and is an important peripheral device for communication. Switching Hubs have multiple ports (usually 8 ports, but can have from tens to hundreds. By connecting a compute to the Ethernet by network cable, etc., a physical network is connected between the switching Hub and computer's network adapter, thus enabling Ethernet communications by layer 2.
The ports of a switching Hub can also be connected to the ports of another switching Hub. Even though the connected switching Hubs were originally separate Ethernet networks, by connecting them by network cable, they work like a single Ethernet network. This is called "cascade connection".
The computers connected to the switching Hubs on the left and right in the following figure can communicate freely with each other.
...
Segment junction by cascade connection of switching hubs.
...
Switching Hubs constantly recognize in advance which computers with what sort of MAC address are connected to the respective ports and maintain the information in an internal database. This is called a "MAC address table".
...
As was previously mentioned, the method of connecting two segments configured of two switching Hubs and using as a single segment is called "cascade connection". Cascade connection can consist of an unlimited number of cascades provided the physical limit established for Ethernet is not exceeded. The fact that cascade connection can be accomplished easily is one of the greatest features of using Ethernet. By cascade connecting another switching Hub to one for which the number of ports has become insufficient, you can increase the number of available ports and increase the number of computers that can be connected to the network.
...
Cascade connection and bridge connection are technically similar connection methods, but whereas cascade connection indicates connecting switching Hubs to construct a single large segment from the beginning, bridge connection means connecting networks to be used as two segments that are physically separate and are administered separately.
...
Virtual Hub is one of the most important functions of SoftEther VPN. Virtual Hub implements the same level of functions as the existing common layer 2 switching Hub as software. Virtual Hub has a MAC address learning function and frame exchange/delivery functions based on learning. Whereas conventional switching Hubs used to handle this processing as hardware, with Virtual Hub of SoftEther VPN, the processing is handled as software.
...
SoftEther VPN Server can create multiple Virtual Hubs. You can create as many Virtual Hubs as memory space, CPU speed and specifications will permit. Each respective Virtual Hub conducts MAC address learning for virtual Ethernet frames flowing through the VPN. As a result virtual layer 2 Ethernet segments are realized by sending Ethernet frames to computers participating in other VPNs.
...
Connection between Virtual Hubs or between Virtual Network Adapters.
Creation and Administration of Multiple Virtual Hubs
If multiple Virtual Hubs are created within a single VPN server, those Virtual Hubs cannot communicate with each other. Consequently if multiple Virtual Hubs are created, it means multiple Ethernet segments are formed within the VPN Server.
...
Segment separation by Virtual Hub within VPN Server.
...
These setting contents are completely independent for each Virtual Hub, and administration is divided into units so each individual administrator can administrate separately. Administrators of VPN Servers at large can manage all Virtual Hubs, but administrators granted authority concerning some Virtual Hubs from the VPN Server administrator can manage only those Virtual Hubs and are unable to manage other Virtual Hubs.
...
Method of Connecting Virtual Hubs to each other
Virtual Hubs can be cascade connected to Virtual Hubs operating on the same VPN Server or VPN Server operating on another computer, and the cascade connected Virtual Hubs that were originally separate segments are joined to work as a single segment.
For Virtual Hubs operating on the same VPN Server, via virtual layer 3 switch by IP routing, network among Virtual Hubs can be connected by layer 3.
...
SoftEther VPN Virtual Network Adapter recognized as a network adapter by the operating system.
...
Property window of Virtual Network Adapter.
...
With SoftEther VPN Server, you can create multiple Virtual Hubs and operate them together. In the initial state however Virtual Hubs have only independent layer 2 segments, and although computers connected to the same Virtual Hub can communicate freely, computers connected to separate Virtual Hubs cannot communicate with each other.
...
Using the virtual layer 3 switch function of SoftEther VPN Server enables IP routing among multiple Virtual Hubs. If conducting IP routing among multiple Virtual Hubs with the previous version of SoftEther 1.0, etc., you had to conduct IP routing with a physical layer 3 switch or special router by bridge connecting each respective Virtual Hub segment to a physical Ethernet segment. SoftEther VPN Server's support of virtual layer 3 switch function enables network administrators to easily realize communication among Virtual Hubs by IP routing among multiple Virtual Hubs.
...
IP routing among Virtual Hubs by virtual layer 3 switch.
...
By connecting Virtual Hub and physical existing LAN by multiple bases and by furthermore cascade connecting Virtual Hubs existing physical LAN of multiple bases can be easily made a single segment via Internet to realize base-to-base VPN.
...
Example of base-to-base connection by SoftEther VPN.
...
Computer-to-computer VPN.
...
Remote access VPN.
...
Base-to-base VPN of ordinary scale.
...
Base-to-base VPN of large scale.