some noob questions

[robinby]

Firstly thank you for your great work. i use your Transmission on my Synology DSM 6.0 System. But i am not good at Computer. May i ask some question about it.

1. I create the docker container with your classic command. It works well. When i shut down my NAS and reboot it, i tried to start the created Container, It appeared error like ''Cannot open TUN/TAP ''.
   what is the problem with it ? Should i not shut down the nas directly or should i pause the torrent , stop the Container,exit the docker, then shut down the nas? what is the steps of power off NAS?
2. how to resume the created container after reboot?
3. Sometimes i want to change the Openvpn. Because i want to choose the fastest VPN Server. Do i have to creat another container for that? Or can i change the environment variables in the existent container?
4. the container is over Openvpn and the NAS over myself ISP Provider. They have different IP addresses. Is that right？

Thank you very much.

[robinby]

Hallo, for question 1, I think I forgot to run with ./TUN.sh at first . Do I have to run it with ./TUN.sh every time when restart the container?

[robinby]

for question 2, the values of the Environment ''OPENVPN_CONFIG'' ''TRANSMISSION_PEER_CONGESTION_ALGORITHM'' and ''TRANSMISSION_SCRIPT_TORRENT_DONE_FILENAME='' can not be empty while i editing the ''OPENVPN_CONFIG'' to another better VPN server before i restart the container again.

[haugene]

Hey. So I'll try to answer your questions, but I think I need more information if you're still struggeling with some of these issues.

1. Seems you figured it out. Either way I don't use the container on a NAS, so I don't know. But if you read the README there is explicit mentioning of "To make it work after a nas restart, create an automated task in your synology web interface". So yeah, every time I guess.
2. Depends on how you're running this. With the docker cli you'd simply do "docker start " and it should be up and running again. For the environment variables you're mentioning, I don't understand? What are you trying to do?
3. Yes, you would typically change servers by creating a new container with the config you want. You can change environment variables of a running container, but it's not the way to go here... If you change these settings often(like alternating a some configs or whatever) you can have lots of containers laying around named after the config they use and you can stop and start containers as you want depending on the config you want.
4. Your NAS will have an IP from your router, and if you've forwarded ports or put it in a DMZ then it will also be accessible on the IP provided by your ISP. The IP of the Docker container is typically in the 172.17.0.0/24 range, and then the container will have another interface (typically tun0) which will get an IP address from your VPN provider. The traffic from the torrents will be routed through tun0 while local traffic (like the WebUI) will be routed through the containers eth0 interface.

Let me know if you have more issues. But if you feel something isn't working as it should, please provide the run commands and logs so that I can reproduce the error.

[ghost]

Hello @robinby

1. As @haugene said, you have to run it on every boot and this is specified in the doc.
2. On synology their is a checkbox "Enable auto-restart" to resume container in the container setting page, just check it and it will work.

[robinby]

@haugene, Thank you for your help. And for the environment variables, i want to change the ''OPENVPN_CONFIG'' to ''NL2 UDP '' but the container was created with ''OPENVPN_CONFIG=NL1 UDP ''. When i stopped the container to set the environment variables, i have to set the ''TRANSMISSION_PEER_CONGESTION_ALGORITHM'' and ''TRANSMISSION_SCRIPT_TORRENT_DONE_FILENAME'' too. They can not be setted with non-values empty as Dockerfile . what should i set them to?
TY

[haugene]

I don't understand. What do you mean you have to set the transmission environment variables? You should be able to change them as you wish. Both openvpn config and transmission settings are read by the startup script on each container start. Logs?

[robinby]

i mean change the “openvpn_config”

[haugene]

Yeah, I get that. But then you said you had to change two of the transmission settings as well and I'm wondering why. Can't you just change your openvpn config? What commands are you running here, do you have logs?

[robinby]

I can't just change openvpn_config, because that two environment variables must be setted some values. They can't be empty when I apply the change of openvpn _config. I don't know why.

[jgeusebroek]

Try NL3 UDP config. I tried this yesterday and found NL1 didn't work, NL3 did.
(might be changed keys or something)

[robinby]

@jgeusebroek kiss, it works, thank you so much

[robinby]

@jgeusebroek do you use Transmission on Synology? how can you change the ''openvpn_config'' in created container? sometimes i want to change another config without creating a new container.

[jgeusebroek]

Sorry, I don't actually use this container. I just tried it, and finally created my own container.
I have my VPN endpoint at my router / firewall, and not in the container.

IIRC the readme contains information on how to use your own VPN.

[ghost]

@robinby
To edit config on a syno, just stop the container, edit config, remove var that doesn't need to be set, save.

[haugene]

Allright @robinby, you got stuff working yet? Think I'm going to close this issue if you don't have any other questions or issues.