Table of contents
Combined revision comparison
...
In 1.4 VPN Processing Principle and Communication Method, it was explained that along with emulating a conventional Ethernet switching hub, SoftEther VPN can be a accept connection from a VPN connection source just as with a physical connection point of a conventional switching hub.
Physical network adapters and switching hubs are connected to each other by network cable, but in the case of SoftEther VPN, but when a Virtual Network Adapter or Virtual Hub of another computer is connected to a Virtual Hub, the communication contents are tunneled and flow through a physical network as TCP/IP-based SoftEther VPN protocol. Consequently each and every SoftEther VPN protocol connection is substantially ,the same as a network cable is to physical Ethernet, and can be expressed as a connection unit for Ethernet.
With SoftEther VPN, when VPN Client connects by VPN to VPN Server or when Virtual Hubs connect to each other by cascade connection, a transmission path for VPN communications is established, and in the case where encapsulated Ethernet frames are transmitted, a VPN session is established between VPN connection source and VPN Server in all cases. In addition to this, although it does not physically exist, virtual hosts or DHCP servers that is connected to a Virtual Hub by software internally generate the VPN sessions.
...
SoftEther VPN Server stands by for connection with multiple TCP/IP ports open as a port number for accepting VPN connection from the VPN connection source computer. The list of port numbers that are used can freely be established or modify by the VPN Server administratorVPN Server administrator can freely establish or modify the list of port numbers used at this time .
The TCP/IP port numbers to open theopento stand by for VPN connection from other computers are called "listener ports". The following three TCP/IP ports are allocated as listener ports by default.
- Port No. 5555 (This port number is used exclusively by SoftEther VPN; the number 5555 mean just for easy remembrance
is used so it is easy to remember.) - Port No. 443 (The number of This port number is the same that of "HTTPS protocol". It will be convenient for you
port number as that of HTTPS protocol. It isconvenient 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 will be convenient for you
isconvenient to make relay equipment recognize TCP/IP connection as TELNETS protocol for VPN session.)
By opening multiple TCP/IP ports, other computers that attemptsattempt to connect to that VPN server, SoftEther VPN Server will execut theexecuted connection to the easiest port number to connect to the accordingaccording to network environment, proxy servers and limitations such as firewalls. No matter which TCP/IP port you connect to, the functions and performance are the same after the VPN session has beenis established. SoftEther VPN Server will treattreats each TCP/IP listener port equally.
...
As it was described beforewasdescribed in 1.4 VPN Processing Principle and Communication Method, SoftEther VPN Server can operate multiple Virtual Hubs within a single server process.
Computers that attemptsattempt to connect by VPN to VPN Server, it will chose the specific Virtual Hubs that isspecify one of the Virtual Hubs operating in VPN Server and can beconnect toconnecttoit.
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 it 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 the VPN connection to the Virtual Hub, an new VPN session will beis established and VPN communication will startstarts.
During the time until connectconnection to the Virtual Hub has been completed, there will beis completed, there is no VPN communication between the VPN connection source computer and VPN Server (sending/receiving of Ethernet frames); VPN data communication is carried out after user authentication has been completed. Processing during connection to Virtual Hub before completion of user authentication by SoftEther VPN protocol during negotiation VPN is actually completed, session is established, and state where VPN communication can be used is expressed as "established".
...
With SoftEther VPN protocol, packets that flowsflow 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.
...
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.
...
Version from 18:50, 3 Mar 2013
...
Physical network adapters and switching hubs are connected to each other by network cable, but in the case of SoftEther VPN, but when a Virtual Network Adapter or Virtual Hub of another computer is connected to a Virtual Hub, the communication contents are tunneled and flow through a physical network as TCP/IP-based SoftEther VPN protocol. Consequently each and every SoftEther VPN protocol connection is substantially the same as a network cable is to physical Ethernet, and can be expressed as a connection unit for Ethernet.
...
SoftEther VPN Server stands by for connection with multiple TCP/IP ports open as a port number for accepting VPN connection from the VPN connection source computer. The VPN Server administrator can freely establish or modify the list of port numbers used at this time.
TCP/IP port numbers open to stand by for VPN connection from other computers are called "listener ports". The following three TCP/IP ports are allocated as listener ports by default.
- 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 isconvenient 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
isconvenient to make relay equipment recognize TCP/IP connection as TELNETS protocol for VPN session.)
By opening multiple TCP/IP ports, other computers that attempt to connect to that VPN server, SoftEther VPN Server executed connection to the easiest port number to connect to according to network environment, proxy servers and limitations such as firewalls. No matter which TCP/IP port you connect to, the functions and performance are the same after the VPN session is established. SoftEther VPN Server treats each TCP/IP listener port equally.
...
Computers that attempt to connect by VPN to VPN Server specify one of the Virtual Hubs operating in VPN Server and connect toit.
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.
During the time until connection to the Virtual Hub is completed, there is no VPN communication between the VPN connection source computer and VPN Server (sending/receiving of Ethernet frames); VPN data communication is carried out after user authentication has been completed. Processing during connection to Virtual Hub before completion of user authentication by SoftEther VPN protocol during negotiation VPN is actually completed, session is established, and state where VPN communication can be used is expressed as "established".
...
With SoftEther VPN protocol, packets that flow 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. TCP/IP packets 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.
...
Version as of 15:10, 21 Jan 2014
...
In 1.4 VPN Processing Principle and Communication Method, it was explained that along with emulating a conventional Ethernet switching hub, SoftEther VPN can be a accept connection from a VPN connection source just as with a physical connection point of a conventional switching hub.
Physical network adapters and switching hubs are connected to each other by network cable, but in the case of SoftEther VPN, when a Virtual Network Adapter or Virtual Hub of another computer is connected to a Virtual Hub, the communication contents are tunneled and flow through a physical network as TCP/IP-based SoftEther VPN protocol. Consequently each and every SoftEther VPN protocol connection is substantially, same as a network cable is to physical Ethernet, and can be expressed as a connection unit for Ethernet.
With SoftEther VPN, when VPN Client connects by VPN to VPN Server or when Virtual Hubs connect to each other by cascade connection, a transmission path for VPN communications is established, and in the case where encapsulated Ethernet frames are transmitted, a VPN session is established between VPN connection source and VPN Server in all cases. In addition to this, although it does not physically exist, virtual hosts or DHCP servers that is connected to a Virtual Hub by software internally generate the VPN sessions.
...
SoftEther VPN Server stands by for connection with multiple TCP/IP ports open as a port number for accepting VPN connection from the VPN connection source computer. The list of port numbers that are used can freely be established or modify by the VPN Server administrator .
The TCP/IP port numbers to open the stand by for VPN connection from other computers are called "listener ports". The following three TCP/IP ports are allocated as listener ports by default.
- Port No. 5555 (This port number is used exclusively by SoftEther VPN; the number 5555 mean just for easy remembrance.)
- Port No. 443 (The number of This port number is the same that of "HTTPS protocol". It will be convenient for you 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 will be convenient for you to make relay equipment recognize TCP/IP connection as TELNETS protocol for VPN session.)
By opening multiple TCP/IP ports, other computers that attempts to connect to that VPN server, SoftEther VPN Server will execut the connection to the easiest port number to connect to the according network environment, proxy servers and limitations such as firewalls. No matter which TCP/IP port you connect to, the functions and performance are the same after the VPN session has been established. SoftEther VPN Server will treat each TCP/IP listener port equally.
...
As it was described before in 1.4 VPN Processing Principle and Communication Method, SoftEther VPN Server can operate multiple Virtual Hubs within a single server process.
Computers that attempts to connect by VPN to VPN Server, it will chose the specific Virtual Hubs that is operating in VPN Server and can beconnect to.
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 it 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 the VPN connection to the Virtual Hub, an new VPN session will be established and VPN communication will start.
During the time until connect to the Virtual Hub has been completed, there will be no VPN communication between the VPN connection source computer and VPN Server (sending/receiving of Ethernet frames); VPN data communication is carried out after user authentication has been completed. Processing during connection to Virtual Hub before completion of user authentication by SoftEther VPN protocol during negotiation VPN is actually completed, session is established, and state where VPN communication can be used is expressed as "established".
...
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.
...
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.
...
