SOCKS Proxy Usage
After a successful tunnel with dynamic forwarding, applications can send traffic through a local SOCKS proxy.
Typical Flow
- Connect to Abdal 4iProto Server with an official client or SSH dynamic forwarding
- Note the local SOCKS listen port created by the client
- Point browsers or apps to that SOCKS endpoint
- All matching traffic is tunneled through the secure SSH connection
Common Local Endpoint
With the Abdal client ecosystem, applications are commonly configured to use:
localhost:52905
If you create the SOCKS listener yourself (for example with ssh -D 1080), use the port you chose.
Tips
- Prefer the official Abdal clients for integrated SOCKS5 setup
- Keep destination filters and quotas in mind when testing high-bandwidth apps
- Validate blocked domains/IPs with a non-admin test account