No connectivity in GW

claudi8b6 · July 6, 2016, 6:24pm

10.137.2.1 is eth0. Both VMs are connected to sys-firewall.

Patrick · July 6, 2016, 6:57pm

Good question. Good catch.

@claudi8b6 did you run whonixsetup? Please run the following command for debug purposes and post the output here.

cat /etc/tor/torrc

Not that I know.

I will come up with a replace-ips script with extensive debugging so we can look what is going on.

claudi8b6 · July 6, 2016, 8:37pm

Where? It’s ‘False’ in torrc as far as I can tell.

Just ran it. Same result (Bootstrapping 45% done, blah blah blah…)

entr0py · July 6, 2016, 10:10pm

My mistake. I was looking at the old, scrubbed (?) entries from /var/log/tor/log.

The relevant log is from Jun 29:

Jun 29 12:49:08.000 [notice] Tor 0.2.7.6 (git-605ae665009853bd) opening log file.
Jun 29 12:49:08.129 [notice] Tor v0.2.7.6 (git-605ae665009853bd) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1k and Zlib 1.2.8.
Jun 29 12:49:08.129 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 29 12:49:08.129 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jun 29 12:49:08.129 [notice] Read configuration file "/etc/tor/torrc".
Jun 29 12:49:08.132 [notice] You configured a non-loopback address '10.137.3.1:9050' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 29 12:49:08.132 [notice] You configured a non-loopback address '10.137.3.1:9100' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
...similar lines removed...
Jun 29 12:49:08.133 [notice] You configured a non-loopback address '10.137.3.1:9186' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 29 12:49:08.133 [notice] You configured a non-loopback address '10.137.3.1:9187' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 29 12:49:08.133 [notice] You configured a non-loopback address '10.137.3.1:9188' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 29 12:49:08.133 [notice] You configured a non-loopback address '10.137.3.1:9189' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 29 12:49:08.133 [notice] You configured a non-loopback address '10.137.3.1:5300' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 29 12:49:08.133 [notice] You configured a non-loopback address '10.137.3.1:9040' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 29 12:49:08.133 [notice] Opening Socks listener on 10.137.3.1:9050
Jun 29 12:49:08.133 [notice] Opening Socks listener on 10.137.3.1:9100
Jun 29 12:49:08.133 [notice] Opening Socks listener on 10.137.3.1:9101
Jun 29 12:49:08.133 [notice] Opening Socks listener on 10.137.3.1:9102
...similar lines removed...
Jun 29 12:49:08.134 [notice] Opening Socks listener on 127.0.0.1:9124
Jun 29 12:49:08.134 [notice] Opening Socks listener on 127.0.0.1:9125
Jun 29 12:49:08.134 [notice] Opening Socks listener on 127.0.0.1:9150
Jun 29 12:49:08.134 [notice] Opening DNS listener on 10.137.3.1:5300
Jun 29 12:49:08.134 [notice] Opening Transparent pf/netfilter listener on 10.137.3.1:9040
Jun 29 12:49:08.134 [notice] Opening Control listener on 127.0.0.1:9051
Jun 29 12:49:08.134 [notice] Opening Control listener on /var/run/tor/control
Jun 29 12:49:08.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jun 29 12:49:08.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Jun 29 12:49:08.000 [notice] Bootstrapped 0%: Starting
Jun 29 12:49:08.000 [notice] Bootstrapped 5%: Connecting to directory server
Jun 29 12:49:08.000 [notice] Signaled readiness to systemd
Jun 29 12:49:08.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Jun 29 12:49:09.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection
Jun 29 12:49:09.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus
Jun 29 12:49:09.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
Jun 29 12:49:09.000 [notice] New control connection opened from 127.0.0.1.
Jun 29 12:49:09.000 [notice] New control connection opened from 127.0.0.1.
Jun 29 12:49:10.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
Jun 29 12:49:11.000 [notice] Bootstrapped 25%: Loading networkstatus consensus
Jun 29 12:49:19.000 [warn] Socks version 71 not recognized. (Tor is not an http proxy.)
Jun 29 12:49:19.000 [notice] New control connection opened from 127.0.0.1.
Jun 29 12:49:19.000 [notice] New control connection opened from 127.0.0.1.
Jun 29 12:49:19.000 [notice] New control connection opened from 127.0.0.1.
Jun 29 12:49:20.000 [notice] New control connection opened from 127.0.0.1.
Jun 29 12:49:22.000 [notice] New control connection opened from 127.0.0.1.
Jun 29 12:49:22.000 [notice] New control connection opened from 127.0.0.1.
Jun 29 12:49:23.000 [notice] New control connection opened.
Jun 29 12:49:24.000 [notice] New control connection opened from 127.0.0.1.
Jun 29 12:49:24.000 [notice] New control connection opened from 127.0.0.1.
Jun 29 12:49:25.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.

Everything looks proper except the reload signal at the end. (Did you reload manually?)

