It appears that both dd-wrt and TomatoUSB firmware builds are available for the Linksys E4200. Both dd-wrt and TomatoUSB are Linux-based firmware. Either firmware can run either an OpenVPN client or a Tor client, but not simultaneously.
By the way, while the Linksys E4200 is adequate as a Tor client, it arguably doesn't have enough CPU or ...
$ openvpn --help
--socks-proxy s [p] [up] : Connect to remote host through a Socks5 proxy at
SocksPort 9050 # what port to open for local application connections
SocksListenAddress 127.0.0.1 # accept connections only from localhost
As a newbie, you are probably meet troubles with wrapping a connection.
While you'll start ...
Unless you can somehow prevent your VPN provider from knowing who you are or what your IP address is, there will always be the possibility of your anonymity being compromised.
You could conceivably sign up to a service under a pseudonym, pay for the service using a bitcurrency that you had sourced anonymously, and ensure every time you connected to ...
This can be done using VirtualBox VMs. It's easy with Whonix. Just set up a VPN client in the workstation VM in /etc/openvpn/, and add socks-proxy 192.168.0.10 9150 up and socks-proxy-retry to the configuration file. The requirement for an up proxy-authentication file is an OpenVPN bug. The up file must exist, but it's not parsed, so its content doesn't ...
VPN must be considered more of a circumvention tool rather than an anonymity tool. Even for circumvention Tor stands very well in cases that public known entry nodes are blocked, with the use of (obfuscate) bridges.
If you're seeking anonymity Tor is the way to go. Tor is using a three-hop circuit to establish an anonymous path to your destination. No ...
I have found that this works pretty well:
(For this, I'm assuming that you have installed tor using "apt-get install tor" and not using the Tor browser bundle.)
Add this line to the "/etc/tor/torrc" file to tunnel vpn traffic:
SocksPort 9150 PreferSOCKSNoAuth
Then you will need to tell OpenVPN to use a proxy.
Add this to your VPN config file:
You probably want to have a read through the Pluggable Transport specification, they're controlled and configured through environment variables. You'll need to set them appropriately to get it to work with OpenVPN. Note that obfs4 also requires the client to have a "certificate" to be able to connect.
I'm unsure why tor cannot terminate obfs4, maybe you've ...
Removing the reverse DNS doesn't matter because what the DNS used to be is sitting around in, for example the Rapid7 Sonar scans. They regularly scan the entire IPv4 address space's PTR records and publish the results. Your link to that server is baked into the internet and it will not go away.
Yes you will be linked by your payment data and following money ...
To rephrase what you are saying: you'd like to establish a VPN tunnel and then use Tor to connect to external hosts across that tunnel.
You can achieve this by running Tor on the VPN server and configuring it to listen on the VPN IP.
i.e. if the VPN IP of the server is 10.0.0.1, you can configure Tor (in torrc) with:
Then, your VPN ...
Yes Tor Browser does a great job of preventing DNS Leaks. Even torsock on the Linux CLI does an admirable job of preventing DNS Leaks for Linux CLI apps. I did some testing on my own with several apps and saw this for myself.
If you ever do find a DNS leak, that would be considered to be a major security hole and would be fixed ASAP.
I can't tell you all ...
A BitTorrent client learns its actual IP Address through port mapping protocols. It uses NAT - PMP, PCP and uPnP for external IP Address discovery.
To join a torrent, a client sends an announce message to the
tracker that maintains the list of all peers in that torrent. This announce message contains an optional parameter, the IP address of the interface ...
You should just run Tor on the local system after connecting to the VPN.
The reason for this is that the Tor data will be encrypted before it reaches your VPN server, making the connection between you and the Tor network end-to-end encrypted.
If you set up Tor on the VPN server then the server would see the plaintext of traffic you were sending to Tor. It ...
obfs2 should be considered dead and buried. A passive observer can remove the obfuscation (and an active attacker can remove obfs3).
The "Corrupted magic value" is actually part of the protocol, it's not related to the "version number", it expects that a "magic" value (obfs2.py, obfs2.h) is part of the decrypted message.
You can read more about obfs2 here, ...
obfs4 and obfs3, among others, are "pluggable transports", and the protocol they speak to Tor is well specified. You could write a program / script to implement that protocol in order to use any pluggable transport for your own purposes.
Shameless plug: I have written a Python 3 program that takes a pluggable transport binary and creates a standalone TCP ...
You will probably need to create a transparent proxy (which uses socks to forward traffic via Tor), and have traffic routed through that. You will also need to do something funky with DNS, to stop clearnet DNS traffic leaking out of your VPN server.
So it's technically possible, but difficult. Some other systems exist which do this, for example http://...
Install Wireshark on the host machine and the VM. I see three places to capture:
the host physical NIC;
the VPN tun interface in the host; and
the virtual NIC in the VM.
Capture 1 should show encrypted VPN traffic with the login server. You should see no Tor traffic there, because it's encapsulated in the VPN packets. Captures 2 and 3 should show ...
You are correct. There is no issue with that.
There are some considerations, the same as running a relay on your home connection: Some websites block access from all Tor relays, exit or not. Now that your IP and hostname are listed on public web pages, you may get more 'traffic' probing for vulnerabilities.