1.9.x problems with hidden tor

Report problems and success stories with Gargoyle on various hardware platforms.

Moderator: Moderators

Post Reply
petbrau
Posts: 28
Joined: Fri Jan 29, 2016 2:08 pm

1.9.x problems with hidden tor

Post by petbrau »

Hello there,

I am a newbie in using gargoyle and maybe someone can help me configuring my router with firmware 1.9.X (Built 20160124-1820 git@bd9e63e).
When I switch on the hidden tor function, my router crashes reproducible after some minutes.
But this is only the case, when using tor for hidden services.
If tor is used for all hosts, it works without any problem.

Here, the configuration I am using
2016-01-29 20_25_04-Gargoyle Router Verwaltung.png
2016-01-29 20_25_04-Gargoyle Router Verwaltung.png (28.66 KiB) Viewed 7106 times
What do I have to do?
Last edited by petbrau on Sat Feb 06, 2016 3:00 pm, edited 1 time in total.
Top
ispyisail
Moderator
Posts: 5185
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: 1.9.x problems with hidden tor

Post by ispyisail »

enable USB swap?

run out of RAM?
Top
petbrau
Posts: 28
Joined: Fri Jan 29, 2016 2:08 pm

Re: 1.9.x problems with hidden tor

Post by petbrau »

ispyisail,
thanks for your advice, but my router has 128MB of RAM.
I checked the RAM status on the status/overview page and the memory usage never exceeded 40 MB until crash.
I flashed back from 1.9.x to 1.9.0 and with the modifications described in http://www.gargoyle-router.com/phpbb/vi ... 584#p30584 the hidden service of the tor client works great.
So it seems, a modification from 1.9.0 to 1.9.x is responsible for this crash behavior.
Top
petbrau
Posts: 28
Joined: Fri Jan 29, 2016 2:08 pm

Re: 1.9.x problems with hidden tor

Post by petbrau »

The handling of layer7 could be the problem.
As I switched on QoS and defined some rules using layer7 protocol, the router crashed after a few minutes.
Layer7 is used in QoS and hidden Tor and was added between 1.9.0 and 1.9.x.
It makes me wonder, that I am the only user, who realizes these problems. At least QoS is a standard feature nearly everybody uses.
Last edited by petbrau on Sat Feb 06, 2016 2:59 pm, edited 2 times in total.
Top
nworbnhoj
Posts: 916
Joined: Mon Jul 21, 2014 10:08 am
Location: Australia
Contact:
Contact nworbnhoj

Re: 1.9.x problems with hidden tor

Post by nworbnhoj »

petbrau wrote:The handling of layer7 could be the problem.
As I switched on QoS and defined some rules using layer7 protcol, the router crashed after a fiew minutes.
That is interesting. Layer7 support has existed for ages but then OpenWRT removed it a while back and broke the Gargoyle stuff that relied on it (including tor). @Eric added Layer7 back in recently but maybe there are still problems.
Can you check logread for anything interesting after you configure Layer7 stuff and before it crashes please? Also please get onto the latest @ispyisail build. Thanks
Can you help someone else get Gargoyle up and running?
TL-WDR3600 : Gargoyle 1.9.0 : NBN FixedWireless
TL-WR1043ND-V2 : Gargoyle 1.8.0 : 3G Huawei E160E
Top
petbrau
Posts: 28
Joined: Fri Jan 29, 2016 2:08 pm

Re: 1.9.x problems with hidden tor

Post by petbrau »

Hi nworbnhoj,

as you can imagine, it is hard to get a logfile seconds before he router crashes.
I compiled the latest source code and flashed the image on my router. Unfortunately the problem still exists.

I switched on the tor client and with the standard system log function, no real problem can be detected until crash. (The errors and warnings contained in the log, should be normal)

Code: Select all

