How osmiteam-ctrl/tor-gatling-proxy works
This repository implements a Tor proxy pool manager: it loads pool and bridge settings, starts active and standby Tor processes, controls their HAProxy server states, and periodically restarts failed instances or safely rotates idle ones. Startup connectivity checks exercise each instance through its SOCKS port. The graph separates configuration, pool lifecycle, and proxy traffic/control. The README is empty and HAProxy and deployment configuration contents were not provided, so traffic routing is shown as unverified rather than asserted.
Main entry points: app.py Pool manager · haproxy.cfg HAProxy configuration · proxy-config.yaml Pool settings · bridges.txt Bridge list
Components 10
Configuration
- Pool settings
config/proxy-config.yaml - Bridge list
config/bridges.txt
Tor pool lifecycle
- Pool manager
tor-manager/app.py - Tor instances
tor-manager/app.py - Connectivity checks
tor-manager/app.py
Proxy traffic and control
- HAProxy configuration
haproxy/haproxy.cfg - HAProxy
- Tor SOCKS ports
tor-manager/app.py
Other components
- Proxy users
- Test endpoints
Connections 10
- Pool manager → Pool settings: reads settings
tor-manager/app.py - Pool manager → Bridge list: reads bridges
tor-manager/app.py - Pool manager → Tor instances: starts and restarts
tor-manager/app.py - Pool manager → HAProxy: sets server state
tor-manager/app.py - Pool manager → Connectivity checks: runs checks
tor-manager/app.py - Connectivity checks → Tor SOCKS ports: proxies requests
tor-manager/app.py - Connectivity checks → Test endpoints: sends test requests
tor-manager/app.py - Proxy users → HAProxy: sends proxy traffic
- HAProxy configuration → HAProxy: configures routing
- HAProxy → Tor SOCKS ports: forwards traffic