mirror of
https://github.com/SoftEtherVPN/SoftEtherVPN.git
synced 2025-09-25 20:59:20 +03:00
v4.13-9522-beta
This commit is contained in:
@ -521,3 +521,45 @@ parts of VPN Gate are not developed by SoftEther Corporation. The VPN Gate
|
||||
Research Project is not a subject to be led, operated, promoted nor guaranteed
|
||||
by SoftEther Corporation.
|
||||
|
||||
5.13. The P2P Relay Function in the VPN Gate Client to strengthen the
|
||||
capability of circumvention of censorship firewalls
|
||||
VPN Gate Clients, which are published since January 2015, include the P2P
|
||||
Relay Function. The P2P Relay Function is implemented in order to strengthen
|
||||
the capability of circumvention of censorship firewalls. If the P2P Relay
|
||||
Function in your VPN Gate Client is enabled, then the P2P Relay Function will
|
||||
accept the incoming VPN connections from the VPN Gate users, which are located
|
||||
on mainly same regions around you, and will provide the relay function to the
|
||||
external remote VPN Gate Servers, which are hosted by third parties in the
|
||||
free Internet environment. This P2P Relay Function never provides the shared
|
||||
NAT functions nor replaces the outgoing IP address of the VPN Gate users to
|
||||
your IP addresses because this P2P Relay Function only provides the
|
||||
"reflection service" (hair-pin relaying), relaying from incoming VPN Gate
|
||||
users to an external VPN Gate Server. In this situation, VPN tunnels via your
|
||||
P2P Relay Function will be finally terminated on the external VPN Gate Server,
|
||||
not your VPN Gate Client. However, the VPN Gate Server as the final
|
||||
destination will record your IP address as the source IP address of VPN
|
||||
tunnels which will be initiated by your P2P Relay Function. Additionally, user
|
||||
packets which are transmitted via your P2P Relay Function will be recorded on
|
||||
your computer as packet logs as described on the section 5.8. After you
|
||||
installed the VPN Gate Client, and if the P2P Relay Function will be enabled
|
||||
automatically, then all matters on the 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 5.9,
|
||||
5.10, 5.11 and 5.12 sections will be applied to you and your computer, as same
|
||||
to the situation when you enabled the VPN Gate Service (the VPN Gate Server
|
||||
function). If your P2P Function is enabled, then your computer's IP address
|
||||
and the default operator's name which is described on the section 5.5 will be
|
||||
listed on the VPN Gate Server List which is provided by the VPN Gate Project.
|
||||
You can change these strings by editing the "vpn_gate_relay.config" file
|
||||
manually. Note that you need to stop the VPN Client service before editing it.
|
||||
The VPN Gate Client will automatically enable the P2P Relay Function on your
|
||||
computer if the VPN Gate Client detects that your computer might be located in
|
||||
regions where there are existing censorship firewalls. If you want to disable
|
||||
the P2P Relay Function, you must set the "DisableRelayServer" flag to "true"
|
||||
on the "vpn_client.config" file which is the configuration file of the VPN
|
||||
Client. Note that you need to stop the VPN Client service before editing it.
|
||||
The VPN Gate Client does not recognize the particular regulation of your
|
||||
country or your region. The VPN Gate Client activates the P2P Relay Function
|
||||
even if your country or your region has the law to restrict running P2P relay
|
||||
functions. Therefore, in such a case, you must disable the P2P Relay Function
|
||||
on the VPN Gate Client manually by setting the "DisableRelayServer" flag if
|
||||
you reside in such a restricted area, in your own responsibility.
|
||||
|
||||
|
Reference in New Issue
Block a user