So the problem has been around for a bit I see as this is an old thread. It sounds like a reasonable solution. Pull requests are always welcome.
Ok. So I don't have all the answers yet, but here are some findings so far.
I've tried three different cases, and all the configs and logs plus iptables routes are pasted below.
I've tried three different cases, and all the configs and logs plus iptables routes are pasted below.
Case 1:
Standard setup, original image, using LOCAL_NETWORK variable to try to make Transmission accessible on my local LAN.
Standard setup, original image, using LOCAL_NETWORK variable to try to make Transmission accessible on my local LAN.
Case 2:
Ditching the LOCAL_NETWORK variable
Ditching the LOCAL_NETWORK variable
Case 3:
Same setup as case 2, but I removed the three route commands in the ovpn file.
For reference, the three consecutive lines starting with this one
Same setup as case 2, but I removed the three route commands in the ovpn file.
For reference, the three consecutive lines starting with this one
Result:
In the first case we see two RTNETLINK errors. In the beginning
In the first case we see two RTNETLINK errors. In the beginning
RTNETLINK answers: Invalid argument
and then at the end RTNETLINK answers: File exists
. Transmission is not available on host:9091, the request just hangs. This is typical behaviour when the local network route is not added, also described in the README. As I also fired up the proxy container I tested connecting through that instead, and it works. So Transmission is running and using http://ipmagnet.services.cbcdn.com/ I could verify that the traffic was routed through the VPN.But anyways, I figured that the first RTNETLINK error could be the LOCAL_NETWORK route. So I removed that from the config.
In the second case, without the local network settings, as expected the first error is gone.
In the third case, where I also removed the route options from the .ovpn file, the second error is also gone.
In all three cases Transmission is running and the IP check says that the traffic is routed through VPN. The route stuff probably need more investigation to know what's needed and why PureVPN is different from others when it comes to the LOCAL_NETWORK variable and have the route options in their configs.
Later I'll try to compare with PIA that I'm using, but this is as far as I came today. Maybe someone can do some more digging as well?
Config for Case 1:
docker-compose.yml:
Logs:
Output from
ip r
:Case 2:
docker-compose.yml:
Same as for Case 1, but without LOCAL_NETWORK line
Same as for Case 1, but without LOCAL_NETWORK line
Logs:
Output from
ip r
:Config for Case 3:
docker-compose.yml:
Same as for Case 2. Note that the image is changed as described.
Same as for Case 2. Note that the image is changed as described.
Logs:
Output from
ip r
:Forgive the newbie question.
I am trying to setup
eth1
in interfaces
:however, I am getting:
RTNETLINK answers: file exists
here are the results of
ifconfig
:what am i doing wrong?
l--'''---------''''''
l--'''---------''''''l--'''---------''''''
2 Answers
Manual methods are unlikely to work correctly if Network Manager is installed and running. If it is installed, it is advisable to set the details there:
If you have removed Network Manager, your interfaces file will also need a gateway and DNS nameservers:
Then get the system to re-read and use the changes:
Check:
chili555chili555
If you had been manually setting a temporary configuration, e.g by doing something like
sudo ifconfig eth0 10.0.0.100 netmask 255.255.255.0
, as described here, you should clear that up first:Now you can try again:
NagevNagev