VortexL2 v2.0 uses HAProxy for production-grade, high-performance port forwarding.
| Feature | Python asyncio (v1.x) | HAProxy (v2.0) |
|---|---|---|
| Latency | ~5-10ms overhead | <1ms overhead |
| Throughput | ~100 Mbps | 10+ Gbps |
| Connections | ~1,000 | 100,000+ |
| CPU Usage | High | Very Low |
| Stability | Moderate | Production-grade |
HAProxy is automatically installed by the VortexL2 installer:
bash <(curl -Ls https://raw.githubusercontent.com/iliya-Developer/VortexL2/main/install.sh)Or manually:
sudo apt-get update
sudo apt-get install haproxyHAProxy configuration is automatically managed by VortexL2:
- Config Location:
/etc/haproxy/haproxy.cfg - Backup:
/etc/haproxy/haproxy.cfg.bak(created before first modification)
When you add/remove port forwards via the VortexL2 panel, HAProxy is automatically reconfigured and reloaded.
# Check HAProxy status
sudo systemctl status haproxy
# View listening ports
ss -tlnp | grep haproxy
# View HAProxy statistics
echo "show stat" | socat stdio /var/run/haproxy.sock
# Manually reload HAProxy
sudo systemctl reload haproxy
# View HAProxy config
cat /etc/haproxy/haproxy.cfg-
Check configuration validity:
sudo haproxy -c -f /etc/haproxy/haproxy.cfg
-
Check logs:
sudo journalctl -u haproxy -f
-
Check for port conflicts:
ss -tlnp | grep <port>
-
Verify HAProxy is running:
sudo systemctl status haproxy
-
Check if port is listening:
ss -tlnp | grep haproxy -
Verify remote host is reachable:
ping <remote-forward-ip>
-
Check HAProxy config was generated:
cat /etc/haproxy/haproxy.cfg | grep frontend
If needed, restore the original HAProxy configuration:
sudo cp /etc/haproxy/haproxy.cfg.bak /etc/haproxy/haproxy.cfg
sudo systemctl restart haproxy ┌─────────────────────┐
│ HAProxy (v2.0) │
│ │
Client ──────────► │ frontend :443 │
443,80,2053 │ frontend :80 │ ──► l2tpeth0 ──► Remote Server
│ frontend :2053 │
│ │
│ ✓ TCP mode │
│ ✓ Health checks │
│ ✓ Auto-reload │
└─────────────────────┘