Table of contents
Combined revision comparison
...
With SoftEther VPN protocol, packets that flows through the actual physical network for communication between SoftEther VPN Server and VPN connection source computer (VPN session) are encapsulated as TCP/IP packets and are generated by sender. The TCP/IP packets that is received by the reception side will beare encapsulated and de-capsulated. All TCP/IP communication is encrypted by Secure Socket Layer (SSL) and an electronic signature can be added.
For communication between SoftEther VPN Server and VPN connection source computer, communication can be carried out by one TCP/IP connection per VPN session. When, but if the user so desires, multiple TCP/IP connections can be established and the load distribution can be performed for communication data among these TCP/IP connections. Also the, delay can be managed, transmission sequence automatically adjusted, network line used more efficiently ,and throughput and response enhanced. Data transmission direction (full duplex or half duplex) and life until cut off can also be set for each TCP/IP connection. For details see 2.1 VPN Communication Protocol and 4.4 Making Connection to VPN Server.
All data contents for data transmission of SoftEther VPN protocol is encrypted by SSL and it is compressed by a data compression algorithm. When it is used for low-speed lines such as modems or ISDN or PHS, data compression may theoretically function effectively while transmitting inwhen transmitting large quantities of data. Compression can be used simultaneously with encryption. For more information on data compression, see 2.1 VPN Communication Protocol and 4.4 Making Connection to VPN Server.
...
Just like a physical switching hub, Virtual Hub automatically conducts MAC address learning and associates the learned MAC addresses with VPN sessions. When Ethernet frames that is neededneed to be processed arrive, the destination MAC address of the Ethernet frame can be read and switched to a suitable matching VPN session. This virtual Ethernet frame switching processing is the most important function of Virtual Hub and it is the most substantial part of VPN communications by SoftEther VPN.
MAC address tables which is managed by Virtual Hub are automatically updated and it'sthe actual network status is appliesapplied as much as possible. The Virtual Hub administrator can display the MAC address table an can freely delete entries.
...
SoftEther VPN Server accepts connection from software that is compatible with SoftEther VPN protocol that is running on other computers (there will be no problem evenis no problem if running by localhost). There are three types of this software: SoftEther VPN Server, SoftEther VPN and SoftEther VPN Bridge (new software or dedicated hardware that supports SoftEther VPN may be developed and offered by SoftEther VPN Project or third party in the future).
...
All VPN connections from these three types of softwaressoftware are conducted by SoftEther VPN protocol; the communication contents and nature are the same regardless of the type of software and purpose of communication.
...
Connection from SoftEther VPN Client is generally connection from Virtual Network Adapter attempting to connect to Virtual Hub. In other words, whenif VPN Client is installed on client computers of end users using VPN communications and VPN Server is registered as the connection destination of VPN Client, the Virtual Network Adapter of the computer connects to Virtual Hub operating by VPN Server, and it can carry out the same communication as for example a network adapter connected to a physical switching hub by network cable.
As a special usage method, it is going to be possible to bridge connection by layer 2 between VPN Client computer Virtual Network Adapter and existing physical network adapter connected to the computer. As for, theis possible. The bridge function of the operating system is going to be useused for this. With SoftEther 1.0, bridging between Virtual Hub and physical network adapter has beenwas often accomplished by this method. With SoftEther VPN, however, because bridging could be accomplished easier and faster by local bridge connection function of VPN Server or VPN Bridge, this method ceased to be used frequently.
...
Whele SoftEther VPN Bridge operating at a base in remote location, itat a remote location can be connected to SoftEther VPN Server by cascading thecascade connection. By connecting the two Virtual Hubs on the VPN Server and VPN Bridge sides to existing physical LAN of both bases, you will be able tocan connect the two bases by VPN connection. This method is often used for base-to-base VPN connection.
...
Because SoftEther VPN Bridge is software that limits just one part of SoftEther VPN Server, as it has been described ealier, thepreviously described connection method from SoftEther VPN Bridge works the same for cascade connection from one SoftEther VPN Server to another and it can be used as such.
...
As it iswas explained in 1.6.6, VPN connection of VPN Client / VPN Server / VPN Bridge, etc., operating on another computer to VPN Server willis established and managed as a VPN session for all Virtual Hubs.
VPN Server is basically treated asthe same for VPN sessions of any SoftEther VPN protocol, but that does not mean it is interested in the type of VPN software of the VPN session connection source or the type of network of the VPN session destination.
...
VPN session in the client mode is primarily applied to VPN sessions connected from VPN Client to VPN Server. In thisThis way of using conventional VPN Client willis primarily usage as VPN client for remote access VPN by installing VPN Client on client computers in a remote location, creating Virtual Hub and connecting the Virtual Hub to VPN Server.
With VPN sessions are established by connection from conventional VPN Client, only one Ethernet device with a MAC address should be connected to VPN on the VPN Client side. In other words, Virtual Network Adapter device driver that is used by VPN Client for connection, is simply connected to Virtual Hub, and the MAC address will allottallotted to the Virtual Network Adapter which is supposed to be the only network adapter existing on the client side for the concerned VPN session.
Users who actually use computers installed with VPN Client, however ithowever can bridge connect to a separate physical network adapter on the client computer side using function of the operating system and it can connect to another IP network by using the IP routing function of the operating system. If this operation is randomly performed by users having VPN Client, the user may unintentionally alter the network topology on the VPN administrator side, and they could destroy the uniformity and manageability of the VPN network as a whole.
Thus in a client mode session (i.e., VPN session connected from VPN Client layer 2 bridge or layer 3 routing on the client side of the VPN session) is forbidden as a rule. This makes it impossible for users of VPN Client connected to SoftEther VPN Server to connect Virtual Network Adapter on the client computer side to another network. In other words alteration of the network topology or unintentional computer connection to VPN by administrator can be prevented.
...
Version from 23:26, 22 Jan 2014
...
With SoftEther VPN protocol, packets that flows through the actual physical network for communication between SoftEther VPN Server and VPN connection source computer (VPN session) are encapsulated as TCP/IP packets and are generated by sender. The TCP/IP packets that is received by the reception side are encapsulated and de-capsulated. All TCP/IP communication is encrypted by Secure Socket Layer (SSL) and an electronic signature can be added.
For communication between SoftEther VPN Server and VPN connection source computer, communication can be carried out by one TCP/IP connection per VPN session, but if the user so desires, multiple TCP/IP connections can be established and load distribution can be performed for communication data among these TCP/IP connections, delay can be managed, transmission sequence automatically adjusted, network line used more efficiently and throughput and response enhanced. Data transmission direction (full duplex or half duplex) and life until cut off can also be set for each TCP/IP connection. For details see 2.1 VPN Communication Protocol and 4.4 Making Connection to VPN Server.
All data contents for data transmission of SoftEther VPN protocol is encrypted by SSL and it is compressed by a data compression algorithm. When used for low-speed lines such as modems or ISDN or PHS, data compression may theoretically function effectively when transmitting large quantities of data. Compression can be used simultaneously with encryption. For more information on data compression, see 2.1 VPN Communication Protocol and 4.4 Making Connection to VPN Server.
...
Just like a physical switching hub, Virtual Hub automatically conducts MAC address learning and associates the learned MAC addresses with VPN sessions. When Ethernet frames that need to be processed arrive, the destination MAC address of the Ethernet frame can be read and switched to a suitable matching VPN session. This virtual Ethernet frame switching processing is the most important function of Virtual Hub and is the most substantial part of VPN communications by SoftEther VPN.
MAC address tables managed by Virtual Hub are automatically updated and the actual network status is applied as much as possible. The Virtual Hub administrator can display the MAC address table an can freely delete entries.
...
SoftEther VPN Server accepts connection from software that is compatible with SoftEther VPN protocol that is running on other computers (there is no problem if running by localhost). There are three types of this software: SoftEther VPN Server, SoftEther VPN and SoftEther VPN Bridge (new software or dedicated hardware that supports SoftEther VPN may be developed and offered by SoftEther VPN Project or third party in the future).
...
All VPN connections from these three types of software are conducted by SoftEther VPN protocol; the communication contents and nature are the same regardless of the type of software and purpose of communication.
...
Connection from SoftEther VPN Client is generally connection from Virtual Network Adapter attempting to connect to Virtual Hub. In other words if VPN Client is installed on client computers of end users using VPN communications and VPN Server is registered as the connection destination of VPN Client, the Virtual Network Adapter of the computer connects to Virtual Hub operating by VPN Server, and can carry out the same communication as for example a network adapter connected to a physical switching hub by network cable.
As a special usage method, bridge connection by layer 2 between VPN Client computer Virtual Network Adapter and existing physical network adapter connected to the computer is possible. The bridge function of the operating system is used for this. With SoftEther 1.0, bridging between Virtual Hub and physical network adapter was often accomplished by this method. With SoftEther VPN, however, because bridging could be accomplished easier and faster by local bridge connection function of VPN Server or VPN Bridge, this method ceased to be used frequently.
...
SoftEther VPN Bridge operating at a base at a remote location can be connected to SoftEther VPN Server by cascade connection. By connecting the two Virtual Hubs on the VPN Server and VPN Bridge sides to existing physical LAN of both bases, you can connect the two bases by VPN connection. This method is often used for base-to-base VPN connection.
...
Because SoftEther VPN Bridge is software that limits just one part of SoftEther VPN Server, previously described connection method from SoftEther VPN Bridge works the same for cascade connection from one SoftEther VPN Server to another and can be used as such.
...
As was explained in 1.6.6, VPN connection of VPN Client / VPN Server / VPN Bridge, etc., operating on another computer to VPN Server is established and managed as a VPN session for all Virtual Hubs.
VPN Server is basically treated the same for VPN sessions of any SoftEther VPN protocol, but that does not mean it is interested in the type of VPN software of the VPN session connection source or the type of network of the VPN session destination.
...
VPN session in the client mode is primarily applied to VPN sessions connected from VPN Client to VPN Server. This way of using conventional VPN Client is primarily usage as VPN client for remote access VPN by installing VPN Client on client computers in a remote location, creating Virtual Hub and connecting the Virtual Hub to VPN Server.
With VPN sessions established by connection from conventional VPN Client, only one Ethernet device with a MAC address should be connected to VPN on the VPN Client side. In other words, Virtual Network Adapter device driver used by VPN Client for connection is simply connected to Virtual Hub, and the MAC address allotted to the Virtual Network Adapter is supposed to be the only network adapter existing on the client side for the concerned VPN session.
...
Version as of 17:03, 30 Jan 2014
...
With SoftEther VPN protocol, packets that flows through the actual physical network for communication between SoftEther VPN Server and VPN connection source computer (VPN session) are encapsulated as TCP/IP packets and are generated by sender. The TCP/IP packets that is received by the reception side will be encapsulated and de-capsulated. All TCP/IP communication is encrypted by Secure Socket Layer (SSL) and an electronic signature can be added.
For communication between SoftEther VPN Server and VPN connection source computer, communication can be carried out by one TCP/IP connection per VPN session. When the user so desires, multiple TCP/IP connections can be established and the load distribution can be performed for communication data among these TCP/IP connections. Also the delay can be managed, transmission sequence automatically adjusted, network line used more efficiently, throughput and response enhanced. Data transmission direction (full duplex or half duplex) and life until cut off can also be set for each TCP/IP connection. For details see 2.1 VPN Communication Protocol and 4.4 Making Connection to VPN Server.
All data contents for data transmission of SoftEther VPN protocol is encrypted by SSL and it is compressed by a data compression algorithm. When it is used for low-speed lines such as modems or ISDN or PHS, data compression may theoretically function effectively while transmitting in large quantities of data. Compression can be used simultaneously with encryption. For more information on data compression, see 2.1 VPN Communication Protocol and 4.4 Making Connection to VPN Server.
...
Just like a physical switching hub, Virtual Hub automatically conducts MAC address learning and associates the learned MAC addresses with VPN sessions. When Ethernet frames that is needed to be processed arrive, the destination MAC address of the Ethernet frame can be read and switched to a suitable matching VPN session. This virtual Ethernet frame switching processing is the most important function of Virtual Hub and it is the most substantial part of VPN communications by SoftEther VPN.
MAC address tables which is managed by Virtual Hub are automatically updated and it's actual network status is applies as much as possible. The Virtual Hub administrator can display the MAC address table an can freely delete entries.
...
SoftEther VPN Server accepts connection from software that is compatible with SoftEther VPN protocol that is running on other computers (there will be no problem even if running by localhost). There are three types of this software: SoftEther VPN Server, SoftEther VPN and SoftEther VPN Bridge (new software or dedicated hardware that supports SoftEther VPN may be developed and offered by SoftEther VPN Project or third party in the future).
...
All VPN connections from these three types of softwares are conducted by SoftEther VPN protocol; the communication contents and nature are the same regardless of the type of software and purpose of communication.
...
Connection from SoftEther VPN Client is generally connection from Virtual Network Adapter attempting to connect to Virtual Hub. In other words, when VPN Client is installed on client computers of end users using VPN communications and VPN Server is registered as the connection destination of VPN Client, the Virtual Network Adapter of the computer connects to Virtual Hub operating by VPN Server, and it can carry out the same communication as for example a network adapter connected to a physical switching hub by network cable.
As a special usage method, it is going to be possible to bridge connection by layer 2 between VPN Client computer Virtual Network Adapter and existing physical network adapter connected to the computer. As for, the bridge function of the operating system is going to be use for this. With SoftEther 1.0, bridging between Virtual Hub and physical network adapter has been often accomplished by this method. With SoftEther VPN, however, because bridging could be accomplished easier and faster by local bridge connection function of VPN Server or VPN Bridge, this method ceased to be used frequently.
...
Whele SoftEther VPN Bridge operating at a base in remote location, it can be connected to SoftEther VPN Server by cascading the connection. By connecting the two Virtual Hubs on the VPN Server and VPN Bridge sides to existing physical LAN of both bases, you will be able to connect the two bases by VPN connection. This method is often used for base-to-base VPN connection.
...
Because SoftEther VPN Bridge is software that limits just one part of SoftEther VPN Server, as it has been described ealier, the connection method from SoftEther VPN Bridge works the same for cascade connection from one SoftEther VPN Server to another and it can be used as such.
...
As it is explained in 1.6.6, VPN connection of VPN Client / VPN Server / VPN Bridge, etc., operating on another computer to VPN Server will established and managed as a VPN session for all Virtual Hubs.
VPN Server is basically treated as same for VPN sessions of any SoftEther VPN protocol, but that does not mean it is interested in the type of VPN software of the VPN session connection source or the type of network of the VPN session destination.
...
VPN session in the client mode is primarily applied to VPN sessions connected from VPN Client to VPN Server. In this way of using conventional VPN Client will primarily usage as VPN client for remote access VPN by installing VPN Client on client computers in a remote location, creating Virtual Hub and connecting the Virtual Hub to VPN Server.
With VPN sessions are established by connection from conventional VPN Client, only one Ethernet device with a MAC address should be connected to VPN on the VPN Client side. In other words, Virtual Network Adapter device driver that is used by VPN Client for connection, is simply connected to Virtual Hub, and the MAC address will allott to the Virtual Network Adapter which is supposed to be the only network adapter existing on the client side for the concerned VPN session.
Users who actually use computers installed with VPN Client, however it can bridge connect to a separate physical network adapter on the client computer side using function of the operating system and it can connect to another IP network by using the IP routing function of the operating system. If this operation is randomly performed by users having VPN Client, the user may unintentionally alter the network topology on the VPN administrator side, and they could destroy the uniformity and manageability of the VPN network as a whole.
Thus in a client mode session (i.e., VPN session connected from VPN Client layer 2 bridge or layer 3 routing on the client side of the VPN session) is forbidden as a rule. This makes it impossible for users of VPN Client connected to SoftEther VPN Server to connect Virtual Network Adapter on the client computer side to another network. In other words alteration of the network topology or unintentional computer connection to VPN by administrator can be prevented.
...
