AnonSurf on Parrot Linux is the built-in tool that routes your whole system’s traffic through the Tor network with a single command. This guide shows you how to start it, stop it, check that it is actually working by verifying your public IP, change your Tor circuit, and recover when something goes wrong. Everything here is meant for protecting your own privacy on your own machine; AnonSurf is not a tool for hiding activity against systems you are not authorised to touch, and it will not make careless behaviour anonymous.
This is an independent guide. For the short reference that ships with the distribution, see the AnonSurf page in the documentation library. For the deeper question of whether a Tor-everything approach fits your threat model at all, read Parrot Linux vs Tails.
What AnonSurf on Parrot Linux actually does
AnonSurf is a wrapper around Tor plus a set of firewall rules. When you start it, it does four things:
- Starts the Tor service if it is not already running.
- Rewrites the system’s packet-filter rules so that outbound TCP connections are transparently redirected into Tor’s transparent proxy port.
- Redirects DNS lookups to Tor’s DNS port so your resolver queries do not leak to your ISP.
- Blocks most traffic that cannot be carried over Tor, such as UDP, so it fails closed rather than leaking.
Because the redirection happens at the firewall level, every application is affected, not just the browser. That is the main difference from simply opening Tor Browser: a terminal curl, a package manager, a chat client, all of them go through Tor whether they know it or not.
The flip side is that anything Tor cannot carry stops working. Video calls, most online games, and anything that needs UDP or a direct connection will fail while AnonSurf is active. Treat that as expected behaviour, not a bug.
Check that AnonSurf is installed
AnonSurf is preinstalled on the Security and Home editions. On an Architect or Cloud install, or if you have removed it, install it from the Parrot repository:
sudo apt update
sudo apt install anonsurfConfirm the command is available and see the sub-commands it accepts:
anonsurf --helpIf apt cannot find the package, your system is probably pointing at a stale or non-Parrot mirror. Fix that first using how to change the Parrot Linux mirror, then retry.
Record your real IP before you start
You cannot verify that AnonSurf works unless you know what your normal public IP is. Before enabling it, note the address once:
curl -s https://check.torproject.org/api/ipThe response is a small JSON object with two fields: IsTor, which should be false right now, and IP, which is your real public address. Keep that value in mind for the comparison later.
How to start AnonSurf
Starting it requires root, so prefix the command with sudo:
sudo anonsurf startYou will see a short log as it starts Tor and applies the firewall rules. Depending on your version it may also ask whether to kill running applications first. Say yes if you are serious about not leaking: a browser that already has open connections can keep using them for a while, and a half-anonymised session is worse than a clearly non-anonymous one.
Give it a few seconds. Tor needs to bootstrap, build a circuit and confirm it has a working path before traffic flows. If the start command returns but web pages hang, wait ten to thirty seconds and try again before assuming it failed.
Verify your IP after starting AnonSurf
This is the step most guides skip, and it is the only step that proves anything. Run the same check as before:
curl -s https://check.torproject.org/api/ipNow IsTor should be true and IP should be a completely different address from the one you recorded. If both of those are true, AnonSurf is doing its job for TCP traffic.
AnonSurf also has a built-in shortcut that does roughly the same thing:
anonsurf myipUse the curl check anyway. The built-in command tells you what AnonSurf thinks your address is; an independent request through an ordinary program tells you what the outside world sees. The two should agree. If they do not, something is wrong with the redirection rules and you should stop and investigate rather than carry on.
To confirm DNS is also going through Tor, resolve a name while AnonSurf is active and compare the behaviour with it disabled:
dig +short example.orgOver Tor, the answer still comes back, but the query never reaches your ISP’s resolver. If dig hangs or fails entirely, the DNS redirect rule has not been applied; restart AnonSurf as described below.
Check AnonSurf status and the Tor service
AnonSurf keeps its own notion of whether it is active:
sudo anonsurf statusPair that with the systemd view of Tor itself, because AnonSurf can report active while Tor has crashed underneath it:
systemctl status tor
journalctl -u tor -n 30 --no-pagerA healthy Tor log ends with a line saying bootstrapping reached 100 percent. If it stalls at a lower percentage, your network is likely blocking Tor’s directory authorities or the relay ports; the Troubleshooting Tor page covers that situation, including the use of bridges.
Change your Tor identity without stopping
Tor reuses a circuit for a while, so your exit IP stays the same for several minutes. To force a new circuit and therefore a new exit address, ask AnonSurf for a new identity:
sudo anonsurf changeidThen run the curl check again. The IP value should have changed. Note that a new circuit does not reset anything inside your applications: cookies, logged-in sessions and browser fingerprints are all still there. Changing identity at the network layer only helps if the application layer is not quietly re-identifying you.
How to stop AnonSurf cleanly
When you are done, stop it so the firewall rules are removed and normal networking returns:
sudo anonsurf stopVerify that you are back on your real address with the same curl command; IsTor should return to false and IP should match the value you recorded at the start. If it does not, or if networking seems broken after stopping, a restart of the service usually clears leftover rules:
sudo anonsurf restart
sudo anonsurf stopIn the rare case that rules are still stuck, you can inspect the current firewall state and compare it to what your normal configuration looks like. The Parrot Linux firewall setup guide explains how to read nftables and ufw output on this distribution.
Common AnonSurf problems and fixes
| Symptom | Likely cause | What to do |
|---|---|---|
| Pages hang right after start | Tor still bootstrapping | Wait 30 seconds, check journalctl -u tor |
IsTor stays false | Firewall rules not applied, or a VPN client is overriding them | Disconnect the VPN, run sudo anonsurf restart, re-check |
| apt fails during update | Mirror unreachable over Tor or very slow | Stop AnonSurf for package updates, or accept the slowdown |
| No network after stop | Leftover redirect rules | sudo anonsurf restart then stop; reboot if still broken |
| Video calls fail | UDP is blocked by design | Expected; stop AnonSurf for that session |
If AnonSurf refuses to start at all after a recent upgrade, make sure the system itself is fully up to date with sudo parrot-upgrade as described in how to update and upgrade Parrot Linux safely. Version mismatches between the AnonSurf package and the Tor package are a common cause of silent failures.
What AnonSurf does not protect you from
It is worth being blunt about the limits, because the single-command convenience makes it easy to over-trust:
- Application-level identity. Logging into an account that already knows who you are defeats the purpose regardless of the route.
- Browser fingerprinting. A normal browser over Tor is still a normal browser. Tor Browser bundles hardening that AnonSurf does not add.
- Traffic you started before enabling it. Connections already open can persist; this is why killing applications at start matters.
- Local logs and disk state. Unlike an amnesic live system, Parrot keeps history, caches and logs on disk.
- Exit node visibility. Unencrypted traffic can be read by whoever runs the exit relay. Use HTTPS everywhere.
For a broader explanation of how Tor itself works and its design limits, the Tor Project website is the right primary source.
FAQ: AnonSurf on Parrot Linux
Does AnonSurf start automatically at boot?
No. It is off by default and must be started manually each session. Leaving it permanently on is possible but makes package updates slow and breaks many applications, so most people enable it only when they need it.
Is AnonSurf the same as a VPN?
No. A VPN moves trust from your ISP to the VPN operator. Tor splits the path across three relays so no single party sees both ends. They solve different problems, and running both at once often breaks AnonSurf’s rules; pick one for a given session.
Can I use AnonSurf together with Tor Browser?
You can, but it is usually unnecessary. Tor Browser carries its own Tor instance, and routing it through AnonSurf’s system-wide Tor simply nests two circuits, which slows things down without a clear benefit. Use AnonSurf for non-browser traffic and Tor Browser for browsing if you want the strongest browser hardening.
[…] scope matters on Parrot, because the distribution also ships AnonSurf, which pushes the whole system through Tor using iptables rules. The two tools solve different […]