From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, oury.dustin@posteo.net,
Raghav Gururajan <rvgn@disroot.org>
Subject: Re: Tor over VPN
Date: Wed, 12 Jun 2019 09:08:03 +0200 [thread overview]
Message-ID: <C4FA1E68-CC4F-42EA-AD73-42D9B34AF7D5@lepiller.eu> (raw)
In-Reply-To: <850227f7533ac7757c5c1c5201a40437@posteo.net>
Le 12 juin 2019 04:26:54 GMT+02:00, oury.dustin@posteo.net a écrit :
>I too wish to get an answer to this so it would be easy for somebody
>non-technical to wrap their head around it. I'm currently doing
>open-vpn
>as root from the desktop and then running tor after it and configuring
>icecat afterwards to connect to TOR
>
>On 11.06.2019 22:27, Raghav Gururajan wrote:
>> Hello Guix!
>>
>> 1) How to use tor over vpn? That is, my system should connect to tor
>> network via
>> vpn.
>> 2) Should I enable both tor-service-type and openvpn-client-service?
>> 3) Do tor and vpn operate on same level as per OSI model?
>>
>> Thank you!
>>
>> Regards,
>> RG.
I think if you activate both services, it will work. Openvpn creates a new virtual network device that gets its own ip and network configuration. It's configured to go through your actual device via routes. Tor will simply try to communicate with another server on the internet. If openvpn has configured your computer to have a default route through the vpn, then tor connection will have no choice but to go through the vpn. Does it make sense?
You can check what your routes are with "ip r".
next prev parent reply other threads:[~2019-06-12 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 20:27 Tor over VPN Raghav Gururajan
2019-06-12 2:26 ` oury.dustin
2019-06-12 7:08 ` Julien Lepiller [this message]
2019-06-12 12:52 ` oury.dustin
2019-06-12 13:58 ` Raghav Gururajan
2019-06-12 13:48 ` Raghav Gururajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C4FA1E68-CC4F-42EA-AD73-42D9B34AF7D5@lepiller.eu \
--to=julien@lepiller.eu \
--cc=help-guix@gnu.org \
--cc=oury.dustin@posteo.net \
--cc=rvgn@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).