Version 1.10.0 marks a long overdue new stable version based on OpenWRT Chaos Calmer, while work is underway to port Gargoyle to the latest version of LEDE.
This version includes several critical security fixes, so upgrading to 1.10.0 is strongly recommended.
New in 1.10.0:
KRACK wireless WPA vulnerabiltiy patched
dnsmasq upgraded to 2.78, with critical security fixes
OpenWRT version upgraded to latest in Chaos Calmer branch
Numerous Improvements for new GUI them, in particular easier menu navigation on mobile devices
Tor upated to 0.3.1.7
MiniDLNA updated to 1.2.1
OpenVPN updated to 2.3.18
OpenVPN configuration using a single file now supported
As of this version, failsafe must be accessed via SSH instead of Telnet
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
mojolacerator wrote:Is it just me being old and blind? Or is Rango/WRT3200ACM not listed.
Not just you, I’ll check with Eric
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Shall be swapping to this from 1.9.2 tomorrow... but what's the best way ? Tplink 3600... I presume I download the "upgrade" version and away we go, but can I backup my current settings, or must I set it from scratch again ?
but can I backup my current settings, or must I set it from scratch again ?
I personally wouldn't install on 4MB routers or use any backup setting derived from either a backup file or preserve settings when flashing this version of Gargoyle.
I'm not sure what Eric's thinking is on these topics?
Tip: Don't rush configuring your router. My hypothesis is clicking on Gargoyle UI screens or buttons before a previous process has finished can corrupt the gargoyle config requireing a re-flash or reset.
-----log----- Sun Oct 29 00:16:05 2017 daemon.notice Tor[15572]: 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. Sun Oct 29 00:16:05 2017 daemon.notice Tor[15572]: Tor can't help you if you use it wrong! Learn how to be safe at ***.torproject.***/download/download#warning Sun Oct 29 00:16:05 2017 daemon.notice Tor[15572]: Read configuration file "/etc/tor/torrc". Sun Oct 29 00:16:05 2017 daemon.notice Tor[15572]: Based on detected system memory, MaxMemInQueues is set to 256 MB. You can override this by setting MaxMemInQueues by hand. Sun Oct 29 00:16:05 2017 daemon.warn Tor[15572]: 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. Sun Oct 29 00:16:05 2017 daemon.warn Tor[15572]: 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. Sun Oct 29 00:16:05 2017 daemon.notice Tor[15572]: Opening Control listener on 127.0.0.1:9051 Sun Oct 29 00:16:05 2017 daemon.notice Tor[15572]: Opening OR listener on 0.0.0.0:9090 Sun Oct 29 00:16:05 2017 daemon.notice Tor[15572]: Configured to measure directory request statistics, but no GeoIP database found. Please specify a GeoIP database using the GeoIPFile option. Sun Oct 29 00:16:05 2017 daemon.warn Tor[15572]: Directory /usr/lib/tor/keys cannot be read: Too many levels of symbolic links Sun Oct 29 00:16:05 2017 daemon.err Tor[15572]: Error initializing keys; exiting Sun Oct 29 00:16:06 2017 daemon.err uhttpd[14395]: nc: can't connect to remote host (127.0.0.1): Connection refused Sun Oct 29 00:17:00 2017 user.notice root: Tor seems to have died unexpectedly, restarting
