# Use host OpenVPN to create an additional tunnel

**URL:** <https://forums.balena.io/t/use-host-openvpn-to-create-an-additional-tunnel/140984>\
**Category:** balenaOS\
**Tags:** docker, network\
**Created:** [June 21, 2020, 5:56pm UTC](https://forums.balena.io/t/use-host-openvpn-to-create-an-additional-tunnel/140984 "2020-06-21T17:56:01Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![mtoman](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/mtoman/32/3599_2.png) [@mtoman](https://forums.balena.io/u/mtoman)\
**Post date:** [June 22, 2020, 9:18am UTC](https://forums.balena.io/t/use-host-openvpn-to-create-an-additional-tunnel/140984/4 "2020-06-22T09:18:42Z")

</div>

Hi,  
I believe you are one step from what you are trying to achieve. Using `network_mode: host` lets you manipulate the host OS’s network stack from within the container so starting an OpenVPN client within such container will actually create the connection on the host. Basically what you need to do is

- Switch all containers in your docker-compose to host networking
- Run the OpenVPN client within one of the containers (I believe it also needs to either be privileged or have the `NET_ADMIN` capability to create the network interface)  
If the OpenVPN client within the container creates a connection this one should be available on the host OS and all the containers as well.  
Please let us know whether this is what you were looking for.

---

_[View the full topic](https://forums.balena.io/t/use-host-openvpn-to-create-an-additional-tunnel/140984)._