Anonsurf cannot resolve hosts

Briefly describe your issue below:
After I started anonsurf transparent proxy I cannot resolve domain names.

root@parrot:~ $ tor-resolve google.com
Oct 06 14:36:04.199 [err] Error while connecting to SOCKS host: Connection refused
root@parrot:~ $ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=64 time=0.065 ms
root@parrot:~ $ ping google.com
ping: google.com: Temporary failure in name resolution

Actually initially I didn’t have internet access (I could’t ping 8.8.8.8) so I had to add this iptables line:

root@parrot:~ $ iptables -A INPUT -i lo -j ACCEPT

So I thought maybe there’s another missing line I am not spotting to make dns resolution work.

Any tips?


What version of Parrot are you running? (include version, edition, and architecture)
Parrot 4.18.6-1parrot8 (2018-09-07)

What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)
Debian Standard

Configured to multiboot with other systems? (yes / no)
No

If there are any similar issues or solutions, link to them below:

If there are any error messages or relevant logs, post them below:

there seems to be an error with tor@default.service:

root@parrot:~ $ journalctl -xe
...
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.651 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/dow
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.651 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.651 [notice] Read configuration file "/etc/tor/torrc".
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.655 [notice] Scheduler type KIST has been enabled.
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.655 [notice] Opening Socks listener on 127.0.0.1:9050
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.655 [notice] Opening DNS listener on 127.0.0.1:5353
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.655 [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9040
Oct 06 14:52:41 parrot audit[3765]: AVC apparmor="DENIED" operation="mknod" profile="system_tor" name="/tmp/tor-proxy.log" pid=3765 comm="tor" requested_mask
Oct 06 14:52:41 parrot kernel: audit: type=1400 audit(1538830361.649:149): apparmor="DENIED" operation="mknod" profile="system_tor" name="/tmp/tor-proxy.log"
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.000 [warn] Couldn't open file for 'Log notice file /tmp/tor-proxy.log': Permission denied
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.000 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.000 [notice] Closing partially-constructed DNS listener on 127.0.0.1:5353
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.000 [notice] Closing partially-constructed Transparent pf/netfilter listener on 127.0.0.1:9040
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.000 [warn] Failed to parse/validate config: Failed to init Log options. See logs for details.
Oct 06 14:52:41 parrot tor[3765]: Oct 06 14:52:41.000 [err] Reading config failed--see warnings above.
Oct 06 14:52:41 parrot systemd[1]: tor@default.service: Main process exited, code=exited, status=1/FAILURE
Oct 06 14:52:41 parrot systemd[1]: tor@default.service: Failed with result 'exit-code'.
Oct 06 14:52:41 parrot systemd[1]: Failed to start Anonymizing overlay network for TCP.
-- Subject: Unit tor@default.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit tor@default.service has failed.
-- 
-- The result is RESULT.
Oct 06 14:52:41 parrot systemd[1]: tor@default.service: Service RestartSec=100ms expired, scheduling restart.
Oct 06 14:52:41 parrot systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Automatic restarting of the unit tor@default.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Oct 06 14:52:41 parrot systemd[1]: Stopped Anonymizing overlay network for TCP.
-- Subject: Unit tor@default.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 


-- Unit tor@default.service has finished shutting down.
Oct 06 14:35:21 parrot systemd[1]: tor@default.service: Start request repeated too quickly.
Oct 06 14:35:21 parrot systemd[1]: tor@default.service: Failed with result 'exit-code'.
Oct 06 14:35:21 parrot systemd[1]: Failed to start Anonymizing overlay network for TCP.
-- Subject: Unit tor@default.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit tor@default.service has failed.
...

but tor deamon seems ok:

root@parrot:~ $ systemctl status tor
  ● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
   Loaded: loaded (/lib/systemd/system/tor.service; disabled; vendor preset: enabled)
   Active: active (exited) since Sat 2018-10-06 14:52:39 CEST; 5min ago
   Process: 3733 ExecStart=/bin/true (code=exited, status=0/SUCCESS)   
   Main PID: 3733 (code=exited, status=0/SUCCESS)

 Oct 06 14:52:39 parrot systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)...
 Oct 06 14:52:39 parrot systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master).

and why this? (happens even if anonsurf is stopped):

root@parrot:~ $ torsocks nmap -p 80 8.8.8.8
Starting Nmap 7.70 ( https://nmap.org ) at 2018-10-06 15:01 CEST
route_dst_netlink: can't find interface "wlan0"

is this a fresh install ?
why do you use tor-resolve and torsocks ?
anonsurf’s main function is to route all traffic through tor without the need on any user interaction.