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 SoftEther VPN are, but in the case being ready just in caseof SoftEther VPN, when a Virtual Network Adapter or Virtual Hub of another computer is connected to a Virtual Hub, the communication contentionscontents are tunneled and flow through a physical network as TCP/IP-based SoftEther VPN protocol. Consequently each and every SoftEther VPN protocol connections areconnection is substantially, same as a network cable foris to physical Ethernet, and it 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 are established. And whenis established, and in the case where encapsulated Ethernet frames are transmitted, a VPN session will beis 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 whichthat is connected to a Virtual Hub by software is internally generatinginternallygenerate the VPN sessions.
...
As it will be subsequently explained, the following seven types of sessionssession exist for SoftEther VPN. Concerning each respective session, with the exception of some special treatment, the Virtual Hub will handle all by theVirtualHubhandles all by same mechanism.
...
SoftEther VPN Server is the only software that can accept the VPN connection session from SoftEther VPN Client, SoftEther VPN Server and SoftEther VPN Bridge running on another computer.
SoftEther VPN Server stands by for the 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 which 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 now hardly used anymore. It will be convenient for you to make relay equipment recognize TCP/IP connection as TELNETS protocol for VPN session.)
...
As it was described earlierbefore 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 now available and operating in VPN Server and can be connect to.
When it is attempting to connect to a Virtual Hub, a user authentication, such as explained earlieruserauthenticationsuchasexplained in 1.5 Strong Security Features has to be carried out. A userUser 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 connectinguntil 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 wil beis carried out after user's authentication has been completed. Processing during connection to Virtual Hub before completion of user's 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".
...
Version from 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.
...
As will be subsequently explained, the following seven types of session exist for SoftEther VPN. Concerning each respective session, with the exception of some special treatment, Virtual Hub handles all by same mechanism.
...
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 be connect 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".
...
Version as of 23:26, 22 Jan 2014
...
Physical network adapters and switching hubs are connected to each other by network cable. But SoftEther VPN are being ready just in case, when a Virtual Network Adapter or Virtual Hub of another computer is connected to a Virtual Hub, the communication contentions are tunneled and flow through a physical network as TCP/IP-based SoftEther VPN protocol. Consequently each and every SoftEther VPN protocol connections are substantially, same as a network cable for physical Ethernet, and it 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 are established. And when encapsulated Ethernet frames are transmitted, a VPN session will be 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 which is connected to a Virtual Hub by software is internally generating the VPN sessions.
...
As it will be subsequently explained, the following seven types of sessions exist for SoftEther VPN. Concerning each respective session, with the exception of some special treatment, the Virtual Hub will handle all by the same mechanism.
...
SoftEther VPN Server is the only software that can accept the VPN connection session from SoftEther VPN Client, SoftEther VPN Server and SoftEther VPN Bridge running on another computer.
SoftEther VPN Server stands by for the 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 which 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 now hardly used anymore. It will be convenient for you to make relay equipment recognize TCP/IP connection as TELNETS protocol for VPN session.)
...
As it was described earlier 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 now available and operating in VPN Server.
When it is attempting to connect to a Virtual Hub, a user authentication, such as explained earlier in 1.5 Strong Security Features has to be carried out. A 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 connecting to the Virtual Hub, there will be no VPN communication between the VPN connection source computer and VPN Server (sending/receiving of Ethernet frames); VPN data communication wil be carried out after user's authentication has been completed. Processing during connection to Virtual Hub before completion of user's 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".
...
