But no connection is encrypt with tor.
Thats my configs. Whats wrong? Can you help me please?
Tor Plugin not work
Moderator: Moderators
Tor Plugin not work
Hey guys, I have installed the tor plugin
But no connection is encrypt with tor.
Thats my configs. Whats wrong? Can you help me please?
But no connection is encrypt with tor.
Thats my configs. Whats wrong? Can you help me please?
Re: Tor Plugin not work
I have the same problem. Until February I used gargoyle ver 1.5.10 on my TP-Link TL-WR1043N/ND v1 and it worked very good. The last days of February Tor didn't work. I changed the gargoyle version using the 1.6.0 and still today Tor doesn't work. Is there anybody can help us? Please
- tor configuration
- tor.jpg (180.06 KiB) Viewed 8316 times
Re: Tor Plugin not work
munez: It will not work if you're connected via a client bridge. You have to use the router in gateway mode to use Tor.
evolisat: Since you said it worked in 1.5.10, I'm assuming you're not in repeater mode. By any chance did you attempt to preserve settings when upgrading from 1.5.10? The Tor configuration files changed a bit since then so if this is the case, try doing a fresh install. If that doesn't work, post again here and I'll try to help you figure out what is wrong.
evolisat: Since you said it worked in 1.5.10, I'm assuming you're not in repeater mode. By any chance did you attempt to preserve settings when upgrading from 1.5.10? The Tor configuration files changed a bit since then so if this is the case, try doing a fresh install. If that doesn't work, post again here and I'll try to help you figure out what is wrong.
Re: Tor Plugin not work
I use my router in Gateway mode not like repeater. So I attached my configuration. I don't have my first configuration, I lost it. Please help me
Another question. Do you know if when I'm using my router with tor someone can use my ip address? Is it safe?
Thank you
Another question. Do you know if when I'm using my router with tor someone can use my ip address? Is it safe?
Thank you
- Attachments
-
- gargoyle1.jpg (192.03 KiB) Viewed 8305 times
-
- gargoyle.jpg (242.17 KiB) Viewed 8305 times
Re: Tor Plugin not work
evolisat: You misunderstand what I meant. When you installed 1.6.0 did you check the box in the upgrade form that says 'Attempt to preserve settings' ? If so, that is likely the source of your issues. Try installing 1.6.0 again, and not checking that box.
Re: Tor Plugin not work
No when I have installed the gargoyle version 1.6.0 I have not checked the box to preserve the settings
Re: Tor Plugin not work
Ok, if that isn't the problem, I'm going to need more information.
(1) You currently have selected hidden service access only. What hidden service address are you testing with? I just want to verify that the address isn't the problem (these come and go regularly). Can you please verify that you cannot connect to Tor Search, http://kbhpodhnfxl3clb4.onion/, which I just verified was up?
(2) If you're still having problems, please ssh into the router (if you're using windows, use PuTTY), and run "logread", and post the output here, and I'll try to help you figure out what might be going wrong.
(1) You currently have selected hidden service access only. What hidden service address are you testing with? I just want to verify that the address isn't the problem (these come and go regularly). Can you please verify that you cannot connect to Tor Search, http://kbhpodhnfxl3clb4.onion/, which I just verified was up?
(2) If you're still having problems, please ssh into the router (if you're using windows, use PuTTY), and run "logread", and post the output here, and I'll try to help you figure out what might be going wrong.
Re: Tor Plugin not work
I'm testing my tor connection with the address http://kbhpodhnfxl3clb4.onion/ but it dosn't work. My router doesn't connect via Tor. Now I'm using PuTTY but I have another problem when I put inside this program the router's ip address It ask me login as: what can i write in it? I use admin, administrator, gargoyle but it doesn't work
Re: Tor Plugin not work
ok I solved. I connected using root as user. And when I run logread the output is this:
.3.134 00:23
b8:d4:1a server
Mar 23 11:02:38 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPINFORM(br-lan) 192.168.3.134 00:23b8:d4:1a
Mar 23 11:02:38 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPACK(br-lan) 192.168.3.134 00:23b8:d4:1a server
Mar 23 11:03:07 Gargoyle daemon.notice Tor[2669]: Catching signal TERM, exiting cleanly.
Mar 23 11:03:07 Gargoyle daemon.notice Tor[2669]: Catching signal TERM, exiting cleanly.
Mar 23 11:03:20 Gargoyle daemon.warn Tor[8230]: You are running Tor as root. You don't need to, and you probably shouldn't.
Mar 23 11:03:20 Gargoyle daemon.warn Tor[8230]: You are running Tor as root. You don't need to, and you probably shouldn't.
Mar 23 11:03:29 Gargoyle daemon.notice Tor[8230]: Bootstrapped 45%: Asking for relay descriptors.
Mar 23 11:03:29 Gargoyle daemon.notice Tor[8230]: Bootstrapped 45%: Asking for relay descriptors.
Mar 23 11:03:30 Gargoyle daemon.notice Tor[8230]: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Mar 23 11:03:30 Gargoyle daemon.notice Tor[8230]: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Mar 23 11:03:30 Gargoyle daemon.notice Tor[8230]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Mar 23 11:03:30 Gargoyle daemon.notice Tor[8230]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Mar 23 11:03:32 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:32 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:36 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:36 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:38 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:38 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:40 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:40 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:43 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:43 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:54 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:54 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:04:03 Gargoyle daemon.info hostapd: wlan0: STA 00:23b8:d4:1a WPA: group key handshake completed (RSN)
Mar 23 11:04:03 Gargoyle daemon.info hostapd: wlan0: STA d0:22:be:51:e1:70 WPA: group key handshake completed (RSN)
Mar 23 11:04:12 Gargoyle daemon.notice Tor[8230]: We now have enough directory information to build circuits.
Mar 23 11:04:12 Gargoyle daemon.notice Tor[8230]: We now have enough directory information to build circuits.
Mar 23 11:04:12 Gargoyle daemon.notice Tor[8230]: Bootstrapped 80%: Connecting to the Tor network.
Mar 23 11:04:12 Gargoyle daemon.notice Tor[8230]: Bootstrapped 80%: Connecting to the Tor network.
Mar 23 11:04:14 Gargoyle daemon.notice Tor[8230]: Bootstrapped 90%: Establishing a Tor circuit.
Mar 23 11:04:14 Gargoyle daemon.notice Tor[8230]: Bootstrapped 90%: Establishing a Tor circuit.
Mar 23 11:04:14 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:04:14 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:04:22 Gargoyle daemon.notice Tor[8230]: Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 23 11:04:22 Gargoyle daemon.notice Tor[8230]: Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 23 11:04:22 Gargoyle daemon.notice Tor[8230]: Bootstrapped 100%: Done.
Mar 23 11:04:22 Gargoyle daemon.notice Tor[8230]: Bootstrapped 100%: Done.
Mar 23 11:04:23 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:04:23 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:05:17 Gargoyle daemon.notice Tor[8230]: Catching signal TERM, exiting cleanly.
Mar 23 11:05:17 Gargoyle daemon.notice Tor[8230]: Catching signal TERM, exiting cleanly.
Mar 23 11:05:34 Gargoyle daemon.warn Tor[8811]: You are running Tor as root. You don't need to, and you probably shouldn't.
Mar 23 11:05:34 Gargoyle daemon.warn Tor[8811]: You are running Tor as root. You don't need to, and you probably shouldn't.
Mar 23 11:05:57 Gargoyle daemon.notice Tor[8811]: We now have enough directory information to build circuits.
Mar 23 11:05:57 Gargoyle daemon.notice Tor[8811]: We now have enough directory information to build circuits.
Mar 23 11:05:57 Gargoyle daemon.notice Tor[8811]: Bootstrapped 80%: Connecting to the Tor network.
Mar 23 11:05:57 Gargoyle daemon.notice Tor[8811]: Bootstrapped 80%: Connecting to the Tor network.
Mar 23 11:05:58 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:05:58 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:05 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:05 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:06 Gargoyle daemon.notice Tor[8811]: Bootstrapped 85%: Finishing handshake with first hop.
Mar 23 11:06:06 Gargoyle daemon.notice Tor[8811]: Bootstrapped 85%: Finishing handshake with first hop.
Mar 23 11:06:07 Gargoyle daemon.notice Tor[8811]: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Mar 23 11:06:07 Gargoyle daemon.notice Tor[8811]: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Mar 23 11:06:07 Gargoyle daemon.notice Tor[8811]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Mar 23 11:06:07 Gargoyle daemon.notice Tor[8811]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Mar 23 11:06:18 Gargoyle daemon.notice Tor[8811]: Bootstrapped 90%: Establishing a Tor circuit.
Mar 23 11:06:18 Gargoyle daemon.notice Tor[8811]: Bootstrapped 90%: Establishing a Tor circuit.
Mar 23 11:06:18 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:18 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:25 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:25 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:31 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:31 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:37 Gargoyle daemon.notice Tor[8811]: Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 23 11:06:37 Gargoyle daemon.notice Tor[8811]: Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 23 11:06:37 Gargoyle daemon.notice Tor[8811]: Bootstrapped 100%: Done.
Mar 23 11:06:37 Gargoyle daemon.notice Tor[8811]: Bootstrapped 100%: Done.
Mar 23 11:06:38 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:38 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:07:18 Gargoyle authpriv.info dropbear[9239]: Child connection from 192.168.3.134:63255
Mar 23 11:07:30 Gargoyle authpriv.warn dropbear[9239]: Login attempt for nonexistent user from 192.168.3.134:63255
Mar 23 11:07:34 Gargoyle authpriv.warn dropbear[9239]: Login attempt for nonexistent user from 192.168.3.134:63255
Mar 23 11:07:39 Gargoyle authpriv.warn dropbear[9239]: Login attempt for nonexistent user from 192.168.3.134:63255
Mar 23 11:07:42 Gargoyle authpriv.warn dropbear[9239]: Login attempt for nonexistent user from 192.168.3.134:63255
Mar 23 11:08:27 Gargoyle authpriv.info dropbear[9239]: Exit before auth: Exited normally
Mar 23 11:08:54 Gargoyle authpriv.info dropbear[13630]: Child connection from 192.168.3.134:63295
Mar 23 11:09:21 Gargoyle authpriv.warn dropbear[13630]: Login attempt for nonexistent user from 192.168.3.134:63295
Mar 23 11:09:29 Gargoyle authpriv.warn dropbear[13630]: Login attempt for nonexistent user from 192.168.3.134:63295
Mar 23 11:09:37 Gargoyle authpriv.info dropbear[13630]: Exit before auth: Exited normally
Mar 23 11:09:48 Gargoyle daemon.notice httpd_gargoyle[1810]: exiting due to signal 15
Mar 23 11:09:48 Gargoyle daemon.notice httpd_gargoyle[11264]: exiting due to signal 15
Mar 23 11:09:48 Gargoyle daemon.warn httpd_gargoyle[15705]: started as root without requesting chroot(), warning only
Mar 23 11:09:48 Gargoyle daemon.notice httpd_gargoyle[15705]: httpd_gargoyle/1.0 14mar2008 starting on Gargoyle, port 80
Mar 23 11:10:58 Gargoyle authpriv.info dropbear[15980]: Child connection from 192.168.3.134:63406
Mar 23 11:11:06 Gargoyle authpriv.warn dropbear[15980]: Login attempt for nonexistent user from 192.168.3.134:63406
Mar 23 11:11:10 Gargoyle authpriv.warn dropbear[15980]: Login attempt for nonexistent user from 192.168.3.134:63406
Mar 23 11:11:23 Gargoyle authpriv.warn dropbear[15980]: Login attempt for nonexistent user from 192.168.3.134:63406
Mar 23 11:11:26 Gargoyle authpriv.info dropbear[15980]: Exit before auth: Exited normally
Mar 23 11:11:48 Gargoyle authpriv.info dropbear[16001]: Child connection from 192.168.3.134:63410
Mar 23 11:12:01 Gargoyle authpriv.warn dropbear[16001]: Login attempt for nonexistent user from 192.168.3.134:63410
Mar 23 11:12:04 Gargoyle authpriv.warn dropbear[16001]: Login attempt for nonexistent user from 192.168.3.134:63410
Mar 23 11:12:18 Gargoyle authpriv.info dropbear[16001]: Exit before auth: Exited normally
Mar 23 11:12:40 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPINFORM(br-lan) 192.168.3.134 00:23b8:d4:1a
Mar 23 11:12:40 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPACK(br-lan) 192.168.3.134 00:23b8:d4:1a server
Mar 23 11:12:58 Gargoyle authpriv.info dropbear[16069]: Child connection from 192.168.3.134:63435
Mar 23 11:13:14 Gargoyle authpriv.warn dropbear[16069]: Login attempt for nonexistent user from 192.168.3.134:63435
Mar 23 11:13:18 Gargoyle authpriv.warn dropbear[16069]: Login attempt for nonexistent user from 192.168.3.134:63435
Mar 23 11:13:40 Gargoyle authpriv.info dropbear[16069]: Exit before auth: Exited normally
Mar 23 11:14:03 Gargoyle daemon.info hostapd: wlan0: STA 00:23b8:d4:1a WPA: group key handshake completed (RSN)
Mar 23 11:14:03 Gargoyle daemon.info hostapd: wlan0: STA d0:22:be:51:e1:70 WPA: group key handshake completed (RSN)
Mar 23 11:15:35 Gargoyle authpriv.info dropbear[16187]: Child connection from 192.168.3.134:63459
Mar 23 11:15:41 Gargoyle authpriv.warn dropbear[16187]: Login attempt for nonexistent user from 192.168.3.134:63459
Mar 23 11:15:46 Gargoyle authpriv.warn dropbear[16187]: Login attempt for nonexistent user from 192.168.3.134:63459
Mar 23 11:15:51 Gargoyle authpriv.warn dropbear[16187]: Login attempt for nonexistent user from 192.168.3.134:63459
Mar 23 11:15:55 Gargoyle authpriv.warn dropbear[16187]: Login attempt for nonexistent user from 192.168.3.134:63459
Mar 23 11:16:04 Gargoyle authpriv.info dropbear[16187]: Exit before auth: Exited normally
Mar 23 11:19:40 Gargoyle authpriv.info dropbear[16256]: Child connection from 192.168.3.134:63488
Mar 23 11:21:44 Gargoyle authpriv.warn dropbear[16256]: Login attempt for nonexistent user from 192.168.3.134:63488
Mar 23 11:21:47 Gargoyle authpriv.warn dropbear[16256]: Login attempt for nonexistent user from 192.168.3.134:63488
Mar 23 11:21:50 Gargoyle authpriv.warn dropbear[16256]: Login attempt for nonexistent user from 192.168.3.134:63488
Mar 23 11:21:55 Gargoyle authpriv.info dropbear[16256]: Exit before auth: Exited normally
Mar 23 11:22:42 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPINFORM(br-lan) 192.168.3.134 00:23b8:d4:1a
Mar 23 11:22:42 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPACK(br-lan) 192.168.3.134 00:23b8:d4:1a server
Mar 23 11:24:02 Gargoyle authpriv.info dropbear[16343]: Child connection from 192.168.3.134:63544
Mar 23 11:24:03 Gargoyle daemon.info hostapd: wlan0: STA 00:23b8:d4:1a WPA: group key handshake completed (RSN)
Mar 23 11:24:03 Gargoyle daemon.info hostapd: wlan0: STA d0:22:be:51:e1:70 WPA: group key handshake completed (RSN)
Mar 23 11:24:10 Gargoyle authpriv.notice dropbear[16343]: Password auth succeeded for 'root' from 192.168.3.134:63544
Mar 23 11:25:36 Gargoyle authpriv.info dropbear[16343]: Exit (root): Exited normally
Mar 23 11:25:45 Gargoyle authpriv.info dropbear[16370]: Child connection from 192.168.3.134:63559
Mar 23 11:25:52 Gargoyle authpriv.notice dropbear[16370]: Password auth succeeded for 'root' from 192.168.3.134:63559
root@Gargoyle:~#
.3.134 00:23
b8:d4:1a serverMar 23 11:02:38 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPINFORM(br-lan) 192.168.3.134 00:23
b8:d4:1aMar 23 11:02:38 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPACK(br-lan) 192.168.3.134 00:23
b8:d4:1a serverMar 23 11:03:07 Gargoyle daemon.notice Tor[2669]: Catching signal TERM, exiting cleanly.
Mar 23 11:03:07 Gargoyle daemon.notice Tor[2669]: Catching signal TERM, exiting cleanly.
Mar 23 11:03:20 Gargoyle daemon.warn Tor[8230]: You are running Tor as root. You don't need to, and you probably shouldn't.
Mar 23 11:03:20 Gargoyle daemon.warn Tor[8230]: You are running Tor as root. You don't need to, and you probably shouldn't.
Mar 23 11:03:29 Gargoyle daemon.notice Tor[8230]: Bootstrapped 45%: Asking for relay descriptors.
Mar 23 11:03:29 Gargoyle daemon.notice Tor[8230]: Bootstrapped 45%: Asking for relay descriptors.
Mar 23 11:03:30 Gargoyle daemon.notice Tor[8230]: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Mar 23 11:03:30 Gargoyle daemon.notice Tor[8230]: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Mar 23 11:03:30 Gargoyle daemon.notice Tor[8230]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Mar 23 11:03:30 Gargoyle daemon.notice Tor[8230]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Mar 23 11:03:32 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:32 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:36 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:36 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:38 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:38 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:40 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:40 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:43 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:43 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:54 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:03:54 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:04:03 Gargoyle daemon.info hostapd: wlan0: STA 00:23
b8:d4:1a WPA: group key handshake completed (RSN)Mar 23 11:04:03 Gargoyle daemon.info hostapd: wlan0: STA d0:22:be:51:e1:70 WPA: group key handshake completed (RSN)
Mar 23 11:04:12 Gargoyle daemon.notice Tor[8230]: We now have enough directory information to build circuits.
Mar 23 11:04:12 Gargoyle daemon.notice Tor[8230]: We now have enough directory information to build circuits.
Mar 23 11:04:12 Gargoyle daemon.notice Tor[8230]: Bootstrapped 80%: Connecting to the Tor network.
Mar 23 11:04:12 Gargoyle daemon.notice Tor[8230]: Bootstrapped 80%: Connecting to the Tor network.
Mar 23 11:04:14 Gargoyle daemon.notice Tor[8230]: Bootstrapped 90%: Establishing a Tor circuit.
Mar 23 11:04:14 Gargoyle daemon.notice Tor[8230]: Bootstrapped 90%: Establishing a Tor circuit.
Mar 23 11:04:14 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:04:14 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:04:22 Gargoyle daemon.notice Tor[8230]: Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 23 11:04:22 Gargoyle daemon.notice Tor[8230]: Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 23 11:04:22 Gargoyle daemon.notice Tor[8230]: Bootstrapped 100%: Done.
Mar 23 11:04:22 Gargoyle daemon.notice Tor[8230]: Bootstrapped 100%: Done.
Mar 23 11:04:23 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:04:23 Gargoyle daemon.notice Tor[8230]: New control connection opened.
Mar 23 11:05:17 Gargoyle daemon.notice Tor[8230]: Catching signal TERM, exiting cleanly.
Mar 23 11:05:17 Gargoyle daemon.notice Tor[8230]: Catching signal TERM, exiting cleanly.
Mar 23 11:05:34 Gargoyle daemon.warn Tor[8811]: You are running Tor as root. You don't need to, and you probably shouldn't.
Mar 23 11:05:34 Gargoyle daemon.warn Tor[8811]: You are running Tor as root. You don't need to, and you probably shouldn't.
Mar 23 11:05:57 Gargoyle daemon.notice Tor[8811]: We now have enough directory information to build circuits.
Mar 23 11:05:57 Gargoyle daemon.notice Tor[8811]: We now have enough directory information to build circuits.
Mar 23 11:05:57 Gargoyle daemon.notice Tor[8811]: Bootstrapped 80%: Connecting to the Tor network.
Mar 23 11:05:57 Gargoyle daemon.notice Tor[8811]: Bootstrapped 80%: Connecting to the Tor network.
Mar 23 11:05:58 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:05:58 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:05 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:05 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:06 Gargoyle daemon.notice Tor[8811]: Bootstrapped 85%: Finishing handshake with first hop.
Mar 23 11:06:06 Gargoyle daemon.notice Tor[8811]: Bootstrapped 85%: Finishing handshake with first hop.
Mar 23 11:06:07 Gargoyle daemon.notice Tor[8811]: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Mar 23 11:06:07 Gargoyle daemon.notice Tor[8811]: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Mar 23 11:06:07 Gargoyle daemon.notice Tor[8811]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Mar 23 11:06:07 Gargoyle daemon.notice Tor[8811]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Mar 23 11:06:18 Gargoyle daemon.notice Tor[8811]: Bootstrapped 90%: Establishing a Tor circuit.
Mar 23 11:06:18 Gargoyle daemon.notice Tor[8811]: Bootstrapped 90%: Establishing a Tor circuit.
Mar 23 11:06:18 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:18 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:25 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:25 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:31 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:31 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:37 Gargoyle daemon.notice Tor[8811]: Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 23 11:06:37 Gargoyle daemon.notice Tor[8811]: Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 23 11:06:37 Gargoyle daemon.notice Tor[8811]: Bootstrapped 100%: Done.
Mar 23 11:06:37 Gargoyle daemon.notice Tor[8811]: Bootstrapped 100%: Done.
Mar 23 11:06:38 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:06:38 Gargoyle daemon.notice Tor[8811]: New control connection opened.
Mar 23 11:07:18 Gargoyle authpriv.info dropbear[9239]: Child connection from 192.168.3.134:63255
Mar 23 11:07:30 Gargoyle authpriv.warn dropbear[9239]: Login attempt for nonexistent user from 192.168.3.134:63255
Mar 23 11:07:34 Gargoyle authpriv.warn dropbear[9239]: Login attempt for nonexistent user from 192.168.3.134:63255
Mar 23 11:07:39 Gargoyle authpriv.warn dropbear[9239]: Login attempt for nonexistent user from 192.168.3.134:63255
Mar 23 11:07:42 Gargoyle authpriv.warn dropbear[9239]: Login attempt for nonexistent user from 192.168.3.134:63255
Mar 23 11:08:27 Gargoyle authpriv.info dropbear[9239]: Exit before auth: Exited normally
Mar 23 11:08:54 Gargoyle authpriv.info dropbear[13630]: Child connection from 192.168.3.134:63295
Mar 23 11:09:21 Gargoyle authpriv.warn dropbear[13630]: Login attempt for nonexistent user from 192.168.3.134:63295
Mar 23 11:09:29 Gargoyle authpriv.warn dropbear[13630]: Login attempt for nonexistent user from 192.168.3.134:63295
Mar 23 11:09:37 Gargoyle authpriv.info dropbear[13630]: Exit before auth: Exited normally
Mar 23 11:09:48 Gargoyle daemon.notice httpd_gargoyle[1810]: exiting due to signal 15
Mar 23 11:09:48 Gargoyle daemon.notice httpd_gargoyle[11264]: exiting due to signal 15
Mar 23 11:09:48 Gargoyle daemon.warn httpd_gargoyle[15705]: started as root without requesting chroot(), warning only
Mar 23 11:09:48 Gargoyle daemon.notice httpd_gargoyle[15705]: httpd_gargoyle/1.0 14mar2008 starting on Gargoyle, port 80
Mar 23 11:10:58 Gargoyle authpriv.info dropbear[15980]: Child connection from 192.168.3.134:63406
Mar 23 11:11:06 Gargoyle authpriv.warn dropbear[15980]: Login attempt for nonexistent user from 192.168.3.134:63406
Mar 23 11:11:10 Gargoyle authpriv.warn dropbear[15980]: Login attempt for nonexistent user from 192.168.3.134:63406
Mar 23 11:11:23 Gargoyle authpriv.warn dropbear[15980]: Login attempt for nonexistent user from 192.168.3.134:63406
Mar 23 11:11:26 Gargoyle authpriv.info dropbear[15980]: Exit before auth: Exited normally
Mar 23 11:11:48 Gargoyle authpriv.info dropbear[16001]: Child connection from 192.168.3.134:63410
Mar 23 11:12:01 Gargoyle authpriv.warn dropbear[16001]: Login attempt for nonexistent user from 192.168.3.134:63410
Mar 23 11:12:04 Gargoyle authpriv.warn dropbear[16001]: Login attempt for nonexistent user from 192.168.3.134:63410
Mar 23 11:12:18 Gargoyle authpriv.info dropbear[16001]: Exit before auth: Exited normally
Mar 23 11:12:40 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPINFORM(br-lan) 192.168.3.134 00:23
b8:d4:1aMar 23 11:12:40 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPACK(br-lan) 192.168.3.134 00:23
b8:d4:1a serverMar 23 11:12:58 Gargoyle authpriv.info dropbear[16069]: Child connection from 192.168.3.134:63435
Mar 23 11:13:14 Gargoyle authpriv.warn dropbear[16069]: Login attempt for nonexistent user from 192.168.3.134:63435
Mar 23 11:13:18 Gargoyle authpriv.warn dropbear[16069]: Login attempt for nonexistent user from 192.168.3.134:63435
Mar 23 11:13:40 Gargoyle authpriv.info dropbear[16069]: Exit before auth: Exited normally
Mar 23 11:14:03 Gargoyle daemon.info hostapd: wlan0: STA 00:23
b8:d4:1a WPA: group key handshake completed (RSN)Mar 23 11:14:03 Gargoyle daemon.info hostapd: wlan0: STA d0:22:be:51:e1:70 WPA: group key handshake completed (RSN)
Mar 23 11:15:35 Gargoyle authpriv.info dropbear[16187]: Child connection from 192.168.3.134:63459
Mar 23 11:15:41 Gargoyle authpriv.warn dropbear[16187]: Login attempt for nonexistent user from 192.168.3.134:63459
Mar 23 11:15:46 Gargoyle authpriv.warn dropbear[16187]: Login attempt for nonexistent user from 192.168.3.134:63459
Mar 23 11:15:51 Gargoyle authpriv.warn dropbear[16187]: Login attempt for nonexistent user from 192.168.3.134:63459
Mar 23 11:15:55 Gargoyle authpriv.warn dropbear[16187]: Login attempt for nonexistent user from 192.168.3.134:63459
Mar 23 11:16:04 Gargoyle authpriv.info dropbear[16187]: Exit before auth: Exited normally
Mar 23 11:19:40 Gargoyle authpriv.info dropbear[16256]: Child connection from 192.168.3.134:63488
Mar 23 11:21:44 Gargoyle authpriv.warn dropbear[16256]: Login attempt for nonexistent user from 192.168.3.134:63488
Mar 23 11:21:47 Gargoyle authpriv.warn dropbear[16256]: Login attempt for nonexistent user from 192.168.3.134:63488
Mar 23 11:21:50 Gargoyle authpriv.warn dropbear[16256]: Login attempt for nonexistent user from 192.168.3.134:63488
Mar 23 11:21:55 Gargoyle authpriv.info dropbear[16256]: Exit before auth: Exited normally
Mar 23 11:22:42 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPINFORM(br-lan) 192.168.3.134 00:23
b8:d4:1aMar 23 11:22:42 Gargoyle daemon.info dnsmasq-dhcp[2217]: DHCPACK(br-lan) 192.168.3.134 00:23
b8:d4:1a serverMar 23 11:24:02 Gargoyle authpriv.info dropbear[16343]: Child connection from 192.168.3.134:63544
Mar 23 11:24:03 Gargoyle daemon.info hostapd: wlan0: STA 00:23
b8:d4:1a WPA: group key handshake completed (RSN)Mar 23 11:24:03 Gargoyle daemon.info hostapd: wlan0: STA d0:22:be:51:e1:70 WPA: group key handshake completed (RSN)
Mar 23 11:24:10 Gargoyle authpriv.notice dropbear[16343]: Password auth succeeded for 'root' from 192.168.3.134:63544
Mar 23 11:25:36 Gargoyle authpriv.info dropbear[16343]: Exit (root): Exited normally
Mar 23 11:25:45 Gargoyle authpriv.info dropbear[16370]: Child connection from 192.168.3.134:63559
Mar 23 11:25:52 Gargoyle authpriv.notice dropbear[16370]: Password auth succeeded for 'root' from 192.168.3.134:63559
root@Gargoyle:~#
Re: Tor Plugin not work
The log says that at 11:03 and 11:05 Tor was restarted. Did you do anything (like re-save the Tor settings) that would explicitly cause this at these times?
Also, can you re-send a log after you've attempted (but failed) to make a connection to the onion site mentioned above, and send me the exact time you tried to make the connection? That way I can correlate the messages I see in the log with your failed attempt to access a hidden service.
Also, can you re-send a log after you've attempted (but failed) to make a connection to the onion site mentioned above, and send me the exact time you tried to make the connection? That way I can correlate the messages I see in the log with your failed attempt to access a hidden service.