Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
docker_notes:docker-deluge [2024-01-10 Wed wk02 19:24] – [Docker Deluge Image / Service] baumkpdocker_notes:docker-deluge [2024-01-10 Wed wk02 19:51] – [OpenVPN setup] baumkp
Line 118: Line 118:
 chmod 660 /dev/net/tun chmod 660 /dev/net/tun
  
-echo "nameserver 192.168.1.1" > /etc/resolv.conf+echo "nameserver 192.168.1.14" >> /etc/resolv.config  #This adds my primary LAN name server 
 +echo "nameserver 192.168.1.2" >> /etc/resolv.config  #This adds my secondary LAN name server 
 +echo "103.231.89.219 au-mel.pvdata.host"  >> /etc/hosts #This adds a PrivatVPN host to the host DNS 
 +echo "103.231.88.203 au-mel.pvdata.host"  >> /etc/hosts #This adds a PrivatVPN host to the host DNS 
 +echo "143.244.63.96 au-syd.pvdata.host"  >> /etc/hosts #This adds a PrivatVPN host to the host DNS 
 +echo "143.244.33.81 sg-sin.pvdata.host"  >> /etc/hosts #This adds a PrivatVPN host to the host DNS 
 + 
 +/usr/sbin/openvpn /etc/openvpn/privatvpn.conf &  #This runs the openvpn program in background using nominated configuration file 
 </code>++ see [[https://serverfault.com/questions/1003011/openvpn-error-cannot-open-tun-tap-dev-dev-net-tun-no-such-file-or-directory|OpenVPN - ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)]] </code>++ see [[https://serverfault.com/questions/1003011/openvpn-error-cannot-open-tun-tap-dev-dev-net-tun-no-such-file-or-directory|OpenVPN - ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)]]
   *Inside container command to run ''/usr/sbin/openvpn /etc/openvpn/privatvpn.conf'', add & to free up terminal   *Inside container command to run ''/usr/sbin/openvpn /etc/openvpn/privatvpn.conf'', add & to free up terminal
Line 180: Line 188:
  
 =====Docker network===== =====Docker network=====
-As described  in the vpn section [[https://wiki.kptree.net/doku.php?id=tech_notes:docker-deluge#openvpn_setup|openvpn setup]], I decided to go with the docker macvlan network setup. This needs to be separately created and can then be called up when the container is run.  A static ip address can be assigned when run.+As described  in the vpn section [[https://wiki.kptree.net/doku.php?id=docker_notes:docker-deluge#openvpn_setup|openvpn setup]], I decided to go with the docker macvlan network setup. This needs to be separately created and can then be called up when the container is run.  A static ip address can be assigned when run.
 <code bash>  <code bash> 
 docker network create -d macvlan  \ docker network create -d macvlan  \