Network Type limitations?

[Raidersan]

Hi,

I have a limited understanding of Docker but just enough to have managed to convert most of my plugins to Dockers.

When I decided to look for one that would offer a openvpn/transmission combination, I had to go 'outside the box' and get a container that is not part of the usual unraid repositories. I went for this one: https://hub.docker.com/r/haugene/transmission-openvpn/

I got it up and running without too many hassles but it was clear that the routing set up by openvpn was not working. With the help of the very helpful author we got to the conclusion that UNnraid does something different and this is why I thought I ought to ask the clever ones here about our findings.

 

The author mentioned that I dont need the bridged network option, and that on his (running) setup, he does not specify this. I started to look at network type on the Unraid docker setup and realised that if Bridge is selected, the docker container seem to have a very different setup compared to what the author describes as a normal container, i.e. there is no docker0 interface with a 172.x.x.x interface which is crucial to the setup of this openvpn container. I then looked at using the Host network option, but this seem to remove the port mapping facilities of the bridge setup.

 

My question is then how do you setup a container so that Bridge is not selected but for which port mapping is setup, such as this command would allow:

 

docker run --privileged  -d \
              -v /your/storage/path/:/data \
              -e "OPENVPN_PROVIDER=PIA" \
              -e "OPENVPN_CONFIG=Netherlands" \
              -e "OPENVPN_USERNAME=user" \
              -e "OPENVPN_PASSWORD=pass" \
              -p 9091:9092 \
              haugene/transmission-openvpn

 

Many thanks!

[lonix]

Hi,

I have a limited understanding of Docker but just enough to have managed to convert most of my plugins to Dockers.

When I decided to look for one that would offer a openvpn/transmission combination, I had to go 'outside the box' and get a container that is not part of the usual unraid repositories. I went for this one: https://hub.docker.com/r/haugene/transmission-openvpn/

I got it up and running without too many hassles but it was clear that the routing set up by openvpn was not working. With the help of the very helpful author we got to the conclusion that UNnraid does something different and this is why I thought I ought to ask the clever ones here about our findings.

 

The author mentioned that I dont need the bridged network option, and that on his (running) setup, he does not specify this. I started to look at network type on the Unraid docker setup and realised that if Bridge is selected, the docker container seem to have a very different setup compared to what the author describes as a normal container, i.e. there is no docker0 interface with a 172.x.x.x interface which is crucial to the setup of this openvpn container. I then looked at using the Host network option, but this seem to remove the port mapping facilities of the bridge setup.

 

My question is then how do you setup a container so that Bridge is not selected but for which port mapping is setup, such as this command would allow:

 

docker run --privileged  -d \
              -v /your/storage/path/:/data \
              -e "OPENVPN_PROVIDER=PIA" \
              -e "OPENVPN_CONFIG=Netherlands" \
              -e "OPENVPN_USERNAME=user" \
              -e "OPENVPN_PASSWORD=pass" \
              -p 9091:9092 \
              haugene/transmission-openvpn

 

Many thanks!

 

Bridged is the default way docker handles networking and thus does not need to be set in a normal docker enviorment.  Basicly there are 3 Network Types in docker, Bridged, Host and None.

 

Bridged: Is the normal setup and works by mapping a series of ports from the host to the guest. (container)

Host: This is a setup where you rather give the container direct and equal access to the host nic.

None: this gives the container no network interface to work with.

 

Based on the fact you are running --privileged and a port transform, its gonna be hard to say excatly what is your issue. May i suggest trying out: binhex's container with binhex-delugevpn, i know its not the software you want, but it gives you a chanse to look at something that we "know" is working.

[CHBMB]

As an alternative, binhex has created just what you're after using Deluge instead of Transmission if you're amenable to a change in torrent client?

 

Here it is if you are interested, it also acts as a proxy server so you can route traffic through it.

 

Deluge is a full-featured ?BitTorrent client for Linux, OS X, Unix and Windows. It uses ?libtorrent in its backend and features multiple user-interfaces including: GTK+, web and console. It has been designed using the client server model with a daemon process that handles all the bittorrent activity. The Deluge daemon is able to run on headless machines with the user-interfaces being able to connect remotely from any platform.

 

This Docker includes OpenVPN to ensure a secure and private connection to the Internet, including use of iptables to prevent IP leakage when the tunnel is down. It also includes Privoxy to allow unfiltered access to index sites, to use Privoxy please point your application at "host ip:8118"

[Raidersan]

Thanks for that useful pointer, I will consider deluge once I get it running!

It fails for me, but I need to find the original thread to report the problem.

 

[CHBMB]

Thanks for that useful pointer, I will consider deluge once I get it running!

It fails for me, but I need to find the original thread to report the problem.

 

I think I linked to the support thread for it in my previous post..

[mr-hexen]

I switched from transmission to deluge for the vpn functionality. It works great.