Gargoyle Forum

Eric has addressed this now.
Looks like I was pretty much on the money.

@ispy will probably pick up a build soon?

does it mean the image file below gets the issue ironed out?
http://www.lantisproject.com/gargoyle_i ... pgrade.bin

ysy wrote:does it mean the image file below gets the issue ironed out?
http://www.lantisproject.com/gargoyle_i ... pgrade.bin

I suspect not?

this does thought

viewtopic.php?f=14&t=11305

Yes that is a mirror of ispy's torrent

just flashed the latest Gargoyle Version: 1.10.X (Built 20171112-0128 git@2219e41)

syslog reported TOR symblink issue:
______________________________
Tue Nov 14 20:10:05 2017 daemon.warn Tor[10877]: Directory /var/tor/keys cannot be read: Too many levels of symbolic links
Tue Nov 14 20:10:05 2017 daemon.err Tor[10877]: Error initializing keys; exiting
Tue Nov 14 20:10:06 2017 daemon.err uhttpd[1699]: nc: can't connect to remote host (127.0.0.1): Connection refused
.
.
.
Tue Nov 14 20:10:50 2017 daemon.err uhttpd[1699]: nc: can't connect to remote host (127.0.0.1): Connection refused
Tue Nov 14 20:11:00 2017 user.notice root: Tor seems to have died unexpectedly, restarting
______________________________

Did you preserve settings?
Also are you installing Tor from the plugin repo or is it preinstalled for your router?

Lantis wrote:Did you preserve settings?
Also are you installing Tor from the plugin repo or is it preinstalled for your router?

Did not preserve settings.
Yep, had to extroot first, then installed Tor from the plugin. I saw four modules pre-installed, hence couldn't be removed to make way for Tor: -
English-EN language strings for Gargoyle web interface
OpenVPN Support for Gargoyle
USB Printer Support for Gargoyle
USB Storage Support for Gargoyle

Maybe we can try having openvpn not pre-installed for the next release?

Ok you are installing the old version.

Can you please uninstall Tor plugin, and add this as a plugin repository? Then refresh plugins and install. Then try again.

guess i did it right, but got the same error. Tor 0.3.1.7 (git-6babd3d9ba9318b3) was the running version. a quick web search gave me the impression that this might be due to a bug in Tor itself.

begin log --------------
Wed Nov 15 10:39:00 2017 user.notice root: Tor seems to have died unexpectedly, restarting
Wed Nov 15 10:39:03 2017 daemon.err uhttpd[1699]: nc: can't connect to remote host (127.0.0.1): Connection refused
Wed Nov 15 10:39:05 2017 daemon.notice Tor[2062]: Tor 0.3.1.7 (git-6babd3d9ba9318b3) running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2l, Zlib 1.2.8, Liblzma N/A, and Libzstd N/A.
Wed Nov 15 10:39:05 2017 daemon.notice Tor[2062]: Based on detected system memory, MaxMemInQueues is set to 256 MB. You can override this by setting MaxMemInQueues by hand.
Wed Nov 15 10:39:05 2017 daemon.warn Tor[2062]: Being a directory cache (default) with less than DIRCACHE_MIN_MEM_MB MB of memory is not recommended and may consume most of the available resources, consider disabling this functionality by setting the DirCache option to 0.
Wed Nov 15 10:39:05 2017 daemon.warn Tor[2062]: 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.
Wed Nov 15 10:39:05 2017 daemon.notice Tor[2062]: Configured to measure directory request statistics, but no GeoIP database found. Please specify a GeoIP database using the GeoIPFile option.
Wed Nov 15 10:39:05 2017 daemon.warn Tor[2062]: Directory /usr/lib/tor/keys cannot be read: Too many levels of symbolic links
Wed Nov 15 10:39:05 2017 daemon.err Tor[2062]: Error initializing keys; exiting

Update: it seems that Tor server runs fine, after going back to oem firmware, formatting the usb thumb, and then applying factory.bin and extroot.

Maybe one should restore firmware default prior to applying sysupgrade.bin to ensure that old settings are removed completely?