V2 Ha Tunnel !!link!!: Realm Host

Realm Host (v2) feature in HA Tunnel Plus is a specialized connection option designed to bypass restrictive firewalls by spoofing the "realm" or domain authority of your connection request. It is particularly effective for networks that use deep packet inspection (DPI) to block standard VPN protocols. ha-tunnel-plus.en.softonic.com Core Mechanism Encapsulation : Like all HA Tunnel Plus features, it uses the

protocol to encrypt data, masking it from the Internet Service Provider (ISP). Host Spoofing

: The "v2" version of Realm Host allows for more granular control over how the SNI (Server Name Indication) and host headers are presented to the network. Bypass Strategy

: By checking "Use Realm Host (v2)," the application wraps your connection request in a way that makes it appear as though it is communicating with an authorized "realm" (like a free educational or social media site), allowing it to pass through "zero-rated" or whitelisted network gates. ha-tunnel-plus.en.softonic.com How to Configure

To set up a connection using Realm Host v2, follow these steps within the HA Tunnel Plus app Enable Custom Setup : Toggle the Custom Setup switch on the home screen. Select Connection Mode : Tap the dropdown menu and select Custom SNI Input SNI Host : Enter a working host address (often found via SNI host generators ) in the provided field. Activate Realm Host : Check the box for Use Realm Host (v2) . For added stability, also check Preserve SNI : Usually, (HTTPS) or (HTTP) is used for these configurations. Start Connection realm host v2 ha tunnel

button and monitor the logs to ensure the connection is established successfully. Optimization Tips Log Monitoring : Always check the

tab if the connection fails; it will tell you if the host is rejected or if there is a timeout. Importing Configs

: If manual setup is too complex, many users share pre-configured files that can be imported via the Import Config option in the app menu. Payload Accuracy : If using a custom payload instead of SNI, ensure the header matches the working realm you are trying to spoof. for your specific region? AI responses may include mistakes. Learn more HA Tunnel Configuration Guide | PDF - Scribd

Part 4: Step-by-Step Implementation (Active-Passive HA)

For this guide, we assume:

• Two Ubuntu 22.04 servers: realm-ha-01 (192.168.1.10) and realm-ha-02 (192.168.1.11).
• A shared etcd cluster (or use built-in memory sync with constraints).
• Backend service: an internal HTTP API on localhost:8080 or a remote MongoDB.

Step 3: Set Up VIP Management (VRRP with Keepalived)

Install Keepalived on both nodes:

sudo apt install keepalived

On realm-ha-01 (/etc/keepalived/keepalived.conf):

vrrp_instance VI_1 
    state MASTER
    interface eth0
    virtual_router_id 51
    priority 101
    advert_int 1
    authentication 
        auth_type PASS
        auth_pass realmHA2024
virtual_ipaddress 
        203.0.113.10/24 dev eth0 label eth0:vip
track_script 
        chk_realm
vrrp_script chk_realm 
script "/usr/local/bin/realm health check --port 8443"
interval 2
fall 2
rise 2

On realm-ha-02, use state BACKUP and priority 100. This ensures the VIP floats only to the node where the Realm daemon is healthy.

Part 1: What is Realm Host V2?

Before diving into HA tunnels, we must understand the core tool.

Realm Host is an open-source, high-performance local proxy and tunneling daemon. Unlike traditional VPNs (which route entire network stacks), Realm focuses on Layer 4 (TCP/UDP) traffic management. It is famous for its:

• Low latency: Written in Rust, it competes with Nginx and HAProxy in raw throughput.
• TLS encryption: Native support for mTLS and TLS 1.3.
• Multi-protocol: Handles TCP, UDP, and WebSocket tunneling.
• Cross-compilation: Runs on x86_64, ARMv7, and ARM64 (Raspberry Pi, Apple Silicon).

Version 2 (V2) introduced critical features for HA: Realm Host (v2) feature in HA Tunnel Plus

• Hot-reloadable configuration (no restart needed for peer changes).
• Native health check endpoints (/health) for load balancers.
• Improved connection draining (graceful shutdown).

5. Configuration Example (TOML)

To achieve HA, the configuration file (config.toml) would look similar to this:

[log]
level = "warn"
Shared tunnel definition (this is the HA tunnel)
[[tunnels]]
name = "ha-tunnel-01"
listen = "0.0.0.0:8443"   # The VIP address will be set by external LB
listen_type = "tcp"
remote = "127.0.0.1:8080" # Backend service
remote_type = "tcp"
Failover Logic Example (Pseudo-code)
while true:
    for endpoint in endpoints:
        if health_check(endpoint) == PASS:
            if endpoint != current_active:
                switch_tunnel(endpoint)  # Zero-downtime migration
            break
    sleep(interval)