hilscherautomation / netpi-openvpn Goto Github PK

Made for Raspberry Pi 3B architecture based devices and compatibles

https://hub.docker.com/r/hilschernetpi/netpi-openvpn/

The image provided hereunder deploys an OpenVPN server, a web shell to configure the server and a web page to download created *.ovpn configuration files for connecting OpenVPN clients.

Base of this image builds debian with installed OpenVPN server package and a web proxy providing access to a web shell and a web server with a download page for *.ovpn files. For a guided OpenVPN configuration the PiVPN Project installer is preinstalled ready for immediate execution.

After configuration an OpenVPN tunnel can be established using an OpenVPN client. The tunnel allows the access to the OpenVPN server device itself and all the devices connected to its network interfaces (e.g. eth0).

The container has been successfully tested on the following hosts

• netPI, model RTE 3, product name NIOT-E-NPI3-51-EN-RE
• netPI, model CORE 3, product name NIOT-E-NPI3-EN
• netFIELD Connect, product name NIOT-E-TPI51-EN-RE/NFLD
• Raspberry Pi, model 3B
• Raspberry Pi, model 4B (arm32v7,arm64v8)

netPI devices specifically feature a restricted Docker protecting the Docker host system software's integrity by maximum. The restrictions are

• privileged mode is not automatically adding all host devices /dev/ to a container
• volume bind mounts to rootfs is not supported
• the devices /dev,/dev/mem,/dev/sd*,/dev/dm*,/dev/mapper,/dev/mmcblk* cannot be added to a container

The container runs in bridge network mode. This makes port mapping necessary.

The default port for the web proxy is 8008. For any other port define the environment variable WEBPORT with the desired port number as value.

The following container ports need to be exposed to host ports

Once deployed port mapping can't be changed for a container. So make sure the mapped ports and protocols are correct prior to deployment.

To allow performing various network-related operations the capability NET_ADMIN needs to be set for the container.

To allow the registration of a network device the /dev/net/tun host device needs to be added to the container.

The privileged mode lifts the standard Docker enforced container limitations: applications inside a container are getting (almost) all capabilities as if running on the host directly.

Enabling the privileged mode is mandatory for this container.

To persist all the container configuration data located in the container folder /etc/data an outsourcing to a Docker volume (e.g. data) is strongly recommended.

Pulling the image may take 10 minutes.

STEP 1. Open netPI's web UI in your browser (https).

STEP 2. Click the Docker tile to open the Portainer.io Docker management user interface.

STEP 3. Click Volumes > + Add Volume. Enter data as Name and click Create the volume.

STEP 4. Enter the following parameters under Containers > + Add Container

STEP 5. Press the button Actions > Start/Deploy container

docker volume create data && docker run -d --network=bridge --privileged --device=/dev/net/tun:/dev/net/tun -v data:/etc/data -e WEBPORT=8008 -p 8008:8008/tcp -p 1194:1194/udp --cap-add=NET_ADMIN hilschernetpi/netpi-openvpn:latest

version: "2"

services:
 openvpn:
   image: hilschernetpi/netpi-openvpn:latest
   restart: always
   privileged: true
   network_mode: bridge
   cap_add:
     - NET_ADMIN
   ports:
     - 8008:8008/tcp
     - 1194:1194/udp
   devices:
     - /dev/net/tun:/dev/net/tun
   volumes:
     - data:/etc/data
   environment:
     - WEBPORT=8008

volumes:
  data:

The container starts the web proxy, web shell and config files web server automatically when deployed. The OpenVPN server is started additionally if found configured.

The provided web pages can be reached with

An Internet router interlinks between local network devices such as the OpenVPN server device and the Internet.

Depending on your Internet provider contract the router gets either a constant Internet IP address forever which makes configuration easy or a dynamic one (usually every 24hrs). Either of the two methods influence the OpenVPN server configuration.

In latter case a DNS provider of your choice is needed first reserving you a public and constant DNS name (e.g. mypersonaladdress.dyndns.org) while providing a service that enables mappping the name to the dynamically changing IP address of your router.

Enable this function in your router and enter the domain credentials received from your DNS provider. The router will then automatically report its dynamically changing Internet IP address to the provider who in turn maps it to your public DNS name and update the global Internet DNS database.

Enable this function in your router to let it forward external Internet traffic on the specified OpenVPN server port (e.g.1194/udp) to the local IP address/port of your OpenVPN server device.

The OpenVPN server comes unconfigured. To configure it visit the web page .../shell in your browser.

In the window prompt (e.g. root@42f19c945b6f:~#) enter the command configure and press enter to start the configuration procedure through the PiVPN installer. For detailed help visit PiVPN help.

The installer will ask for several settings. Here is a typical configuration example

After the setup the configuration files can be created.

For a secure tunnel a server and a client configuration file pair needs to be created. The server file will remain in the container whereas the matching client file is to be imported into the OpenVPN client program.

To create a file pair enter the command pivpn add on the web page .../shell and press enter. When asked enter a name and a password and server and client files will be created.

To download the corresponding client file visit the web page .../config (a refresh click may be necessary). In the listed directory tree locate your client *.opvn file under your given name. Click it to download it and import it into your OpenVPN client.

The OpenVPN server configuration is completed and the server can be started.

Restart the container after configuration to start the OpenVPN server.

Copyright (c) Hilscher Gesellschaft fuer Systemautomation mbH. All rights reserved. Licensed under the LISENSE.txt file information stored in the project's source code repository.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained). As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

Hilscher Gesellschaft fuer Systemautomation mbH www.hilscher.com