Version 1.7.2
Moderator: Moderators
Re: Version 1.7.2
Just updated to 1.7.2 and restored saved configuration from 1.7.x 1043nd v1.7 by the way where is the adlock located, can't find it.
Re: Version 1.7.2
Hi after you have installed it from the plugins page it should show up under firewall.apvm wrote:Just updated to 1.7.2 and restored saved configuration from 1.7.x 1043nd v1.7 by the way where is the adlock located, can't find it.
Linksys WRT3200ACM
NETGEAR Nighthawk R7800
NETGEAR R6260
NETGEAR Nighthawk R7800
NETGEAR R6260
Re: Version 1.7.2
Thanks, I thought it was preinstalled.tapper wrote:Hi after you have installed it from the plugins page it should show up under firewall.apvm wrote:Just updated to 1.7.2 and restored saved configuration from 1.7.x 1043nd v1.7 by the way where is the adlock located, can't find it.
-
- Posts: 3
- Joined: Sun Jul 19, 2015 1:54 pm
Re: Version 1.7.2
It would be nice if the TOR-Plugin issue could be fixed
TP Link Archer C5 and C7
TP Link Archer C5 and C7
Re: Version 1.7.2
I am also broadcasting a Guest network on 2.4GHz only, with WPA2 PSK. From time to time (2-24hrs) this Guest network stops broadcasting despite having 4-6 wifi client connected. The primary wifi SSID continues to operate correctly (Dual Band 20MHz ch11 & 40MHz (2nd channel above) ch157).nworbnhoj wrote:Successfully installed on TL-WDR3600 including 3G, Tor, Dynamic DNS, port forwarding, Adblock, Quotas, QoS, USB Storage.
/etc/init.d/network restart resolves the issue.
I have not been able to identify any relevant log entries when the problem occurs.
Any more info I can collect?
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
TL-WDR3600 : Gargoyle 1.9.0 : NBN FixedWireless
TL-WR1043ND-V2 : Gargoyle 1.8.0 : 3G Huawei E160E
Re: Version 1.7.2
Successfully installed 1.7.2 on a WDR4300 along with the Tor plugin and everything works perfectly! Kudos for a great job.
However, the Tor package in the plugin is version 0.2.5.10 from October 2014. It has been superseded by three stables versions since then: 0.2.5.11, 0.2.5.12 and the latest stable 0.2.6.10. (See https://dist.torproject.org)
Can the plugin be updated to the latest Tor, 0.2.6.10?
Or is this something that we, as users, can do manually by ourselves?
No one likes to run old/outdated/insecure packages on this brand-spanking new Gargoyle.
However, the Tor package in the plugin is version 0.2.5.10 from October 2014. It has been superseded by three stables versions since then: 0.2.5.11, 0.2.5.12 and the latest stable 0.2.6.10. (See https://dist.torproject.org)
Can the plugin be updated to the latest Tor, 0.2.6.10?
Or is this something that we, as users, can do manually by ourselves?
No one likes to run old/outdated/insecure packages on this brand-spanking new Gargoyle.
Re: Version 1.7.2
Just a report on 1.7.2
I upgraded from 1.7.1 to 1.7.2 on my TP-Link TL-WR1043N/ND v1
I tried to keep the system settings, and that seemed to causing instability as the router would reboot every minute. I went back to 1.7.1 and reflashed not keeping the system settings, and everything seems to be working well.
I upgraded from 1.7.1 to 1.7.2 on my TP-Link TL-WR1043N/ND v1
I tried to keep the system settings, and that seemed to causing instability as the router would reboot every minute. I went back to 1.7.1 and reflashed not keeping the system settings, and everything seems to be working well.
Re: Version 1.7.2
Yes. I did it. The only gotcha was that it was very unstable when I tried to preserve system settings, so it would be better to do backup/restore of system settings and not to try to preserve the settings.jachsz wrote:Any one upgraded to 1.7.2 to TP-Link TL-WR1043N/ND V1. Any problem expected?
Other than that everything is nice.
Re: Version 1.7.2
I'm going to update the first post to recommend people don't preserve settings. I did mention this but it's obviously being missed.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.
Re: Version 1.7.2
QMI support still seems to be broken, but I got it working after these two fixes:
In cache_basic_vars.sh the line
should be be
The file /utility/scan_qmidevices.sh is still missing, so scanning for QMI devices doesn't work at all on the Connection -> Basic page. In my case it should output /dev/cdc-wdm0. When I enter that manually as the device, I get a working LTE connection.
In cache_basic_vars.sh the line
Code: Select all
echo "qmiInterface=\"$qmi_if\";"
Code: Select all
echo "qmiInterface=\"$qmi_if\";" >> "$out_file"