Search Results

First of all - you can not see the exit node's IP in your WireShark: it's encapsulated inside a 3-layered "onion". What you can see is: A guard node(s) that are used to Enter Tor network by your tor …

Duplicate the line # Allow Tor process output iptables -A OUTPUT -o $_out_if -m owner --uid-owner $_tor_uid -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -m state --state NEW -j ACCEPT and the line # …

Do not abuse the way that Tor is built up! Use it as a SOCKS5S proxy, it will work fine. Mismanaging the logic of Tor leads to privacy leaks. In your particular case - just use it as a proxy

It happens when your tor instance is either not yet synchronized to the network - or it was a DisableNetwork=1 situation when it was instructed to disconnect from the network but do not terminate. Tor …

it's a control connection from your nyx - the red line. Additionally - keep in mind that Tor nodes are not just "standing still", they are participating in the consensus - including node speed measure …

Self-signed is the only option if we're speaking about security! But you can make it even more secure ;) First of all, make the DH params openssl dhparam -out dhparams.pem 4096 Second - you need the …

You need to parse the consensus data, all the actions are digitally signed. What exact data/votes/actions is broadcasted - it was changing from time to time due to the protocol versions, but as far as …

As a Tor Browser, so the Brave with Tor - are combo-packs for an unskilled users. If you need a deep tweak - use an insulation and regular browser fully-routed through Tor - and on that level you can …

This problem is a frequent one on Windows, so looks like on macOS too now. The system built-in service is "accidently" either blocks or occupies 9050 and 9051 ports - point them to 19050 and 19051. Th …

It's about the $HOME environment variable that still points to the /root folder and of course it's not writable or readable by other users. To avoid that set Data directory and the user in /etc/tor/to …

You need Tor's DNS port on the Leader to be in /etc/resolv.conf as a primary one, so dot-onion hostname for Follower will be resolvable into Tor's virtual network mapped. Your problem starts when the …

You're missing the local host configuration. The user-based connection issues on a tor side are only taking place when you are using Unix socket, not TCP socket …

Yes, onion sites are just the same web sites with all the standards and conventions

You don't need to open any ports for nyx: it's using localhost. To specify it better add ControlListenAddress 127.0.0.1:9051 to your torrc and it will be just fine. Service names you're asking for is …

It's bootstrapping :D Check the logs: it has to be up and running so you will have an working instance to control, so that's why it happens after that time. But anyway - it should respond you. So use …