Sun Jan 31 11:17:54 2016 daemon.notice Tor[2478]: You configured a non-loopback address '192.168.1.1:9053' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Sun Jan 31 11:17:54 2016 daemon.notice Tor[2478]: You configured a non-loopback address '192.168.1.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.
Sun Jan 31 11:17:54 2016 daemon.notice Tor[2478]: You configured a non-loopback address '192.168.1.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.
Sun Jan 31 11:17:54 2016 daemon.notice Tor[2478]: Opening DNS listener on 192.168.1.1:9053
Sun Jan 31 11:17:54 2016 daemon.notice Tor[2478]: Opening DNS listener on 192.168.1.1:9053
Sun Jan 31 11:17:54 2016 daemon.notice Tor[2478]: Opening Transparent pf/netfilter listener on 192.168.1.1:9040
Sun Jan 31 11:17:54 2016 kern.warn kernel: [   33.760000] ipt_bandwidth: timezone shift of 60 minutes detected, adjusting
Sun Jan 31 11:17:54 2016 kern.warn kernel: [   33.770000]                old minutes west=0, new minutes west=-60
Sun Jan 31 11:17:58 2016 daemon.notice Tor[2478]: Bootstrapped 0%: Starting
Sun Jan 31 11:17:58 2016 daemon.notice Tor[2478]: Bootstrapped 0%: Starting
Sun Jan 31 11:17:59 2016 daemon.info ddns_gargoyle[2528]: 	Update successful

Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: Bootstrapped 5%: Connecting to directory server
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: Bootstrapped 5%: Connecting to directory server
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: Bootstrapped 10%: Finishing handshake with directory server
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: Bootstrapped 10%: Finishing handshake with directory server
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: 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.
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: 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.
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: Bootstrapped 15%: Establishing an encrypted directory connection
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: Bootstrapped 15%: Establishing an encrypted directory connection
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: Bootstrapped 20%: Asking for networkstatus consensus
Sun Jan 31 11:17:59 2016 daemon.notice Tor[2478]: Bootstrapped 20%: Asking for networkstatus consensus
Sun Jan 31 11:18:00 2016 daemon.notice Tor[2478]: Bootstrapped 25%: Loading networkstatus consensus
Sun Jan 31 11:18:00 2016 daemon.notice Tor[2478]: Bootstrapped 25%: Loading networkstatus consensus
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: started, version 2.73 cachesize 150
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: DNS service limited to local subnets
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq-dhcp[2812]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 6h
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain micro
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain micro
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain micro
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain oss
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain oss
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain oss
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain null
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain null
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain null
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain ing
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain ing
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain ing
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain indy
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain indy
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain indy
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain gopher
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain gopher
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain gopher
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain geek
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain geek
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain geek
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain fur
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain fur
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain fur
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain free
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain free
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain free
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain bbs
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain bbs
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain bbs
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain dyn
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain dyn
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain dyn
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain parody
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain parody
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain parody
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain glue
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain glue
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain glue
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 176.58.118.172#53 for domain bit
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 106.187.47.17#53 for domain bit
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 178.32.31.41#53 for domain bit
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using local addresses only for domain lan
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: reading /tmp/resolv.conf.auto
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain micro
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain micro
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain micro
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain oss
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain oss
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain oss
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain null
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain null
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain null
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain ing
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain ing
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain ing
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain indy
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain indy
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain indy
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain gopher
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain gopher
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain gopher
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain geek
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain geek
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain geek
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain fur
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain fur
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain fur
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain free
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain free
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain free
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain bbs
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain bbs
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain bbs
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain dyn
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain dyn
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain dyn
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain parody
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain parody
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain parody
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.142.171.235#53 for domain glue
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 95.211.32.162#53 for domain glue
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 66.244.95.20#53 for domain glue
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 176.58.118.172#53 for domain bit
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 106.187.47.17#53 for domain bit
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 178.32.31.41#53 for domain bit
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using local addresses only for domain lan
Sun Jan 31 11:18:01 2016 daemon.warn dnsmasq[2812]: ignoring nameserver 192.168.1.1 - local interface
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 78.42.43.41#53
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: using nameserver 82.212.62.41#53
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: read /etc/hosts - 3 addresses
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq[2812]: read /tmp/hosts/dhcp - 1 addresses
Sun Jan 31 11:18:01 2016 daemon.info dnsmasq-dhcp[2812]: read /etc/ethers - 1 addresses
Sun Jan 31 11:18:02 2016 daemon.notice Tor[2478]: I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Sun Jan 31 11:18:02 2016 daemon.notice Tor[2478]: I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Sun Jan 31 11:18:02 2016 daemon.notice Tor[2478]: Bootstrapped 40%: Loading authority key certs
Sun Jan 31 11:18:02 2016 daemon.notice Tor[2478]: Bootstrapped 40%: Loading authority key certs
Sun Jan 31 11:18:02 2016 kern.notice kernel: [   42.000000] random: nonblocking pool is initialized
Sun Jan 31 11:18:05 2016 daemon.notice Tor[2478]: Bootstrapped 45%: Asking for relay descriptors
Sun Jan 31 11:18:05 2016 daemon.notice Tor[2478]: Bootstrapped 45%: Asking for relay descriptors
Sun Jan 31 11:18:05 2016 daemon.notice Tor[2478]: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7142, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
Sun Jan 31 11:18:05 2016 daemon.notice Tor[2478]: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7142, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
Sun Jan 31 11:18:06 2016 daemon.notice Tor[2478]: Bootstrapped 50%: Loading relay descriptors
Sun Jan 31 11:18:06 2016 daemon.notice Tor[2478]: Bootstrapped 50%: Loading relay descriptors
Sun Jan 31 11:18:07 2016 daemon.info dnsmasq-dhcp[2812]: DHCPREQUEST(br-lan) 192.168.1.100 00:25:86:ee:ce:da 
Sun Jan 31 11:18:07 2016 daemon.info dnsmasq-dhcp[2812]: DHCPACK(br-lan) 192.168.1.100 00:25:86:ee:ce:da PC
Sun Jan 31 11:18:08 2016 daemon.info hostapd: wlan0: STA 20:62:74:d9:e8:78 IEEE 802.11: authenticated
Sun Jan 31 11:18:08 2016 daemon.info hostapd: wlan0: STA 20:62:74:d9:e8:78 IEEE 802.11: associated (aid 2)
Sun Jan 31 11:18:08 2016 daemon.info hostapd: wlan0: STA 20:62:74:d9:e8:78 RADIUS: starting accounting session 56ADDF4E-00000001
Sun Jan 31 11:18:08 2016 daemon.info hostapd: wlan0: STA 20:62:74:d9:e8:78 WPA: pairwise key handshake completed (RSN)
Sun Jan 31 11:18:13 2016 daemon.notice Tor[2478]: Bootstrapped 56%: Loading relay descriptors
Sun Jan 31 11:18:13 2016 daemon.notice Tor[2478]: Bootstrapped 56%: Loading relay descriptors
Sun Jan 31 11:18:15 2016 daemon.notice Tor[2478]: Bootstrapped 64%: Loading relay descriptors
Sun Jan 31 11:18:15 2016 daemon.notice Tor[2478]: Bootstrapped 64%: Loading relay descriptors
Sun Jan 31 11:18:16 2016 daemon.notice Tor[2478]: Bootstrapped 73%: Loading relay descriptors
Sun Jan 31 11:18:16 2016 daemon.notice Tor[2478]: Bootstrapped 73%: Loading relay descriptors
Sun Jan 31 11:18:17 2016 daemon.notice Tor[2478]: Bootstrapped 80%: Connecting to the Tor network
Sun Jan 31 11:18:17 2016 daemon.notice Tor[2478]: Bootstrapped 80%: Connecting to the Tor network
Sun Jan 31 11:18:17 2016 daemon.notice Tor[2478]: Bootstrapped 90%: Establishing a Tor circuit
Sun Jan 31 11:18:17 2016 daemon.notice Tor[2478]: Bootstrapped 90%: Establishing a Tor circuit
Sun Jan 31 11:18:19 2016 daemon.notice Tor[2478]: Tor has successfully opened a circuit. Looks like client functionality is working.
Sun Jan 31 11:18:19 2016 daemon.notice Tor[2478]: Tor has successfully opened a circuit. Looks like client functionality is working.
Sun Jan 31 11:18:19 2016 daemon.notice Tor[2478]: Bootstrapped 100%: Done
Sun Jan 31 11:18:19 2016 daemon.notice Tor[2478]: Bootstrapped 100%: Done
Sun Jan 31 11:18:20 2016 user.notice root: vsftpd init: mounted = 0
Sun Jan 31 11:18:20 2016 user.emerg syslog: ERROR: No drives attached, no directories to share!
Sun Jan 31 11:18:20 2016 user.emerg syslog: setting up led WAN LED (green)
Sun Jan 31 11:18:20 2016 daemon.info procd: - init complete -
Success
This week, I have no time to make a deep dive, but maybe some other users can reproduce this problem and will give us their support.
Last edited by petbrau on Thu Mar 31, 2016 5:48 am, edited 1 time in total.
Top
nworbnhoj
Posts: 916
Joined: Mon Jul 21, 2014 10:08 am
Location: Australia
Contact:
Contact nworbnhoj

