[Feature Request] Local SOCKS Proxy to OpenVPN Network Inferface
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 465
- PR merge metrics
- No merged PRs in 30d
Description
Please include a tiny local SOCKS server that tunnels traffic to the OpenVPN interface, so individual Windows applications that can't bind to a network interface or ip address, can pipe traffic to the localhost SOCKS proxy server instead.
There are a LOT of web forums with people asking for a solution to do this, and no solutions seem to be available unless somebody writes the software to do this.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the OpenVPN GUI architecture and how it interacts with the OpenVPN interface on Windows. Define the SOCKS proxy's routing, lifecycle, and application-compatibility requirements before implementing it; done means individual Windows applications can send traffic through localhost to the VPN interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100