Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/kizzx2/docker-openvpn-client-socks
Expose an OpenVPN tunnel as a SOCKS proxy
https://github.com/kizzx2/docker-openvpn-client-socks
docker openvpn opsec privacy proxy
Last synced: about 2 months ago
JSON representation
Expose an OpenVPN tunnel as a SOCKS proxy
- Host: GitHub
- URL: https://github.com/kizzx2/docker-openvpn-client-socks
- Owner: kizzx2
- License: other
- Fork: true (mook/docker-openvpn-client-socks)
- Created: 2016-02-26T14:33:02.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2024-04-04T09:18:45.000Z (8 months ago)
- Last Synced: 2024-08-01T03:22:51.962Z (4 months ago)
- Topics: docker, openvpn, opsec, privacy, proxy
- Language: Dockerfile
- Homepage: https://hub.docker.com/r/kizzx2/openvpn-client-socks
- Size: 5.86 KB
- Stars: 138
- Watchers: 5
- Forks: 69
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- stars - kizzx2/docker-openvpn-client-socks
- awesome-network-stuff - **22**星
README
# OpenVPN-client
This is a docker image of an OpenVPN client tied to a SOCKS proxy server. It is
useful to isolate network changes (so the host is not affected by the modified
routing).
This supports directory style (where the certificates are not bundled together in one `.ovpn` file) and those that contains `update-resolv-conf`
(For the same thing in WireGuard, see [kizzx2/docker-wireguard-socks-proxy](https://github.com/kizzx2/docker-wireguard-socks-proxy))
## Why?
This is arguably the easiest way to achieve "app based" routing. For example, you may only want certain applications to go through your WireGuard tunnel while the rest of your system should go through the default gateway. You can also achieve "domain name based" routing by using a [PAC file](https://developer.mozilla.org/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_(PAC)_file) that most browsers support.
## Usage
Preferably, using `start` in this repository:
```bash
start /your/openvpn/directory
```
`/your/openvpn/directory` should contain *one* OpenVPN `.conf` file. It can reference other certificate files or key files in the same directory.
Alternatively, using `docker run` directly:
```bash
docker run -it --rm --device=/dev/net/tun --cap-add=NET_ADMIN \
--name openvpn-client \
--volume /your/openvpn/directory/:/etc/openvpn/:ro -p 1080:1080 \
kizzx2/openvpn-client-socks
```
Then connect to SOCKS proxy through through `localhost:1080` / `local.docker:1080`. For example:
```bash
curl --proxy socks5h://local.docker:1080 ipinfo.io
```
## Solutions to Common Problems
### I'm getting `RTNETLINK answers: Permission denied`
Try adding `--sysctl net.ipv6.conf.all.disable_ipv6=0` to your docker command
### DNS doesn't work
You can put a `update-resolv-conf` as your `up` script. One simple way is to put [this file](https://gist.github.com/Ikke/3829134) as `up.sh` inside your OpenVPN configuration directory.
## HTTP Proxy
You can easily convert this to an HTTP proxy using [http-proxy-to-socks](https://github.com/oyyd/http-proxy-to-socks), e.g.
```bash
hpts -s 127.0.0.1:1080 -p 8080
```