openppp2

PPP PRIVATE NETWORK™ 2

Enterprise-grade Virtual Ethernet VPN Solution
Next-generation security network access technology, providing high-performance Virtual Ethernet tunneling service.

简体中文


English

Core Technology Features

• Synchronous Hyper-threaded IO Technology
• Full Coroutine + Multithread Architecture
• Supports Printable Plain Text Transmission
• Full Duplex/Half Duplex Tunnels
• VPN Virtual Subnet
• Port Mapping to Public Network P-NAT2
• Forward Proxy Support
• Virtual Firewall
• Virtual BGP Multi-line Diversion
• Domain Name Query Diversion
• Native Support for Soft Routers
• PaperAirplane Layering Technology

• Dual Network Protocol Stack Support
• Broadcast Support (Non-Unicast)
• Support for Multiple Tunnel Protocols
• MUX Multiplexing
• DNS Caching
• Dedicated Virtual Memory
• CDN Forwarding Support
• VPN Turbo
• TCP Fast Open
• Fixed Window Size Setting
• VPN Server Proxy Forwarding
• UDP Multi-line Bandwidth Aggregation

Platform Support

• Windows
• Linux
• macOS
• Android

Supported CPU Architectures

• x86 Series
  i386 · x86_64
• ARM Series
  armv7l · armv7a · aarch64
• Other Architectures
  s390x · mipsel · ppc64el · riscv64

User License Agreement

✅ Authorized User Groups

️Usage Restrictions Warning
Use by other users violates the agreement
Unauthorized use will bear legal responsibility

️ Eight Categories of Prohibited Behaviors and Legal Details

Classification and Legal Basis of Prohibited Behaviors

⚖️ Cross-Region Legal Supervision and Accountability Mechanism (Cross-border Judicial Enforcement Framework)

Cross-border Investigation and Evidence Collection Process (GitHub Compatible Version)

⏱️ Forensics Timeline

? Key Evidence Handover Nodes

! Evidence Chain 1: Encrypted Asset Flow Map
+ Submitted to: Seychelles FIU
- Technical Means: Chainalysis on-chain tracing
# Legal Validity: 《Anti-Money Laundering Law 2020》 Annex 3

! Evidence Chain 2: GitHub Development Logs
+ Submitted to: INTERPOL Digital Crime Division
- Technical Verification: GPG signatures + Timestamps
# Legal Validity: The Hague Electronic Evidence Convention

️ User Legal Risk Tips

• For Chinese Users:

  • Under Article 38 of the Anti-Telecommunications Fraud Law, involved accounts are jointly frozen with family members\’ bank cards
  • Actions harming national security fall under Article 113 of the Criminal Law, possible death penalty
  • Illegal cross-border data transmission triggers Article 45 of the Data Security Law, up to 5 million RMB fine + license revocation

• For US Users:

  • The FBI initiates \”Unilateral Jurisdiction\” (based on USD settlement channels), no extradition needed for direct prosecution
  • Child pornography cases invoke 18 U.S.C. §2251, minimum 25-year sentence
  • Financial crimes apply the RICO Act, asset confiscation

• For Seychelles Users:

  • Offshore company controllers are personally unlimited liable (Pierce Corporate Veil principle)
  • Violations of Article 7 of the Anti-Money Laundering Law 2020 result in $10,000 daily progressive fines
  • Dark web transactions under Article 88 of the ICT Law, minimum 10-year sentence without parole

️ Real Cases of Consequences for Violations

Virtual Currency Money Laundering Cases

? Cross-border Gambling Operations

Data Selling and Privacy Crimes

️ Compound Punishment Cases of Eight Types of Crimes

Developer Disclaimer

/* Validated by cross-jurisdictional judicial practice */

1. Technology Neutral Principle
   This tool is a network protocol pure technical implementation (RFC 8446 standard), developers:

   • Do not operate any servers
   • Do not store user traffic logs
   • Do not provide commercial support services

