TOR not working Gargoyle 1.9 WR1043ND V3

Report wireless and/or network connectivity problems in this forum.

Moderator: Moderators

Post Reply
suffix
Posts: 12
Joined: Fri Apr 29, 2016 3:46 pm

TOR not working Gargoyle 1.9 WR1043ND V3

Post by suffix »

Hey all,

after havin hard times of installing gargoyle, mounting my usb to my wr1043nd v3 and getting ready to finally install the TOR plugin, I am just not able to get it work!

Herre are my settings:

Image

Here is my log:


root@Gargoyle:~# logread
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain micro
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain micro
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain micro
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain oss
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain oss
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain oss
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain null
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain null
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain null
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain ing
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain ing
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain ing
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain indy
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain indy
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain indy
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain gopher
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain gopher
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain gopher
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain geek
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain geek
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain geek
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain fur
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain fur
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain fur
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain free
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain free
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain free
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain bbs
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain bbs
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain bbs
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain dyn
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain dyn
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain dyn
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain parody
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain parody
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain parody
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain glue
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain glue
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain glue
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 176.58.118.172#53 for domain bit
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 106.187.47.17#53 for domain bit
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 178.32.31.41#53 for domain bit
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using local addresses only for domain lan
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: reading /tmp/resolv.conf.auto
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain micro
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain micro
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain micro
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain oss
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain oss
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain oss
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain null
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain null
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain null
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain ing
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain ing
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain ing
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain indy
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain indy
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain indy
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain gopher
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain gopher
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain gopher
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain geek
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain geek
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain geek
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain fur
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain fur
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain fur
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain free
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain free
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain free
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain bbs
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain bbs
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain bbs
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain dyn
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain dyn
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain dyn
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain parody
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain parody
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain parody
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.142.171.235#53 for domain glue
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 95.211.32.162#53 for domain glue
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 66.244.95.20#53 for domain glue
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 176.58.118.172#53 for domain bit
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 106.187.47.17#53 for domain bit
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 178.32.31.41#53 for domain bit
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using local addresses only for domain lan
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: using nameserver 192.168.178.1#53
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: read /etc/hosts - 2 addresses
Fri Apr 29 21:40:31 2016 daemon.info dnsmasq[14115]: read /tmp/hosts/dhcp - 1 addresses
Fri Apr 29 21:40:31 2016 daemon.err uhttpd[1680]: uci: Entry not found
Fri Apr 29 21:40:31 2016 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Fri Apr 29 21:40:31 2016 daemon.notice netifd: radio0 (14069): Configuration file: /var/run/hostapd-phy0.conf
Fri Apr 29 21:40:31 2016 kern.info kernel: [ 3674.400000] device wlan0 entered promiscuous mode
Fri Apr 29 21:40:31 2016 kern.info kernel: [ 3674.410000] br-lan: port 3(wlan0) entered forwarding state
Fri Apr 29 21:40:31 2016 kern.info kernel: [ 3674.410000] br-lan: port 3(wlan0) entered forwarding state
Fri Apr 29 21:40:31 2016 daemon.notice netifd: radio0 (14069): Using interface wlan0 with hwaddr f4:f2:6d:dc:36:26 and ssid "Gargoyle"
Fri Apr 29 21:40:31 2016 daemon.notice netifd: radio0 (14069): wlan0: interface state UNINITIALIZED->ENABLED
Fri Apr 29 21:40:31 2016 daemon.notice netifd: radio0 (14069): wlan0: AP-ENABLED
Fri Apr 29 21:40:31 2016 daemon.notice netifd: Network device 'wlan0' link is up
Fri Apr 29 21:40:32 2016 kern.info kernel: [ 3675.310000] br-lan: port 1(eth1) entered forwarding state
Fri Apr 29 21:40:32 2016 kern.info kernel: [ 3675.330000] br-lan: port 2(eth0) entered forwarding state
Fri Apr 29 21:40:33 2016 kern.info kernel: [ 3676.410000] br-lan: port 3(wlan0) entered forwarding state
Fri Apr 29 21:41:21 2016 user.notice firewall: Reloading firewall due to ifup of wan6 (eth0)
Fri Apr 29 21:42:38 2016 daemon.notice Tor[8877]: Catching signal TERM, exiting cleanly.
Fri Apr 29 21:42:38 2016 daemon.notice Tor[8877]: Catching signal TERM, exiting cleanly.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Tor v0.2.6.10 (git-58c51dc6087b0936) running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2d and Zlib 1.2.8.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Tor v0.2.6.10 (git-58c51dc6087b0936) running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2d and Zlib 1.2.8.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Read configuration file "/etc/tor/torrc".
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Read configuration file "/etc/tor/torrc".
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: You configured a non-loopback address '192.168.178.11:9053' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: You configured a non-loopback address '192.168.178.11:9053' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: You configured a non-loopback address '192.168.178.11:9040' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: You configured a non-loopback address '192.168.178.11:9040' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri Apr 29 21:42:39 2016 daemon.warn Tor[15376]: ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That's bad! You should upgrade your Tor controller as soon as possible.
Fri Apr 29 21:42:39 2016 daemon.warn Tor[15376]: ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That's bad! You should upgrade your Tor controller as soon as possible.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: You configured a non-loopback address '192.168.178.11:9053' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: You configured a non-loopback address '192.168.178.11:9053' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: You configured a non-loopback address '192.168.178.11:9040' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: You configured a non-loopback address '192.168.178.11:9040' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Opening DNS listener on 192.168.178.11:9053
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Opening DNS listener on 192.168.178.11:9053
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Opening Transparent pf/netfilter listener on 192.168.178.11:9040
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Opening Transparent pf/netfilter listener on 192.168.178.11:9040
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Opening Control listener on 127.0.0.1:9051
Fri Apr 29 21:42:39 2016 daemon.notice Tor[15376]: Opening Control listener on 127.0.0.1:9051
Fri Apr 29 21:42:39 2016 daemon.warn Tor[15376]: You are running Tor as root. You don't need to, and you probably shouldn't.
Fri Apr 29 21:42:39 2016 daemon.warn Tor[15376]: You are running Tor as root. You don't need to, and you probably shouldn't.
Fri Apr 29 21:42:40 2016 daemon.err uhttpd[1680]: iptables v1.4.21: Couldn't load match `layer7':No such file or directory
Fri Apr 29 21:42:40 2016 daemon.err uhttpd[1680]:
Fri Apr 29 21:42:40 2016 daemon.err uhttpd[1680]: Try `iptables -h' or 'iptables --help' for more information.
Fri Apr 29 21:42:40 2016 daemon.err uhttpd[1680]: iptables v1.4.21: Couldn't load match `layer7':No such file or directory
Fri Apr 29 21:42:40 2016 daemon.err uhttpd[1680]:
Fri Apr 29 21:42:40 2016 daemon.err uhttpd[1680]: Try `iptables -h' or 'iptables --help' for more information.
Fri Apr 29 21:42:41 2016 daemon.notice Tor[15376]: Bootstrapped 0%: Starting
Fri Apr 29 21:42:41 2016 daemon.notice Tor[15376]: Bootstrapped 0%: Starting
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: Bootstrapped 5%: Connecting to directory server
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: Bootstrapped 5%: Connecting to directory server
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: Bootstrapped 80%: Connecting to the Tor network
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: Bootstrapped 80%: Connecting to the Tor network
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: New control connection opened from 127.0.0.1.
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: New control connection opened from 127.0.0.1.
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: Bootstrapped 85%: Finishing handshake with first hop
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: Bootstrapped 85%: Finishing handshake with first hop
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: 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.
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: 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.
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Fri Apr 29 21:42:45 2016 daemon.notice Tor[15376]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
Fri Apr 29 21:42:47 2016 daemon.notice Tor[15376]: Bootstrapped 90%: Establishing a Tor circuit
Fri Apr 29 21:42:47 2016 daemon.notice Tor[15376]: Bootstrapped 90%: Establishing a Tor circuit
Fri Apr 29 21:42:47 2016 daemon.notice Tor[15376]: New control connection opened from 127.0.0.1.
Fri Apr 29 21:42:47 2016 daemon.notice Tor[15376]: New control connection opened from 127.0.0.1.
Fri Apr 29 21:42:47 2016 daemon.notice Tor[15376]: Tor has successfully opened a circuit. Looks like client functionality is working.
Fri Apr 29 21:42:47 2016 daemon.notice Tor[15376]: Tor has successfully opened a circuit. Looks like client functionality is working.
Fri Apr 29 21:42:47 2016 daemon.notice Tor[15376]: Bootstrapped 100%: Done
Fri Apr 29 21:42:47 2016 daemon.notice Tor[15376]: Bootstrapped 100%: Done
Fri Apr 29 21:42:49 2016 daemon.notice Tor[15376]: New control connection opened from 127.0.0.1.
Fri Apr 29 21:42:49 2016 daemon.notice Tor[15376]: New control connection opened from 127.0.0.1.
root@Gargoyle:~#


Maybe u will want to know that i also have installed TOR and Privoxy in freetz on my fritzbox. Its configured to be used as a proxy, what is actually working fine. But i have a device where it is not possible to set up a proxy and therefore i bought the 1043nd v3 to use it with gargoyle as an access point and get everything routed through tor with this setup....


Anybody knows what i am missing? I just dont get it. If i type in an .onion address, chrome tells me that the DNS address couldn't be found.

nworbnhoj
Posts: 916
Joined: Mon Jul 21, 2014 10:08 am
Location: Australia
Contact:

Re: TOR not working Gargoyle 1.9 WR1043ND V3

Post by nworbnhoj »

logout as Gargoyle admin and on the Gargoyle login webpage there will be a button to toggle Tor for the host that you are on. Does this work for you?

Toggling Tor for a hsot without a browser is a bit more tricky! Sorry, cannot remember the file name at the moment, but there is a simply text file that stores the ip addresses for hosts which have been toggled tor active. You can simply manually edit this file to add other (static) ip addresses. If you cannot locate the file get back to me an I will chase it down (again)
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

suffix
Posts: 12
Joined: Fri Apr 29, 2016 3:46 pm

Re: TOR not working Gargoyle 1.9 WR1043ND V3

Post by suffix »

Thanks! I must have been blind. Anyways, i get this error message.

Image

My IP is static and DHCP is off, since im using the fritzbox as a DHCP Server.

connection settings
Image

dhcp
Image

suffix
Posts: 12
Joined: Fri Apr 29, 2016 3:46 pm

Re: TOR not working Gargoyle 1.9 WR1043ND V3

Post by suffix »

If I try to change settings, for example to activate TOR for all hosts, i get this message when i try to save changes:

http://www.pic-upload.de/view-30506012/ ... s.jpg.html


If i activate tor for all hosts, the button to activate it disappears and its still not working...

suffix
Posts: 12
Joined: Fri Apr 29, 2016 3:46 pm

Re: TOR not working Gargoyle 1.9 WR1043ND V3

Post by suffix »

Ok, I dont know why, but now the toggle for switching TOR on after Logout disappeared... it is still configured as "Enabled, Toggle By Each Host", but the toggle is not there anymore...

sorry for multipost..

nworbnhoj
Posts: 916
Joined: Mon Jul 21, 2014 10:08 am
Location: Australia
Contact:

Re: TOR not working Gargoyle 1.9 WR1043ND V3

Post by nworbnhoj »

There is a problem with your configuration.
Gargoyle - Connection - Basic - Internet/WAN - Static IP - 192.168.178.X
cannot be in the same range as
Gargoyle - Connection - Basic - Local Network / LAN - Router IP- 192.168.178.X

This may help
https://www.gargoyle-router.com/wiki/do ... ario-modem
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

suffix
Posts: 12
Joined: Fri Apr 29, 2016 3:46 pm

Re: TOR not working Gargoyle 1.9 WR1043ND V3

Post by suffix »

Not really... I dont know what to type in there then. I need to have the 1043ND in my network...

If I put another range its not in my network thats being created of the dhcp server...

suffix
Posts: 12
Joined: Fri Apr 29, 2016 3:46 pm

Re: TOR not working Gargoyle 1.9 WR1043ND V3

Post by suffix »

I think i totally messed it up now... I changed the mode to disabled and then put it to "WAN bridge to LAN" (or sth similar).
Now i cant access the TP link at all... the Webgui just wont show up anymore... is there a way to reset it without gui?

nworbnhoj
Posts: 916
Joined: Mon Jul 21, 2014 10:08 am
Location: Australia
Contact:

Re: TOR not working Gargoyle 1.9 WR1043ND V3

Post by nworbnhoj »

suffix wrote: is there a way to reset it without gui?
Login to the Gargoyle command line interface and type firstboot at the prompt

viewtopic.php?f=8&t=8505&p=37739&hilit=cli#p37739
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

Post Reply