1.6 VPN Communication Details

Version from 02:58, 2 Mar 2013

...

In #1.4.2#, it was explained that along with emulating a conventional Ethernet switching hub, SoftEther VPN can accept connection from a VPN connection source just as with a physical connection point of a conventional switching hub.

...

For more information on VPN sessions, see the rest of this chapter and #3.4.5#, etc.

...

• Port No. 8888 (This port number is used exclusively by SoftEther VPN; the number 8888 is used so it is easy to remember.)
• Port No. 443 (This port number is the same port number as that of HTTPS protocol. It is convenient to make relay equipment recognize TCP/IP connection as HTTPS protocol for VPN session.)
• Port No. 992 (This port number is the same port number as that of TELNETS protocol, which is hardly used anymore. It is convenient to make relay equipment recognize TCP/IP connection as TELNETS protocol for VPN session.)

...

For more information on listener ports, see #3.3.6#.

...

As was described in #1.4.2#, SoftEther VPN Server can operate multiple Virtual Hubs within a single server process.

...

When attempting to connect to a Virtual Hub, user authentication such as explained in #1.5.1# has to be carried out. User information is managed separately for each Virtual Hub and has to be set in advance by each SoftEther VPN Server and Virtual Hub administrator. As a result of carrying out user authentication according to user information in the security account database that exists for each Virtual Hub, if the VPN Server recognizes the VPN connection as proper, the VPN Server accepts VPN connection to the Virtual Hub, an new VPN session is established and VPN communication starts.

...

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.3# and #4.4.11#.

All data contents for data transmission of SoftEther VPN protocol is encrypted by SSL and 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.3# and #4.4.16#.

...

For more information on SoftEther VPN Bridge, see #5#.

...

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.

...

By selecting the bridge/router mode as the connection mode for advanced communication setting of VPN Client connection settings, client mode session limitations are canceled and bridge and routing on the VPN Client side become possible. For details see #4.4.17#.

If deny security policy bridge and router operation is enabled for user setting values registered for each Virtual Hub of SoftEther VPN Server, users cannot connect to VPN Server in bridge/router mode (error occurs for VPN connection). For more information on security policy, see #3.5.9#.

...

Setting on the VPN Client side is required to connect to from SoftEther VPN Client to Virtual Hub in the bridge/router mode. For details see #4.4.17#.

The administrator must establish security policy so the user can't connect to Virtual Hub created for use with general VPN connection in the bridge/router mode. For more information on security policy, see #3.5.9#.

...

1-6-8 Monitoring mode session.

...

For more information on these functions, see #3.6#.

...

For more information on cascade connection sessions, see #3.4.11#.

...

A SecureNAT session is a special session automatically created internally if the SecureNAT function, which is one of the Virtual Hub functions of SoftEther VPN Server or SoftEther VPN Bridge, is enabled. For more information on SecureNAT function, see #3.7#.

...

A virtual layer 3 switch session is a special session automatically created internally for connection between virtual layer 3 switch and Virtual Hub if virtual layer 3 switch function, which is a function of SoftEther VPN Server, is used. For more information on virtual layer 3 switch function, see #3.8#.

Version as of 00:44, 3 Mar 2013

...

In 1.4 VPN Processing Principle and Communication Method, it was explained that along with emulating a conventional Ethernet switching hub, SoftEther VPN can accept connection from a VPN connection source just as with a physical connection point of a conventional switching hub.

...

For more information on VPN sessions, see the rest of this chapter and 3.4 Virtual Hub Functions, etc.

...

• Port No. 5555 (This port number is used exclusively by SoftEther VPN; the number 5555 is used so it is easy to remember.)
• Port No. 443 (This port number is the same port number as that of HTTPS protocol. It is convenient to make relay equipment recognize TCP/IP connection as HTTPS protocol for VPN session.)
• Port No. 992 (This port number is the same port number as that of TELNETS protocol, which is hardly used anymore. It is convenient to make relay equipment recognize TCP/IP connection as TELNETS protocol for VPN session.)

...

For more information on listener ports, see 3.3 VPN Server Administration.

...

As was described in 1.4 VPN Processing Principle and Communication Method, SoftEther VPN Server can operate multiple Virtual Hubs within a single server process.

...

When attempting to connect to a Virtual Hub, user authentication such as explained in 1.5 Strong Security Features has to be carried out. User information is managed separately for each Virtual Hub and has to be set in advance by each SoftEther VPN Server and Virtual Hub administrator. As a result of carrying out user authentication according to user information in the security account database that exists for each Virtual Hub, if the VPN Server recognizes the VPN connection as proper, the VPN Server accepts VPN connection to the Virtual Hub, an new VPN session is established and VPN communication starts.

...

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 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.

...

For more information on SoftEther VPN Bridge, see 5. SoftEther VPN Bridge Manual.

...

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.

...

By selecting the bridge/router mode as the connection mode for advanced communication setting of VPN Client connection settings, client mode session limitations are canceled and bridge and routing on the VPN Client side become possible. For details see 4.4 Making Connection to VPN Server.

If deny security policy bridge and router operation is enabled for user setting values registered for each Virtual Hub of SoftEther VPN Server, users cannot connect to VPN Server in bridge/router mode (error occurs for VPN connection). For more information on security policy, see 3.5 Virtual Hub Security Features.

...

Setting on the VPN Client side is required to connect to from SoftEther VPN Client to Virtual Hub in the bridge/router mode. For details see 4.4 Making Connection to VPN Server.

The administrator must establish security policy so the user can't connect to Virtual Hub created for use with general VPN connection in the bridge/router mode. For more information on security policy, see 3.5 Virtual Hub Security Features.

...

For more information on these functions, see 3.6 Local Bridges.

...

For more information on cascade connection sessions, see 3.4 Virtual Hub Functions.

...

A SecureNAT session is a special session automatically created internally if the SecureNAT function, which is one of the Virtual Hub functions of SoftEther VPN Server or SoftEther VPN Bridge, is enabled. For more information on SecureNAT function, see 3.7 Virtual NAT & Virtual DHCP Servers.

...

A virtual layer 3 switch session is a special session automatically created internally for connection between virtual layer 3 switch and Virtual Hub if virtual layer 3 switch function, which is a function of SoftEther VPN Server, is used. For more information on virtual layer 3 switch function, see 3.8Virtual Layer 3 Switches.