2. Illegal Responsibility Separation Mechanism

   graph LR
      User_Actions-->ISP[Network Service Provider]
      Developer-->Code[GitHub Repository]
      Judicial_Forensics-->ISP
      Developer-.No_Access.->User_Actions
   

   
   
   Loading
   
   
   

⚖️ Judicial Cooperation Limitation Statement

Developer Compliance Cooperation Framework

graph LR
     A[Law Enforcement Request] --> B{Meets Legal Threshold}
     B -->|Yes| C[Provide Limited Materials]
     B -->|No| D[Written Rejection and Filing]
     C --> E[Record Material Delivery]
     D --> F[Judicial Remedy Procedures]
     classDef green fill:#d6f5d6,stroke:#28a745
     classDef red fill:#ffd6cc,stroke:#dc3545
     class C,E green
     class D,F red

⚖️ Cross-Jurisdiction Judicial Cooperation Details

️ Non-cooperation Situations

• No formal judicial documents, only oral/email requests
• Requests for user traffic logs or communication content
• Requests for non-public code design documents
• Cross-border requests without Hague certification

• Compliance Response: Immediately activate the \”Judicial Defense Plan\” Chapter 7 process

⚔️ Judicial Cooperation Emergency Plan

• Judicial Freeze Response
  Upon receiving forensic requests, execute immediately:

  # Freeze GitHub repository to prevent modification
  gh api repos/liulilittle/openppp2/actions/permissions --method PUT -f enabled=false
  # Activate legal protection branch
  git checkout -b legal_lockdown
  git push origin --force legal_lockdown

? Anti-Phishing Verification Process

+ Step1: Extract judicial document digital signature
+ Step2: Verify with CNNIC/GlobalSign root certificates
- Step3: If verification fails, immediately trigger judicial alert
! Step4: Send violation report to EFF

Command Line Interface

General Commands

? IP List Data Source: APNIC Official List

Server Commands

Client Commands

Core Settings

Virtual Network Card

Advanced Features

Routing Settings

Platform Specific

? Windows Commands

Global Parameters

MUX Acceleration Mode

Virtual Network Card Default Values

Virtual Gateway Server Default Values

SSMT Optimization Mode

? Symbol Explanation

Network Protocol Stack

Compilation Guide

Must use a compiler that supports C++17, no other special requirements. Install a C++17 development environment in the standard way.

Dependency Requirements

Minimum Dependencies

• Boost >= 1.70 and <= 1.8.6
• jemalloc >= 5.30 (Android excluded)
• OpenSSL >= 1.1.x

Full Dependencies

• Boost
• jemalloc
• OpenSSL
• cURL

Resource Addresses

• cURL: https://gi*t*hub.c*om/curl/curl
• jemalloc: https://git*hub.c*om*/jemalloc/jemalloc
• openssl: https://gi*th*ub*.com/openssl/openssl
• Boost: https://www.*b*oo*st.org/releases/latest

Platform Compilation Guide

Precompiled Library Resources

• Linux: openppp2-ubuntu-3rd-environment
• macOS: openppp2-macos-amd64-environment
• Android: openppp2-android-ndk-r20b-3rd-environment

Environment Requirements

Must use a compiler supporting C++17, no other special requirements. Install a C++17 development environment in the standard way.

Compilation Commands

1. Set third-party library paths
   Modify CMakeLists.txt to specify dependency library directories:
   SET(THIRD_PARTY_LIBRARY_DIR /your/actual/path)

2. Compile and run

   # Linux/macOS compilation process
   mkdir build && cd build
   cmake .. -DCMAKE_BUILD_TYPE=Release
   make -j$(nproc)  # Linux automatically detects cores
   cd ../bin && ./ppp  # Run the program

Preprocessor Macros

ANCIL_FD_BUFFER_STRUCT
Enable sendfd/recvfd shared file descriptor parent fd protection mode

CURLINC_CURL
Access HTTP/HTTPS resources via cURL library