Also, replace-ips doesn’t seem to be an issue. (10.137.3.1 is correct)

Might still be useful to see your torrc.

I’ve never run Whonix-Gateway through sys-firewall. What iptables rules does sys-firewall use?

Patrick · July 6, 2016, 10:21pm

entr0py:

Also, replace-ips doesn’t seem to be an issue. (10.137.3.1 is correct)

Above there was a log with the wrong IP which was not properly replaced.

entr0py · July 6, 2016, 10:31pm

I don’t understand this behavior but I checked my tor logs and it confirmed that every connection attempt prior to most recent attempt (or most recent day?) is “scrubbed”. My logs also show 10.152.152.10 for past connection attempts. Most recent entries have the correct 10.137.x.x addresses.

Patrick · July 6, 2016, 10:37pm

To be expected. sys-whonix by default is a TemplateBasedVM and Tor’s log will not persist since it is stored in the root image.

So this is not an uncommon bug.

Patrick · July 7, 2016, 7:31pm

I might have found and fixed bug. Can you please emulate the following commit? Apply this in your whonix-gw TemplateVM. Then shut down the TemplateVM and restart sys-whonix.

claudi8b6 · July 7, 2016, 8:17pm

It fails too… (Bootstrapping 25% done …)

entr0py · July 7, 2016, 8:33pm

What bug? Mine works fine without @default

How much time are you allowing for bootstrap? The last intact log was 20 secs… Something is causing Tor to reset (if not being done manually). Can you post a recent log? And torrc?

Patrick · July 7, 2016, 9:30pm

The “IP 10.152.152.10 appears in /var/run/tor/log” bug.

IP 10.152.152.10 should not ever appear in /var/run/tor/log. Can you confirm please after emulating the above git commit? @entropy

Can you confirm please after emulating the above git commit that there is no longer IP 10.152.152.10 in /var/run/tor/log? @claudi8b6

See if replace-ips now works properly. Run following command and post the output here please.

cat /usr/share/tor/tor-service-defaults-torrc | grep -i TransPort

Patrick · July 7, 2016, 9:42pm

This is also what the above git commit bug fix is for.
/lib/systemd/system/qubes-whonix-postinit.service ought to include Before=tor@default.service. Otherwise Tor runs before bind-directories is done, which is bad for two reasons.

DisableNetwork 1 will still be set in original (from TemplateVM) /etc/tor/torrc. (“User” [whonixsetup] modified DisableNetwork 0 would not be visible at that stage.) → The “why DisableNetwork is still true” bug.
replace-ips will not be done replacing IP 10.152.152.10 in /usr/share/tor/tor-service-defaults-torrc. → The “IP 10.152.152.10 appears in /var/run/tor/log” bug.

Whether the bug fix will solve @claudi8b6’s problem is unclear at this time.

entr0py · July 12, 2016, 4:10pm

The above git commits have no effect on TemplateVM’s /var/run/tor/log (which as you pointed out to me, is what we see when we restart our appVM) because:

lib/systemd/system/qubes-whonix-postinit.service returns false:

 ConditionPathExists=|/var/run/qubes-service/whonix-gateway
 ConditionPathExists=|/var/run/qubes-service/whonix-workstation

/usr/lib/qubes-whonix/init/qubes-whonix-postinit would also return false:

 if [ "$qubes_vm_type" = "TemplateVM" ]; then
    # Do none of the following in a TemplateVM.
    exit 0
 fi

Does this mean that Whonix-Gateway only works on my machine because I am winning a race condition that I was not aware of?

Patrick · July 12, 2016, 11:21pm

Tor should not be running in the TemplateVM anyhow. That is a bug which is fixed in git master. Not a big issue, since Tor cannot connect to the Tor network from the TemplateVM anyhow. Still useless to run Tor in the TemplateVM.

This is fine.

I don’t know yet. I guess we are fixing a valid bug here but it may or may not work for @claudi8b6. We’ll see.

IP 10.152.152.10 should not ever appear in /var/run/tor/log in sys-whonix. Can you confirm please after emulating the above git commit? @entropy

claudi8b6 · July 13, 2016, 3:16pm

It connected for the first time today, but still there’s no connectivity on whonix-gw template and in the gateway.
I still don’t understand how I was the only one to report that failure? I even tried to install Qubes 3.1 on a different machine.

Output from the Gateway:

