Table of contents

5.2 Operating Modes

    Table of contents
    to the older version or return to version archive.

    Combined revision comparison

    Comparing version 17:17, 4 Mar 2013 by yagi with version 12:16, 20 Jan 2024 by puripuri2100.

    ...

    • Installing the Windows version SoftEther VPN Bridge from the installer results in the installation of the Service Mode and automatic initiation of its operation as a background service. For details, please refer to  9.27.2 Install on Windows and Initial Configurations.
    • In order to install the SoftEther VPN Bridge in Service Mode on the Linux version or other UNIX versions, it is necessary to register it on the system as a daemon process. For details, please refer to  9.37.3 Install on Linux and Initial Configurations.

    ...

    Please refer to 9.37.3 Install on Linux and Initial Configurations  for details on installing and launching the Linux and other UNIX versions of the SoftEther VPN Bridge in Service Mode.

    ...

    As described in  9.37.3 Install on Linux and Initial Configurations, daemonizing and using the vpnbridge process in UNIX operating systems is simply a matter of registering it so as to instruct the operating system's startup script to call up vpnbridge start. Even when running the VPN Bridge in Service Mode, something equivalent to the procedure described here is automatically performed by a system with root authority so there is fundamentally no difference. Accordingly, the items described below also apply generally to the daemonized VPN Bridge .

    As shown below, the vpnbridge process is launched in two stages on the UNIX version VPN Bridge . First, the first process named execsvc is launched as a background process, after which that process creates a child process using the fork() system call, and this child process carries out the actual VPN processing. The parent process (process ID 1549 in the example below) constantly monitors the child process (process ID 1550 in the example below) and in the event that an abnormal error occurs, immediately terminates the process and launches it again to attempt recovery (see 3.3.12 Failure Recovery3.3 VPN Server Administration for details). The example below was actually run on a particular Linux system so it may not appear the same on different Linux or other operating systems. In addition, in order to display multiple threads as multiple processes in the case of versions with old Linux kernels (i.e. versions not compatible with native threads), the actual vpnbridge processes created may be more than those in the example below but this is a display issue and operation is in fact normal.

    ...

    See Also

    Other changes:

    1. /body/ul/li/a/@href: "mks://localhost/4-docs/1-manual/7/7.2" ⇒ "mks://localhost/4-docs/1-manual/9/9.2"
    2. /body/ul/li/a/@title: "7.2 Install on Windows and Initial Configurations" ⇒ "9.2 Install on Windows and Initial Configurations"
    3. /body/ul/li[2]/a/@href: "mks://localhost/4-docs/1-manual/7/7.3" ⇒ "mks://localhost/4-docs/1-manual/9/9.3"
    4. /body/ul/li[2]/a/@title: "7.3 Install on Linux and Initial Configurations" ⇒ "9.3 Install on Linux and Initial Configurations"
    5. /body/p[21]/a/@href: "mks://localhost/4-docs/1-manual/7/7.3" ⇒ "mks://localhost/4-docs/1-manual/9/9.3"
    6. /body/p[21]/a/@title: "7.3 Install on Linux and Initial Configurations" ⇒ "9.3 Install on Linux and Initial Configurations"
    7. /body/p[36]/a/@href: "mks://localhost/4-docs/1-manual/7/7.3" ⇒ "mks://localhost/4-docs/1-manual/9/9.3"
    8. /body/p[36]/a/@title: "7.3 Install on Linux and Initial Configurations" ⇒ "9.3 Install on Linux and Initial Configurations"
    9. /body/p[37]/a/@href: "mks://localhost/4-docs/1-manual/3/3.3" ⇒ "mks://localhost/4-docs/1-manual/3/3.3#3.3.12_Failure_Recovery"
    10. /body/p[37]/a/@title: "3.3 VPN Server Administration" ⇒ "3.3.12 Failure Recovery"

    Version from 17:17, 4 Mar 2013

    This revision modified by yagi (Ban)

    ...

    • Installing the Windows version SoftEther VPN Bridge from the installer results in the installation of the Service Mode and automatic initiation of its operation as a background service. For details, please refer to 7.2 Install on Windows and Initial Configurations.
    • In order to install the SoftEther VPN Bridge in Service Mode on the Linux version or other UNIX versions, it is necessary to register it on the system as a daemon process. For details, please refer to 7.3 Install on Linux and Initial Configurations.

    ...

    Please refer to 7.3 Install on Linux and Initial Configurations for details on installing and launching the Linux and other UNIX versions of the SoftEther VPN Bridge in Service Mode.

    ...

    As described in 7.3 Install on Linux and Initial Configurations, daemonizing and using the vpnbridge process in UNIX operating systems is simply a matter of registering it so as to instruct the operating system's startup script to call up vpnbridge start. Even when running the VPN Bridge in Service Mode, something equivalent to the procedure described here is automatically performed by a system with root authority so there is fundamentally no difference. Accordingly, the items described below also apply generally to the daemonized VPN Bridge .

    As shown below, the vpnbridge process is launched in two stages on the UNIX version VPN Bridge . First, the first process named execsvc is launched as a background process, after which that process creates a child process using the fork() system call, and this child process carries out the actual VPN processing. The parent process (process ID 1549 in the example below) constantly monitors the child process (process ID 1550 in the example below) and in the event that an abnormal error occurs, immediately terminates the process and launches it again to attempt recovery (see 3.3 VPN Server Administration for details). The example below was actually run on a particular Linux system so it may not appear the same on different Linux or other operating systems. In addition, in order to display multiple threads as multiple processes in the case of versions with old Linux kernels (i.e. versions not compatible with native threads), the actual vpnbridge processes created may be more than those in the example below but this is a display issue and operation is in fact normal.

    ...

    Current version

    This revision modified by puripuri2100 (Ban)

    ...

    • Installing the Windows version SoftEther VPN Bridge from the installer results in the installation of the Service Mode and automatic initiation of its operation as a background service. For details, please refer to 9.2 Install on Windows and Initial Configurations.
    • In order to install the SoftEther VPN Bridge in Service Mode on the Linux version or other UNIX versions, it is necessary to register it on the system as a daemon process. For details, please refer to 9.3 Install on Linux and Initial Configurations.

    ...

    Please refer to 9.3 Install on Linux and Initial Configurations for details on installing and launching the Linux and other UNIX versions of the SoftEther VPN Bridge in Service Mode.

    ...

    As described in 9.3 Install on Linux and Initial Configurations, daemonizing and using the vpnbridge process in UNIX operating systems is simply a matter of registering it so as to instruct the operating system's startup script to call up vpnbridge start. Even when running the VPN Bridge in Service Mode, something equivalent to the procedure described here is automatically performed by a system with root authority so there is fundamentally no difference. Accordingly, the items described below also apply generally to the daemonized VPN Bridge .

    As shown below, the vpnbridge process is launched in two stages on the UNIX version VPN Bridge . First, the first process named execsvc is launched as a background process, after which that process creates a child process using the fork() system call, and this child process carries out the actual VPN processing. The parent process (process ID 1549 in the example below) constantly monitors the child process (process ID 1550 in the example below) and in the event that an abnormal error occurs, immediately terminates the process and launches it again to attempt recovery (see 3.3.12 Failure Recovery for details). The example below was actually run on a particular Linux system so it may not appear the same on different Linux or other operating systems. In addition, in order to display multiple threads as multiple processes in the case of versions with old Linux kernels (i.e. versions not compatible with native threads), the actual vpnbridge processes created may be more than those in the example below but this is a display issue and operation is in fact normal.

    ...

    See Also