TRANSMISSION_O1
Force network transmission layer to use /O1 optimization

JEMALLOC
Use jemalloc memory allocator instead of default

BUDDY_ALLOC_IMPLEMENTATION
Use buddy allocator for virtual memory management

MUSL
Statically link musl-libc C++ standard library (detached from GNU/Linux libc)

_LARGEFILE64_SOURCE
Ensure musl-libc supports 64-bit file functions

IO_URING Version Compilation

1. Download liburing source code and install
2. Uncomment the following in CMakeLists.txt:

   # IF(PLATFORM_SYSTEM_LINUX) 
   #     ADD_DEFINITIONS(-DBOOST_ASIO_HAS_IO_URING=1)
   #     ADD_DEFINITIONS(-DBOOST_ASIO_DISABLE_EPOLL=1)
   # ENDIF()

3. Uncomment the # liburing.a line in TARGET_LINK_LIBRARIES:

   TARGET_LINK_LIBRARIES(${NAME} 
       libc.a
       libssl.a 
       libcrypto.a 
       libjemalloc.a
       # liburing.a
   
       atomic
       dl
       pthread
   
       libboost_system.a
       libboost_coroutine.a 
       libboost_thread.a 
       libboost_context.a 
       libboost_regex.a
       libboost_filesystem.a) 

4. Follow the standard Linux build process

SIMD + AES_NI Optimization Implementation

Optimization Algorithms

Prerequisites

1. Only support i386/amd64 platforms
2. CPU must support AES-NI instruction set
   (PPP automatically detects CPU support via assembly instructions)

Compilation Steps

1. Modify CMakeLists.txt:

   SET(__AES_NI__ TRUE)  # Original value FALSE

2. Follow standard Linux build process:

   mkdir build && cd build
   cmake .. -DCMAKE_BUILD_TYPE=Release
   make -j $(nproc) 

Notes

• Only support i386/amd64; other platforms will fail to compile when enabled
• CPU must support AES-NI instructions (PPP auto-detects)
• Only optimize the following algorithms:
  • simd-aes-128-cfb
  • simd-aes-256-cfb
• After modifying CMakeLists.txt, full recompile:

  rm -rf build && mkdir build && cd build
  cmake .. -DCMAKE_BUILD_TYPE=Release
  make clean && make -j $(nproc)

Configuration Files

? Global Settings

? Encryption Settings (key)

? Network Interfaces (ip)

? Virtual Memory (vmem)

? TCP Settings

? UDP Settings

Multiplexing (mux)

WebSocket Settings

Server Configuration (server)

Client Configuration (client)

? Port Mappings

?️ Routing Rules

Configuration Guide

MUX Connection Count

VPN Thread Count

SSMT Thread Count

DNS Rules List

▶️Mainland China Domain Direct Connection Rules (Regularly Updated):
github.com/liulilittle/dns-rules.txt
Function: Bypass VPN for DNS queries, accelerating local domain resolution

HTTPS Certificate Configuration

Place the root certificate in the VPN runtime directory: cacert.pem

Certificate purpose: Ensure secure validation for HTTPS access

Quick Start

Server Deployment

1. Ubuntu 18.04 LTS x86_64 Rapid Launch

sudo su
screen -S openppp2
mkdir -p openppp2 && cd openppp2
wget https://*git*hub.co*m/liulilittle/openppp2/releases/latest/download/openppp2-linux-amd64-simd.zip
unzip openppp2-linux-amd64-simd.zip  
chmod a+x ppp
rm -rf *.txt *.key *.pem *.zip

1.1. Configure Backend

Edit appsettings.json, clear or remove the server.backend field:

\"server\": {
    \"backend\": \"\",  // Ensure this is empty
    // Other configurations remain unchanged...
    \"backend-key\": \"HaEkTB55VcHovKtUPHmU9zn0NjFmC6tff\"
}

1.2. Start Service

./ppp

Client Deployment

1. Windows Rapid Setup