[[Support] binhex - DelugeVPN]

On 1/13/2018 at 3:49 PM, Pans said:

So 

 

I'm having this issue, too (route add...)

 

To be clear, is LAN_NETWORK supposed to be the actual LAN network, or the Docker network? Or both?

 

I currently have it as the LAN network , 192.168.1.0/24, but the docker network is, from memory 172.17.0.0/16.

 

I'm also having another issue, where the VPN_DEVICE_TYPE is set to 'tun0', then in the iptables rules, it's adding tun00, which clearly isn't right.

 

All of this is on a QNAP server.

 

Having worked around the tun00 issue, here's the log from my QNAP server trying to run things. It seems to come up, and every once in a while even gets a connection, then the openvpn crashes/bails for some reason, and we get into about a 30 second restart loop.

 

In this case, it's running as UID and GID 0, as I thought it might have been a permission thing, but the results are the same using the correct UID/GID for my user.

 

Don't know if it matters, but the docker version is 1.11.2.

 

I've also attached the script I'm using to create the container, in case that is helpful. I've backed off strict-port-forward and privoxy in the hope they were the issue, but without a change. Also, note that this script removes the username and password arguments. I just deleted the lines, rather than change them, but rest assured they're there on the version I'm running. 

supervisord.log

deluge.sh

[[Support] binhex - DelugeVPN]

So 

On 1/12/2018 at 4:41 AM, binhex said:

 

no thats not the issue, it manages to get the tunnel ip address (from your log):-

 

2018-01-12 08:37:44,066 DEBG 'deluge-script' stdout output:
[debug] Valid IP address from tunnel acquired '188.72.98.244'

i think this might be your issue:-

 

Fri Jan 12 08:37:15 2018 ERROR: Linux route add command failed: external program exited with error status: 2

so that is normally a symptom of defining the wrong LAN_RANGE, can you double check this is correct:-

 

2018-01-12 08:37:10.701407 [info] LAN_NETWORK defined as '192.168.69.0/24'

Link to help section if your unsure, Q3:-

 

 

 

I'm having this issue, too (route add...)

 

To be clear, is LAN_NETWORK supposed to be the actual LAN network, or the Docker network? Or both?

 

I currently have it as the LAN network , 192.168.1.0/24, but the docker network is, from memory 172.17.0.0/16.

 

I'm also having another issue, where the VPN_DEVICE_TYPE is set to 'tun0', then in the iptables rules, it's adding tun00, which clearly isn't right.

 

All of this is on a QNAP server.