Upstream Socks5/HTTP/(s) Proxy support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 15.2k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
Let's say before connecting to OpenVPN that is installed on my VPS I have to supply a Socks5 proxy that my company gave me. like: socks-proxy 89.84.23.12:1080
How do I use my socks5 as a middle man before reaching Brook Wsserver?
On my VPS where Brook is install I ran: brook wsserver --listen :443 --password hello --path /ws
On my client I tried:
.\brook.exe wsclient --socks5 127.0.0.1:9090 -s ws://my.vps.ip:443 --password hello --socks5ServerIP 89.84.23.12:1080
And then I got: lookup 89.84.23.12:1080: no such host
Now I'm confused as I thought --socks5ServerIP will be my upstream Socks5 (The one I need to my company gave me to access the internet)
My question is: How to make use of your upstream proxy on the Brook client, be it Socks5 or HTTP/(s) as a middle man before reaching Brook Wsserver ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the wsclient command and its --socks5 and --socks5ServerIP arguments, using the reported wsserver invocation as the connection target. No source files or tests are named, so first locate the wsclient entry point and determine the intended upstream SOCKS5 and HTTP/(S) proxy behavior; done means a client can connect through the upstream proxy without the reported host lookup error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100