user@host:~$ !56
cat /var/log/tor/log 
..............
Jul 13 07:44:42.122 [notice] Opening Socks listener on 10.137.3.1:9050
Jul 13 07:44:42.123 [notice] Opening Socks listener on 127.0.0.1:9150
Jul 13 07:44:42.123 [notice] Opening DNS listener on 10.137.3.1:5300
Jul 13 07:44:42.123 [notice] Opening Transparent pf/netfilter listener on 10.137.3.1:9040
Jul 13 07:44:42.123 [notice] Opening Control listener on 127.0.0.1:9051
Jul 13 07:44:42.123 [notice] Opening Control listener on /var/run/tor/control
Jul 13 07:44:42.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jul 13 07:44:42.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Jul 13 07:44:42.000 [notice] Bootstrapped 0%: Starting
Jul 13 07:44:42.000 [notice] Bootstrapped 5%: Connecting to directory server
Jul 13 07:44:42.000 [notice] Bootstrapped 45%: Asking for relay descriptors
Jul 13 07:44:42.000 [notice] Signaled readiness to systemd
Jul 13 07:44:42.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:44:53.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:44:53.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:44:53.000 [warn] Socks version 71 not recognized. (Tor is not an http proxy.)
Jul 13 07:44:53.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:45:54.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:45:54.000 [notice] No circuits are opened. Relaxed timeout for circuit 5 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. 11 guards are live.
Jul 13 07:45:55.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 1073/7023, and can only build 0% of likely paths. (We have 14% of guards bw, 14% of midpoint bw, and 16% of exit bw = 0% of path bw.)
Jul 13 07:45:55.000 [notice] Bootstrapped 50%: Loading relay descriptors
Jul 13 07:45:57.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:45:57.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:51:30.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:51:38.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 07:51:38.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 07:53:32.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:53:38.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 07:53:38.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 07:55:38.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 07:55:44.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:55:44.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:57:38.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 07:57:46.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:57:46.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:59:38.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 07:59:48.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 07:59:48.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:01:38.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 08:01:40.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:01:40.000 [notice] New control connection opened from 127.0.0.1.
...
Jul 13 08:23:43.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:23:53.000 [notice] New control connection opened from 127.0.0.1.
...
Jul 13 08:33:13.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:33:23.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:33:23.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:33:33.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:33:33.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:33:41.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 08:33:41.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 08:33:43.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:33:43.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:33:53.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:33:53.000 [notice] New control connection opened from 127.0.0.1.
...
...
Jul 13 08:45:47.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 08:45:47.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 08:45:56.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:45:56.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:46:06.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:46:06.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:46:14.000 [notice] No circuits are opened. Relaxed timeout for circuit 287 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. 0 guards are live. [139 similar message(s) suppressed in last 3600 seconds]
Jul 13 08:46:15.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 193/6967, and can only build 0% of likely paths. (We have 2% of guards bw, 2% of midpoint bw, and 2% of exit bw = 0% of path bw.)
**Jul 13 08:46:16.000 [notice] New control connection opened from 127.0.0.1.**
**Jul 13 08:46:16.000 [notice] New control connection opened from 127.0.0.1.**
**Jul 13 08:46:17.000 [notice] Bootstrapped 55%: Loading relay descriptors**
**Jul 13 08:46:17.000 [notice] Bootstrapped 63%: Loading relay descriptors**
**Jul 13 08:46:17.000 [notice] Bootstrapped 73%: Loading relay descriptors**
**Jul 13 08:46:17.000 [notice] Bootstrapped 80%: Connecting to the Tor network**
**Jul 13 08:46:18.000 [notice] Bootstrapped 90%: Establishing a Tor circuit**
**Jul 13 08:46:18.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.**
**Jul 13 08:46:18.000 [notice] Bootstrapped 100%: Done**
Jul 13 08:46:26.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:46:27.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:46:33.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:46:33.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:46:38.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:46:38.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 08:49:39.000 [notice] Your system clock just jumped 179 seconds forward; assuming established circuits no longer work.
Jul 13 08:49:40.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Jul 13 08:49:40.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Jul 13 10:28:25.000 [notice] No circuits are opened. Relaxed timeout for circuit 391 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. 75 guards are live. [2 similar message(s) suppressed in last 3600 seconds]
Jul 13 10:34:39.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:34:39.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:36:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
Jul 13 10:36:40.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:36:40.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:38:40.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
Jul 13 10:38:41.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:38:41.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:40:41.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 13 10:40:42.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:40:42.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:43:03.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:43:03.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:43:10.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 10:43:10.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 12:01:16.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 12:01:16.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 12:03:00.000 [notice] No circuits are opened. Relaxed timeout for circuit 456 (a General-purpose client 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. 65 guards are live. [31 similar message(s) suppressed in last 3600 seconds]
Jul 13 12:03:16.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
Jul 13 12:03:17.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 12:03:17.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 12:04:02.000 [notice] Tor has not observed any network activity for the past 72 seconds. Disabling circuit build timeout recording.
Jul 13 12:04:18.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 87 seconds during 1 circuit attempts.
Jul 13 12:05:17.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
Jul 13 12:05:18.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 12:05:18.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 12:06:23.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 12:06:23.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 12:06:27.000 [notice] New control connection opened from 127.0.0.1.
Jul 13 12:06:27.000 [notice] New control connection opened from 127.0.0.1.


Jul 13 15:34:23.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 15:34:24.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 15:34:24.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 15:34:57.000 [notice] Tor has not observed any network activity for the past 62 seconds. Disabling circuit build timeout recording.
Jul 13 15:34:58.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 63 seconds during 3 circuit attempts.
Jul 13 15:36:15.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:36:15.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:36:15.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:36:15.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:36:15.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:37:07.000 [notice] Tor has not observed any network activity for the past 62 seconds. Disabling circuit build timeout recording.
Jul 13 15:37:07.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 62 seconds during 1 circuit attempts.
Jul 13 15:38:10.000 [notice] Tor has not observed any network activity for the past 62 seconds. Disabling circuit build timeout recording.
Jul 13 15:38:10.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 62 seconds during 1 circuit attempts.
Jul 13 15:38:21.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:38:21.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:38:21.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:38:21.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:38:21.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:39:12.000 [notice] Tor has not observed any network activity for the past 62 seconds. Disabling circuit build timeout recording.
Jul 13 15:39:12.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 62 seconds during 1 circuit attempts.
Jul 13 15:40:14.000 [notice] Tor has not observed any network activity for the past 62 seconds. Disabling circuit build timeout recording.
Jul 13 15:40:15.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 63 seconds during 1 circuit attempts.
Jul 13 15:40:27.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:40:27.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:40:27.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:40:27.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:40:27.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:42:22.000 [notice] Tor has not observed any network activity for the past 63 seconds. Disabling circuit build timeout recording.
Jul 13 15:42:24.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 65 seconds during 1 circuit attempts.
Jul 13 15:42:35.000 [notice] Tried for 128 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:42:35.000 [notice] Tried for 128 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:42:35.000 [notice] Tried for 128 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:42:35.000 [notice] Tried for 128 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:42:35.000 [notice] Tried for 128 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:43:27.000 [notice] Tor has not observed any network activity for the past 62 seconds. Disabling circuit build timeout recording.
Jul 13 15:43:27.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 62 seconds during 1 circuit attempts.
Jul 13 15:44:29.000 [notice] Tor has not observed any network activity for the past 62 seconds. Disabling circuit build timeout recording.
Jul 13 15:44:29.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 62 seconds during 1 circuit attempts.
Jul 13 15:44:39.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:44:39.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:44:39.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:44:39.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:44:39.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:46:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 15:46:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 15:46:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 15:46:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 15:46:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 15:46:50.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 15:46:55.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 15:48:15.000 [notice] Tor has not observed any network activity for the past 63 seconds. Disabling circuit build timeout recording.
Jul 13 15:48:28.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 76 seconds during 10 circuit attempts.
Jul 13 15:48:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:48:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:48:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:48:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:48:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 15:49:30.000 [notice] Tor has not observed any network activity for the past 62 seconds. Disabling circuit build timeout recording.
Jul 13 15:49:30.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 62 seconds during 1 circuit attempts.
Jul 13 15:53:11.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $95DA61AEF23A6C851028C1AA88AD8593F659E60F~DigiGesTor2e2 at 176.10.104.243. Retrying on a new circuit.
Jul 13 15:53:11.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $95DA61AEF23A6C851028C1AA88AD8593F659E60F~DigiGesTor2e2 at 176.10.104.243. Retrying on a new circuit.
Jul 13 16:03:49.000 [notice] Tor has not observed any network activity for the past 63 seconds. Disabling circuit build timeout recording.
Jul 13 16:04:35.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 108 seconds during 42 circuit attempts.
Jul 13 16:04:36.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 13 16:05:53.000 [notice] Tor has not observed any network activity for the past 63 seconds. Disabling circuit build timeout recording.
Jul 13 16:05:54.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 64 seconds during 1 circuit attempts.
Jul 13 16:09:11.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 13 16:16:01.000 [notice] Tor has not observed any network activity for the past 72 seconds. Disabling circuit build timeout recording.
Jul 13 16:16:02.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 73 seconds during 1 circuit attempts.
Jul 13 16:27:03.000 [notice] Tor has not observed any network activity for the past 64 seconds. Disabling circuit build timeout recording.
Jul 13 16:28:06.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 127 seconds during 32 circuit attempts.
Jul 13 16:38:03.000 [notice] New control connection opened.
Jul 13 16:38:03.000 [notice] New control connection opened.
Jul 13 16:38:03.000 [notice] New control connection opened.
Jul 13 16:38:03.000 [notice] New control connection opened.
Jul 13 16:38:09.000 [notice] New control connection opened.
Jul 13 16:38:09.000 [notice] New control connection opened.
Jul 13 16:38:09.000 [notice] New control connection opened.
Jul 13 16:38:09.000 [notice] New control connection opened.
Jul 13 16:38:14.000 [notice] New control connection opened.
Jul 13 16:38:14.000 [notice] New control connection opened.
Jul 13 16:38:14.000 [notice] New control connection opened.
Jul 13 16:38:14.000 [notice] New control connection opened.
Jul 13 16:42:06.000 [warn] Socks version 71 not recognized. (Tor is not an http proxy.)
Jul 13 16:42:06.000 [notice] New control connection opened.
Jul 13 16:42:06.000 [notice] New control connection opened.
Jul 13 16:42:06.000 [notice] New control connection opened.
Jul 13 16:42:06.000 [notice] New control connection opened.
Jul 13 16:44:05.000 [notice] Tor has not observed any network activity for the past 63 seconds. Disabling circuit build timeout recording.
Jul 13 16:44:11.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 13 16:44:25.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 83 seconds during 18 circuit attempts.
Jul 13 16:44:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:44:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:44:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:44:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:44:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:45:27.000 [notice] Tor has not observed any network activity for the past 62 seconds. Disabling circuit build timeout recording.
Jul 13 16:45:28.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 63 seconds during 1 circuit attempts.
Jul 13 16:46:12.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 13 16:46:50.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:46:55.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:46:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:46:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:46:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:46:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:46:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:48:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:48:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:48:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:48:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:48:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:49:27.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 13 16:50:51.000 [notice] Tor has not observed any network activity for the past 72 seconds. Disabling circuit build timeout recording.
Jul 13 16:50:52.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 73 seconds during 1 circuit attempts.
Jul 13 16:50:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:50:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:50:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:50:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:50:57.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jul 13 16:52:28.000 [notice] Tor has not observed any network activity for the past 64 seconds. Disabling circuit build timeout recording.
Jul 13 16:52:54.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 90 seconds during 15 circuit attempts.
Jul 13 16:53:05.000 [notice] Tried for 128 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 16:53:05.000 [notice] Tried for 128 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 16:53:05.000 [notice] Tried for 128 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 16:53:05.000 [notice] Tried for 128 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 16:53:05.000 [notice] Tried for 128 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 16:54:19.000 [warn] Socks version 71 not recognized. (Tor is not an http proxy.)
Jul 13 16:54:19.000 [notice] New control connection opened.
Jul 13 16:54:19.000 [notice] New control connection opened.
Jul 13 16:54:19.000 [notice] New control connection opened.
Jul 13 16:54:19.000 [notice] New control connection opened.
Jul 13 16:55:09.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 16:55:09.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 16:55:09.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 16:55:09.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up.
Jul 13 16:55:09.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up.

user@host:~$ !61
sudo systemctl --failed list-units
  UNIT                       LOAD   ACTIVE SUB    DESCRIPTION
● apparmor.service           loaded failed failed LSB: AppArmor initialization
● qubes-update-check.service loaded failed failed Qubes check for VM updates and notify dom0

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
user@host:~$ !62
sudo service qubes-whonix-postinit status
● qubes-whonix-postinit.service - Qubes-Whonix post init
   Loaded: loaded (/lib/systemd/system/qubes-whonix-postinit.service; enabled)
   Active: active (exited) since Wed 2016-07-13 07:44:39 UTC; 5h 54min ago
  Process: 484 ExecStart=/usr/lib/qubes-whonix/init/qubes-whonix-postinit (code=exited, status=0/SUCCESS)
 Main PID: 484 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/qubes-whonix-postinit.service

Jul 13 07:44:38 host qubes-whonix-postinit[484]: + '[' -d /rw/srv/whonix/etc/tor ']'
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + sync
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + mount --bind /rw/srv/whonix/etc/tor /etc/tor
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + sync
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + exit 0
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + /usr/lib/qubes-whonix/replace-ips
Jul 13 07:44:39 host qubes-whonix-postinit[484]: + '[' -e /var/run/qubes-service/whonix-gateway ']'
Jul 13 07:44:39 host qubes-whonix-postinit[484]: + '[' -e /var/run/qubes-service/whonix-tor-enable ']'
Jul 13 07:44:39 host qubes-whonix-postinit[484]: + '[' -e /var/run/qubes-service/whonix-tor-disable ']'
Jul 13 07:44:39 host systemd[1]: Started Qubes-Whonix post init.

user@host:~$ !63
sudo journalctl -u qubes-whonix-postinit | cat
-- Logs begin at Wed 2016-07-13 07:47:28 UTC, end at Wed 2016-07-13 13:39:05 UTC. --
Jul 13 07:44:36 host systemd[1]: Starting Qubes-Whonix post init...
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + '[' -e /var/run/qubes-service/whonix-gateway ']'
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + /usr/lib/qubes-whonix/bind-directories
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + '[' -e /var/run/qubes-service/whonix-gateway ']'
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + BINDS=('/rw/srv/whonix/var/lib/tor:/var/lib/tor' '/rw/srv/whonix/var/lib/whonix:/var/lib/whonix' '/rw/srv/whonix/var/lib/whonixcheck:/var/lib/whonixcheck' '/rw/srv/whonix/var/cache/whonix-setup-wizard:/var/cache/whonix-setup-wizard' '/rw/srv/qubes-whonix/var/cache/qubes-whonix:/var/cache/qubes-whonix' '/rw/srv/whonix/etc/tor:/etc/tor')
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + for bind in '${BINDS[@]}'
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + rw_dir=/rw/srv/whonix/var/lib/tor
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + ro_dir=/var/lib/tor
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + umount /var/lib/tor
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + true
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + '[' -n '' ']'
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + '[' -d /var/lib/tor ']'
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + '[' -d /rw/srv/whonix/var/lib/tor ']'
Jul 13 07:44:36 host qubes-whonix-postinit[484]: + sync
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + mount --bind /rw/srv/whonix/var/lib/tor /var/lib/tor
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + for bind in '${BINDS[@]}'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + rw_dir=/rw/srv/whonix/var/lib/whonix
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + ro_dir=/var/lib/whonix
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + umount /var/lib/whonix
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + true
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + '[' -n '' ']'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + '[' -d /var/lib/whonix ']'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + '[' -d /rw/srv/whonix/var/lib/whonix ']'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + sync
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + mount --bind /rw/srv/whonix/var/lib/whonix /var/lib/whonix
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + for bind in '${BINDS[@]}'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + rw_dir=/rw/srv/whonix/var/lib/whonixcheck
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + ro_dir=/var/lib/whonixcheck
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + umount /var/lib/whonixcheck
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + true
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + '[' -n '' ']'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + '[' -d /var/lib/whonixcheck ']'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + '[' -d /rw/srv/whonix/var/lib/whonixcheck ']'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + sync
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + mount --bind /rw/srv/whonix/var/lib/whonixcheck /var/lib/whonixcheck
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + for bind in '${BINDS[@]}'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + rw_dir=/rw/srv/whonix/var/cache/whonix-setup-wizard
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + ro_dir=/var/cache/whonix-setup-wizard
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + umount /var/cache/whonix-setup-wizard
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + true
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + '[' -n '' ']'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + '[' -d /var/cache/whonix-setup-wizard ']'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + '[' -d /rw/srv/whonix/var/cache/whonix-setup-wizard ']'
Jul 13 07:44:37 host qubes-whonix-postinit[484]: + sync
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + mount --bind /rw/srv/whonix/var/cache/whonix-setup-wizard /var/cache/whonix-setup-wizard
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + for bind in '${BINDS[@]}'
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + rw_dir=/rw/srv/qubes-whonix/var/cache/qubes-whonix
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + ro_dir=/var/cache/qubes-whonix
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + umount /var/cache/qubes-whonix
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + true
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + '[' -n '' ']'
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + '[' -d /var/cache/qubes-whonix ']'
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + mkdir -p /var/cache/qubes-whonix
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + '[' -d /rw/srv/qubes-whonix/var/cache/qubes-whonix ']'
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + sync
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + mount --bind /rw/srv/qubes-whonix/var/cache/qubes-whonix /var/cache/qubes-whonix
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + for bind in '${BINDS[@]}'
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + rw_dir=/rw/srv/whonix/etc/tor
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + ro_dir=/etc/tor
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + umount /etc/tor
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + true
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + '[' -n '' ']'
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + '[' -d /etc/tor ']'
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + '[' -d /rw/srv/whonix/etc/tor ']'
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + sync
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + mount --bind /rw/srv/whonix/etc/tor /etc/tor
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + sync
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + exit 0
Jul 13 07:44:38 host qubes-whonix-postinit[484]: + /usr/lib/qubes-whonix/replace-ips
Jul 13 07:44:39 host qubes-whonix-postinit[484]: + '[' -e /var/run/qubes-service/whonix-gateway ']'
Jul 13 07:44:39 host qubes-whonix-postinit[484]: + '[' -e /var/run/qubes-service/whonix-tor-enable ']'
Jul 13 07:44:39 host qubes-whonix-postinit[484]: + '[' -e /var/run/qubes-service/whonix-tor-disable ']'
Jul 13 07:44:39 host systemd[1]: Started Qubes-Whonix post init.

user@host:~$ !64
cat /var/cache/qubes-whonix/whonix-ip-gateway 
10.137.3.1user@host:~$ !65
cat /var/cache/qubes-whonix/whonix-ip-local
cat: /var/cache/qubes-whonix/whonix-ip-local: No such file or directory

user@host:~$ !66
sudo ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:16:3e:5e:6c:08  
          inet addr:10.137.2.10  Bcast:10.255.255.255  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18340 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12051 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:20264405 (19.3 MiB)  TX bytes:6233008 (5.9 MiB)

eth1      Link encap:Ethernet  HWaddr 92:fe:71:49:7f:c3  
          inet addr:10.137.3.1  Bcast:10.255.255.255  Mask:255.255.255.255
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:22850 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22850 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:11202785 (10.6 MiB)  TX bytes:11202785 (10.6 MiB)

user@host:~$ !67
sudo route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         10.137.2.1      0.0.0.0         UG    0      0        0 eth0
10.137.2.1      *               255.255.255.255 UH    0      0        0 eth0

user@host:~$ !68
qubesdb-multiread 
Usage: qubesdb-multiread [-frq] [-c <command>] [-d <destination domain>] 
       [command arguments]
  -f - print full path (affects reading commands)
  -r - print raw value (affects reading commands)
  -q - quiet - do not print error
  -c <command> - specify command
  -d <domain> - specify destination domain, available only in dom0

Available commands:
  read path [path...] - read value(s)
  write path value [path value...] - write value(s)
  rm path [path...] - remove value(s)
  multiread path [path...] - read all entries matching given path
  list path - list paths mathing given argument
  watch [-n N] path [path...] - watch given path(s) for modifications
    if -n given you can specify how many events should be received before terminating

user@host:~$ !69
sudo /usr/lib/qubes-whonix/replace-ips

user@host:~$ !70
cat /usr/share/tor/tor-service-defaults-torrc | grep -i TransPort
## TransPort is not used for anything preinstalled by default.
TransPort 10.137.3.1:9040
## TransPort and DnsPort are no longer used on Gateway by default.
##TransPort 127.0.0.1:9041

claudi8b6 · July 13, 2016, 5:26pm

Output from the GW template:

er@host:~$ sudo apt-get update
Ign http://security.debian.org jessie/updates InRelease                        
Ign http://deb.torproject.org jessie InRelease                                 
Ign http://ftp.us.debian.org jessie InRelease                                  
Ign http://deb.qubes-os.org jessie InRelease                                   
Ign http://mirror.whonix.de jessie InRelease                                   
Ign http://security.debian.org jessie/updates Release.gpg                      
Ign http://deb.torproject.org jessie Release.gpg                               
Ign http://ftp.us.debian.org jessie Release.gpg                                
Ign http://deb.qubes-os.org jessie Release.gpg                                 
Ign http://mirror.whonix.de jessie Release.gpg                                 
Ign http://deb.torproject.org jessie Release                                   
Ign http://security.debian.org jessie/updates Release                          
Ign http://ftp.us.debian.org jessie Release                                    
Ign http://deb.qubes-os.org jessie Release                                     
Ign http://mirror.whonix.de jessie Release                                     
Err http://deb.torproject.org jessie/main amd64 Packages                       
  500  Unable to connect
Err http://deb.qubes-os.org jessie/main amd64 Packages                         
  500  Unable to connect
Err http://mirror.whonix.de jessie/main amd64 Packages                         
  500  Unable to connect
Ign http://deb.torproject.org jessie/main Translation-en_US                    
Ign http://deb.qubes-os.org jessie/main Translation-en_US                      
Ign http://mirror.whonix.de jessie/main Translation-en_US                      
Ign http://deb.torproject.org jessie/main Translation-en                       
Ign http://deb.qubes-os.org jessie/main Translation-en                         
Ign http://mirror.whonix.de jessie/main Translation-en                         
Err http://security.debian.org jessie/updates/main amd64 Packages    
  500  Unable to connect
Err http://ftp.us.debian.org jessie/main amd64 Packages
  500  Unable to connect
Err http://security.debian.org jessie/updates/contrib amd64 Packages
  500  Unable to connect
Err http://ftp.us.debian.org jessie/contrib amd64 Packages
  500  Unable to connect
Err http://security.debian.org jessie/updates/non-free amd64 Packages
  500  Unable to connect
Err http://ftp.us.debian.org jessie/non-free amd64 Packages
  500  Unable to connect
Ign http://security.debian.org jessie/updates/contrib Translation-en_US
Ign http://ftp.us.debian.org jessie/contrib Translation-en_US
Ign http://security.debian.org jessie/updates/contrib Translation-en
Ign http://ftp.us.debian.org jessie/contrib Translation-en
Ign http://security.debian.org jessie/updates/main Translation-en_US
Ign http://ftp.us.debian.org jessie/main Translation-en_US
Ign http://security.debian.org jessie/updates/main Translation-en
Ign http://ftp.us.debian.org jessie/main Translation-en
Ign http://security.debian.org jessie/updates/non-free Translation-en_US
Ign http://ftp.us.debian.org jessie/non-free Translation-en_US
Ign http://security.debian.org jessie/updates/non-free Translation-en
Ign http://ftp.us.debian.org jessie/non-free Translation-en
W: Failed to fetch http://deb.torproject.org/torproject.org/dists/jessie/main/binary-amd64/Packages  500  Unable to connect

W: Failed to fetch http://security.debian.org/dists/jessie/updates/main/binary-amd64/Packages  500  Unable to connect

W: Failed to fetch http://security.debian.org/dists/jessie/updates/contrib/binary-amd64/Packages  500  Unable to connect

W: Failed to fetch http://security.debian.org/dists/jessie/updates/non-free/binary-amd64/Packages  500  Unable to connect

W: Failed to fetch http://ftp.us.debian.org/debian/dists/jessie/main/binary-amd64/Packages  500  Unable to connect

W: Failed to fetch http://ftp.us.debian.org/debian/dists/jessie/contrib/binary-amd64/Packages  500  Unable to connect

W: Failed to fetch http://ftp.us.debian.org/debian/dists/jessie/non-free/binary-amd64/Packages  500  Unable to connect

W: Failed to fetch http://deb.qubes-os.org/r3.1/vm/dists/jessie/main/binary-amd64/Packages  500  Unable to connect

W: Failed to fetch http://mirror.whonix.de/whonixdevelopermetafiles/internal/dists/jessie/main/binary-amd64/Packages  500  Unable to connect

E: Some index files failed to download. They have been ignored, or old ones used instead.

Output from the Workstation:



user@host:~$  whonixcheck 
[INFO] [whonixcheck] anon-whonix | Whonix-Workstation | whonix-ws Template-Based AppVM | Wed Jul 13 16:53:41 UTC 2016
[INFO] [whonixcheck] Connected to Tor.
[INFO] [whonixcheck] SocksPort Test: Testing Tor's SocksPort...
[ERROR] [whonixcheck] SocksPort Test Result: https://check.torproject.org was not reachable.
You could check, if you can reach https://check.torproject.org via the Tor Browser Bundle.
(curl exit code: [7] - [Failed to connect to host.])
[ERROR] [whonixcheck] TransPort Test: Not checking Tor's TransPort, because SocksPort test failed already.
[ERROR] [whonixcheck] Stream Isolation Test: Skipped, because SocksPort test failed! Can not test stream isolation.
[INFO] [whonixcheck] Whonix News Download: Checking for Whonix news and updates...
[ERROR] [whonixcheck] Whonix News Result: Download of Whonix News File failed.
[INFO] [whonixcheck] Debian Package Update Check: Checking for software updates via apt-get... ( Documentation: https://www.whonix.org/wiki/Update )
[WARNING] [whonixcheck] Debian Package Update Check Result: Could not check for software updates! (apt-get code: 100)
Please manually check inside your 'whonix-ws' TemplateVM.
1. Open a TemplateVM terminal. (dom0 -> Start Menu -> Template: whonix-ws -> Terminal)
2. Update. sudo apt-get update && sudo apt-get dist-upgrade
3. Shutdown your TemplateVM. (dom0 -> Qubes VM Manager -> right click 'whonix-ws' -> Shutdown VM)
4. Shutdown and restart this Template-Based AppVM. (dom0 -> Qubes VM Manager -> right click 'anon-whonix' -> Shutdown VM)
[INFO] [whonixcheck] Whonix APT Repository: Enabled.
When the Whonix team releases JESSIE updates,
they will be AUTOMATICALLY installed (when you run apt-get dist-upgrade)
along with updated packages from the Debian team. Please
read https://www.whonix.org/wiki/Trust to understand the risk.
If you want to change this, use:
    sudo whonix_repository

entr0py · July 13, 2016, 8:19pm

Confirmed:

neither tor.service nor tor@default.service runs in gw-template
/var/run/tor/ is not created in gw-template
/var/run/tor/log in sys-whonix has correct ip address

That’s really odd… after an hour… I was going to suggest that you might have misconfigured Qubes firewalls but the fact that it connected kinda kills that theory.

The schizophrenic log looks like what would happen if there were conflicting IP addresses on the network, but I don’t think that’s possible with Qubes. What’s left? Unpredictable WAN? Bad hardware / drivers? Did you try your 2nd NIC?

claudi8b6 · July 13, 2016, 8:36pm

[quote=“entr0py, post:38, topic:2662”]
What’s left? Unpredictable WAN?
[/quote]Tor works fine on other platforms I tried.

As I wrote above, I installed Qubes 3.1 on a completely different pc and it didn’t connect.

I’m getting many notices on Arm: we tried for X seconds to connect to [scrubbed] using exit ------ … No circuits are opened… Tor has not observed any network activity for the past 63 seconds…

entr0py · July 13, 2016, 8:47pm

These messages are not necessarily indicative of a malfunctioning gateway.

I’m just grasping at straws now… If you want to try something, try skipping sys-firewall and connect sys-whonix to sys-net directly. The Fedora template operates differently from Whonix-Gateway template in the way it interacts with Qubes firewall.

Patrick · July 13, 2016, 9:31pm

→

qubesdb-multiread /

(But not required at the moment.)

Dunno why that failed, but we are no longer using that since Whonix 13 anymore.

Dunno why that failed (should still work), but we are not using mirror.whonix.de in Whonix 13 anymore.

(Note to myself.) In conclusion you are still on Whonix 12, not Whonix 13. Which is to be expected, since Qubes R3.1 came with Whonix 12 on Qubes installer iso and I don’t think it has been updated in meanwhile. ( Redirecting to Google Groups )

To not bother with Whonix 12 already fixed issues and upgrading to Whonix 13, it may be best to reinstall Whonix from Qubes repository. See the following instructions.

How to Reinstall a TemplateVM