daveanderson

Members
  • Posts

    2
  • Joined

daveanderson's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Gotcha, I understand now. My mind had linked the term 'killswitch' to the client solutions provided by the VPN providers. After reading the FAQ your solution has become much clearer. Guess that's why it pays to read the FAQs first 🙄 Thanks again for the explanation
  2. I have a query about the PrivoxyVPN docker and the 'killswitch' that it contains. I am trying to set up a single VPN docker with multiple dockers passing packets through it out to the VPN endpoint. I have been successful in setting up the binhex-privoxyvpn docker, connecting to my VPN provider, and configuring the binhex-nzbget docker to pass all data through the VPN tunnel (screenshot of dockers attached). Running 'curl ifconfig.io' on both docker consoles reveals the VPN provider's IP address. If I terminate the VPN connection by 'kill {openvpn pid}' on the privoxyvpn docker then I can no longer get a repsonse from the 'curl ifconfig.io' command on the nzbget docker - all good so far. My query comes from the fact that after running a 'ping 8.8.8.8' command on the nzbget docker and then killing the VPN connection, there was still a response being received whilst the VPN connection was down. I have attached a screenshot of the ping repsonses and you can see that initially there was a response time of approx 470ms going through the VPN, then when the VPN was cut the response times dropped to about 9ms and then went back up to the original 470ms when the VPN had automatically reconnected. 9ms is the response time I get when I execute a ping 8.8.8.8 through my ISP connection - hence it appears that when the OpenVPN is disconnected, some traffic (IMCP packets at least) appear to be traversing through my ISP connection. I guess I have 2 questions - 1) have I followed the correct steps above in order to test for packet flow whilst the VPN is down, and 2) if several dockers are in the process of downloading and communicating to other servers / trackers when the VPN connection goes down, will this expose the traffic to my ISP and allow them to log those connections I am making whilst the VPN is disconnected. Apologies for the long post but I want to make sure that this setup can protect my connection privacy from my ISP including when an interruption to the VPN happens. The supervisord.log file from the privoxy docker is also attached for any reference needed. privoxy_supervisord.log