Re: 1.9.x problems with hidden tor

Post by nworbnhoj »

petbrau wrote:I switched on the tor client and with the standard system log function, no real problem can be detected until crash.
Thank you - but nothing much helpful there as you can see - all looks happy.

Are your QOS layer 7 rules actually doing something useful for you? I gave up in L7 a while back. Interested to know if they are of value?
Can you help someone else get Gargoyle up and running?
TL-WDR3600 : Gargoyle 1.9.0 : NBN FixedWireless
TL-WR1043ND-V2 : Gargoyle 1.8.0 : 3G Huawei E160E
Top
petbrau
Posts: 28
Joined: Fri Jan 29, 2016 2:08 pm

Re: 1.9.x problems with hidden tor

Post by petbrau »

Of course, only a few persons really need Layer 7 support, but if it's implemented and part of the system, it has to work (for my router, TOR is a standard plugin that can't be removed).

I would be pleased, if someone can check, if the crash is related to my type of router or if it's a general problem (please use gargoyle-ispy 1.9.x Jan 18 or later).
You just have to switch-on the tor client for hidden services and wait some minutes. If a crash occurs, after the reboot, you can switch-off the TOR service and everything works fine once again (no problem or risk for your router).
Be careful, using Layer7 in QoS. I got a reboot loop, which was a little bit more complex to fix.
Please, let me know your test results.
Top
nworbnhoj
Posts: 916
Joined: Mon Jul 21, 2014 10:08 am
Location: Australia
Contact:
Contact nworbnhoj

Re: 1.9.x problems with hidden tor

Post by nworbnhoj »

petbrau wrote:I would be pleased, if someone can check, if the crash is related to my type of router or if it's a general problem (please use gargoyle-ispy 1.9.x Jan 18 or later).
You just have to switch-on the tor client for hidden services and wait some minutes.
Confirmed - except that enabling tor client for hidden services resulted in a reboot loop. Fixed with a ssh firstboot.
Can you help someone else get Gargoyle up and running?
TL-WDR3600 : Gargoyle 1.9.0 : NBN FixedWireless
TL-WR1043ND-V2 : Gargoyle 1.8.0 : 3G Huawei E160E
Top
petbrau
Posts: 28
Joined: Fri Jan 29, 2016 2:08 pm

Re: 1.9.x problems with hidden tor

Post by petbrau »

oh sorry.
I had some minutes after reboot. Maybe due to the hardware differences. So very risky for those, who are not familiar with failsave mode.
But thank you for the info, that this is not a problem of my router only.
Top
Post Reply

Return to “Hardware / Installation Issues”