Routing Switch
| Property |
Value |
| Binary Name |
routing-switch |
| Version |
9.0.1 |
| File Size |
5.7MB |
| Author |
Warith Al Maawali |
| License |
Proprietary |
| Category |
Network & Routing |
| Description |
System-wide traffic routing through various proxy protocols |
| JSON Data |
View Raw JSON |
SHA256 Checksum
3019631aef8b985709a66fe847d19d6ea6ef7b3a4030b8285f6a11e27186e489
Key Features
Multi-Protocol Support
| Protocol Type |
Description |
| Traditional VPNs |
OpenVPN and WireGuard with native kernel routing |
| Tor Integration |
Routes through Tor using redsocks transparent proxy |
| SOCKS5 Proxies |
Dante for generic SOCKS5 proxy support |
| Shadowsocks |
High-performance encrypted proxy |
| V2Ray |
Advanced proxy with multiple transport protocols |
| Xray Variants |
VLESS, VLESS-Reality, Trojan, VMess protocols |
| Mieru/Mita |
Censorship-resistant proxy protocol |
| Hysteria2 |
QUIC-based proxy for unreliable networks |
| Auto-Selection |
Intelligently chooses best protocol based on availability |
Why Routing Switch is Essential
| Feature |
Description |
| System-Wide Protection |
Routes ALL traffic, not just browser |
| Protocol Flexibility |
Switch between protocols based on needs |
| Authentication Required |
Works with online-auth for secure access |
| Zero Configuration |
Protocols are pre-configured from authentication cards |
TL;DR - Essential Commands
Important: Requires authentication via online-auth before use. Use sudo for connection commands.
# Auto-select and connect to best protocol (requires auth)
sudo routing-switch auto-select
# Connect to specific protocol examples
sudo routing-switch connect openvpn
sudo routing-switch connect wireguard
sudo routing-switch connect tor
sudo routing-switch connect dante
sudo routing-switch connect shadowsocks
sudo routing-switch connect v2ray
sudo routing-switch connect xray-vless
sudo routing-switch connect xray-vless-reality
sudo routing-switch connect xray-trojan
sudo routing-switch connect xray-vmess
sudo routing-switch connect mita
sudo routing-switch connect hysteria2
# Check connection status
routing-switch status
# Disconnect current connection
sudo routing-switch disconnect
# List available protocols
routing-switch list-protocols
Understanding Protocol Support
How Routing Works
Routing Switch requires authentication through online-auth to access server configurations. The routing-switch automatically fetches your "card" containing all server details:
# Step 1: Authenticate first (required)
sudo online-auth authenticate
# Step 2: Connect using routing-switch (automatically fetches card)
sudo routing-switch auto-select
Available Protocols
# List all available protocols with scores
routing-switch list-protocols
# List protocols sorted by speed (fastest first)
routing-switch list-protocols --sort-by-speed
# List protocols sorted by reliability
routing-switch list-protocols --sort-by-reliability
# Test specific protocol connectivity
routing-switch test-protocol openvpn
routing-switch test-protocol wireguard
# Benchmark all protocols
routing-switch benchmark
Protocol Categories:
| Category |
Protocols |
Description |
| Native Routing |
OpenVPN, WireGuard |
Direct kernel-level routing |
| Redsocks Proxy |
Tor |
Transparent SOCKS proxy redirection |
| SOCKS5 Proxies |
Dante |
Generic SOCKS5 proxy support |
| Tun2socks |
Shadowsocks, V2Ray, Xray-VLESS, Xray-VLESS-Reality, Xray-Trojan, Xray-VMess, Mieru/Mita, Hysteria2 |
TUN interface proxy routing |
Connection Management
# Connect to best available protocol
sudo routing-switch auto-select
# Connect to specific protocol
sudo routing-switch connect openvpn
sudo routing-switch connect wireguard
sudo routing-switch connect shadowsocks
sudo routing-switch connect v2ray
sudo routing-switch connect xray-vmess
# Check current status
routing-switch status
# Check DNS configuration
routing-switch dns-info
# Optional: verify no DNS leaks with the dedicated tester
dns-leak test --json
# Disconnect current connection
sudo routing-switch disconnect
# Reset all routing to defaults
sudo routing-switch reset
Microsocks SOCKS5 Server
Turn your Kodachi machine into a SOCKS5 proxy server so other devices on your network can route their traffic through your active routing-switch connection:
# Step 1: Connect routing-switch to any service first
sudo routing-switch connect wireguard
# or any other protocol: v2ray, shadowsocks, hysteria2, etc.
# Step 2: Enable microsocks server (auto port detection)
sudo routing-switch microsocks-enable -u USERNAME -p PASSWORD
# Enable with specific port (30050-30054 range)
sudo routing-switch microsocks-enable -u USERNAME -p PASSWORD --port 30051
# Check server status
routing-switch microsocks-status
routing-switch microsocks-status --json
# Disable microsocks server
sudo routing-switch microsocks-disable
Microsocks Features:
| Feature |
Description |
| Port Range |
Auto-selects from 30050-30054 or specify manually |
| Authentication |
Username and password required |
| Process Management |
PID tracking and graceful shutdown |
| Status Monitoring |
Real-time status with uptime tracking |
| Network Interfaces |
Listens on all interfaces (0.0.0.0) |
Workflow Example:
| Step |
Action |
Description |
| 1 |
sudo routing-switch connect wireguard |
Connect to your VPN/proxy service |
| 2 |
sudo routing-switch microsocks-enable -u microkodachi -p 'SecurePass123' |
Start SOCKS5 server |
| 3 |
Connect other devices |
Use socks5://microkodachi:SecurePass123@YOUR_IP:30050 |
Security Notes:
| Practice |
Description |
| Strong Credentials |
Use complex username and password |
| Network Security |
Only enable on trusted networks |
| Connection First |
Always connect routing-switch before enabling microsocks |
| Port Management |
Microsocks uses dedicated 30050-30054 range |
Configuration Export
# Export all protocol configurations
routing-switch export-config
# Export specific protocol configuration
sudo routing-switch export-config wireguard
sudo routing-switch export-config shadowsocks
sudo routing-switch export-config v2ray
# Show configuration for current protocol
routing-switch showconfig
# Show configuration as URL
routing-switch showconfigurl
# Show configuration as QR code
routing-switch showconfigqr
Mobile Device Integration
Connect your mobile devices using QR codes generated by routing-switch. Different protocols work with different mobile apps:
WireGuard (Official App)
# Generate WireGuard QR code
routing-switch showconfigqr wireguard
Shadowsocks, V2Ray, and Xray Protocols
# Generate QR codes for various protocols
routing-switch showconfigqr shadowsocks
routing-switch showconfigqr v2ray
routing-switch showconfigqr xray-vmess
routing-switch showconfigqr xray-trojan
routing-switch showconfigqr xray-vless
Recommended Mobile Apps:
| Platform |
App Name |
Supported Protocols |
| Android |
V2RayNG |
V2Ray, Xray (all variants), Shadowsocks |
| Android |
Matsuri |
V2Ray, Xray, Shadowsocks, Trojan |
| Android |
Clash for Android |
Multi-protocol support with rule-based routing |
| Android |
Surfboard |
Shadowsocks, V2Ray, Trojan |
| iOS |
Shadowrocket |
Shadowsocks, V2Ray, Trojan, VMess, VLESS |
| iOS |
Quantumult X |
Advanced proxy client with multiple protocol support |
| iOS |
Surge |
Professional networking tool supporting various protocols |
| iOS |
Stash |
Clash-compatible client for iOS |
How to Connect:
| Step |
Action |
| 1 |
Generate the QR code for your desired protocol |
| 2 |
Open your chosen mobile app |
| 3 |
Scan the QR code using the app's import feature |
| 4 |
The app will automatically configure the connection |
| 5 |
Enable the VPN/proxy in the app to connect |
Recovery and Cleanup
# Clean up orphaned processes
sudo routing-switch cleanup
# Recover from partial failure
sudo routing-switch recover
# Reset all routing tables
sudo routing-switch reset
For advanced users who need access to all available commands and options, please refer to the auto-generated command reference which includes:
| Feature |
Description |
| Protocol Testing |
Protocol testing and benchmarking |
| Configuration Management |
Configuration export and import |
| Mobile Integration |
QR code generation for mobile |
| Custom Config |
Custom configuration files |
| Recovery Tools |
Recovery and cleanup operations |
| CLI Reference |
All command-line flags and parameters |
Security Notes
Important Security Practices:
| Practice |
Description |
| Authentication |
Always authenticate with online-auth first |
| Verification |
Verify connection status after connecting |
| DNS Security |
Test for DNS leaks after connection |
| Auto-Selection |
Use auto-select for optimal security |
| Proper Disconnection |
Disconnect properly to restore routing |
| Monitoring |
Monitor connection status regularly |
| Metric |
Value |
Description |
| Connection Time |
2-10 seconds |
Depending on protocol |
| Memory Usage (VPN) |
~40MB |
For VPN protocols |
| Memory Usage (Proxy) |
~60MB |
For proxy protocols |
| CPU Usage (VPN) |
< 10% |
For VPN protocols |
| CPU Usage (Proxy) |
< 15% |
For proxy protocols |
| WireGuard Speed |
90-95% |
Of line speed |
| OpenVPN Speed |
70-80% |
Of line speed |
| Tor Speed |
1-10 Mbps |
Typical speeds |
Support