How aminmgmt/backpack works
BackPack is a Go tunneling and server-operations product. Operators configure the Iran and kharej endpoints through the CLI or web panel; the resulting client/server engines establish reverse tunnels that carry forwarded TCP/UDP traffic. Direct layer-3 tunnels, transport fallback, diagnostics, fleet control, backups, updates, and Telegram monitoring are additional product branches. The main entry point and engine dispatch are evidenced in excerpts; several capability links are documented by the README, while unsampled implementation details are not asserted.
Main entry points: main.go Process entry · client.go Client engine · server.go Server engine · transport Server transports
Components 22
Operator entry points
- Process entry
main.go - Interactive CLI
internal/cli/cli.go - Management menus
internal/menu/menu.go - Tunnel configuration
config/config.go
Tunnel runtime
- Client engine
internal/client/client.go - Server engine
internal/server/server.go - Client transports
internal/client/transport - Server transports
internal/server/transport - Fallback chain
internal/tunnel/chain/chain.go - Traffic forwarding
internal/utils/handlers/tcp_handler.go - Direct L3 tunnel
internal/tunnel/l3/tunnel.go
Operations and fleet
- Health diagnostics
internal/manage/health/health.go - Backup and restore
internal/manage/backup/backup.go - Verified updates
internal/manage/update.go - Fleet management
internal/control/fleet.go - Managed nodes
internal/node/runner.go - Runtime metrics
internal/metrics/metrics.go
Monitoring interfaces
- Web panel server
internal/webui/server.go - Panel interface
internal/webui/panel/js/main.js - Panel API client
internal/webui/panel/js/api.js - Telegram monitoring
internal/telegram/telegram.go
Other components
- Operator
Connections 25
- Operator → Process entry: starts
main.go - Process entry → Interactive CLI: dispatches
main.go - Process entry → Management menus: opens
main.go - Process entry → Client engine: runs configured engine
- Process entry → Server engine: runs configured engine
- Interactive CLI → Tunnel configuration: configures
- Management menus → Tunnel configuration: configures
- Client engine → Fallback chain: runs fallback
internal/client/client.go - Server engine → Fallback chain: runs fallback
internal/server/server.go - Client engine → Client transports: starts transport
internal/client/client.go - Server engine → Server transports: starts transport
internal/server/server.go - Server transports → Traffic forwarding: forwards traffic
- Client engine → Direct L3 tunnel: supports direct mode
- Server engine → Direct L3 tunnel: supports direct mode
- Operator → Panel interface: manages tunnels
README.md - Panel interface → Panel API client: requests data
internal/webui/panel/js/main.js - Panel API client → Web panel server: calls API
internal/webui/panel/js/api.js - Web panel server → Fleet management: serves fleet operations
internal/webui/server.go - Web panel server → Managed nodes: routes node operations
- Operator → Health diagnostics: runs diagnostics
README.md - Operator → Backup and restore: backs up state
README.md - Operator → Verified updates: applies updates
README.md - Telegram monitoring → Runtime metrics: reads monitoring data
internal/telegram/telegram.go - Client transports → Runtime metrics: reports tunnel metrics
- Server transports → Runtime metrics: reports tunnel metrics