1.12.0.x gargoyle-ispy 2020-March-02 06
Moderator: Moderators
1.12.0.x gargoyle-ispy 2020-March-02 06
USE AT YOUR OWN RISK
WARNING: DO NOT PRESERVE SETTINGS
Now includes packages
1.12.0.x gargoyle-ispy 2020-March-02 06
Torrent
http://bit.ly/2VCnP5w
magnet:?xt=urn:btih:c4cbaeb90543d0ee2bdd84b8b008d6a03280414c&dn=1.12.0.x%20gargoyle-ispy%202020-March-02%2006.7z&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80&tr=udp%3a%2f%2fopen.demonii.com%3a1337&tr=udp%3a%2f%2ftracker.coppersurfer.tk%3a6969&tr=udp%3a%2f%2ftracker.leechers-paradise.org%3a6969&tr=udp%3a%2f%2ftracker.coppersurfer.tk%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.open-internet.nl%3a6969%2fannounce&tr=udp%3a%2f%2fallesanddro.de%3a1337%2fannounce&tr=udp%3a%2f%2f9.rarbg.to%3a2710%2fannounce
Routers
http://bit.ly/2IdF1Gw
Changelog
(see creation date for commit date)
https://github.com/ericpaulbishop/gargoyle/commits/1.12
WARNING: DO NOT PRESERVE SETTINGS
Now includes packages
1.12.0.x gargoyle-ispy 2020-March-02 06
Torrent
http://bit.ly/2VCnP5w
magnet:?xt=urn:btih:c4cbaeb90543d0ee2bdd84b8b008d6a03280414c&dn=1.12.0.x%20gargoyle-ispy%202020-March-02%2006.7z&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80&tr=udp%3a%2f%2fopen.demonii.com%3a1337&tr=udp%3a%2f%2ftracker.coppersurfer.tk%3a6969&tr=udp%3a%2f%2ftracker.leechers-paradise.org%3a6969&tr=udp%3a%2f%2ftracker.coppersurfer.tk%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.open-internet.nl%3a6969%2fannounce&tr=udp%3a%2f%2fallesanddro.de%3a1337%2fannounce&tr=udp%3a%2f%2f9.rarbg.to%3a2710%2fannounce
Routers
http://bit.ly/2IdF1Gw
Changelog
(see creation date for commit date)
https://github.com/ericpaulbishop/gargoyle/commits/1.12
Re: 1.12.0.x gargoyle-ispy 2020-March-02 06
Installed on a (previously) spare TL-WR1043ND V1, running as AP and wireless repeater. No problems so far.
Seeding the torrent, too
Seeding the torrent, too

Re: 1.12.0.x gargoyle-ispy 2020-March-02 06
I have a few reboots with this build, not sure what causing them. I can't see anything in the logs (for now).
WRT 1200ac
WRT 1200ac
Re: 1.12.0.x gargoyle-ispy 2020-March-02 06
Uptime: 17 days, 14 hours, 11 minutes
So no, mine is stable. But it's being used as Wireless Repeater only, so it has very minor load.
So no, mine is stable. But it's being used as Wireless Repeater only, so it has very minor load.
Re: 1.12.0.x gargoyle-ispy 2020-March-02 06
Just did an update to this latest one and noticed a couple of curiosities (btw, I did an upgrade but did NOT preserve settings)
Router is Archer C7 V2:
Router is Archer C7 V2:
- Wifi works fine but the activity leds no longer display
- When I turned on QoS Download I noticed that the Congestion Control Status is blank. I remember in past releases it did show some info
Paul
Gargoyle 1.11.x on TP-Link Archer C7 V2 H/W
Gargoyle 1.11.x on TP-Link Archer C7 V2 H/W
Re: 1.12.0.x gargoyle-ispy 2020-March-02 06
Saving QOS again should fix the congestion control status being blank.
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: 1.12.0.x gargoyle-ispy 2020-March-02 06
Hey Lantis, thanks for the suggestion but no luck. I've enabled, disabled, tried different browsers no luck. I'm an old Unix/ASM hack so I can login to the router via root was wondering if there is anything I can check in /etc that may indicate a problem?
It's also strange that while wifi works fine, the leds on the router no longer display activity. Is there some file I can check in /etc to see if there is a setting problem?
My only other approach is to do a backup, re-flash and then a restore and see if that "fixes" it.
Very strange to me.
Paul
Gargoyle 1.11.x on TP-Link Archer C7 V2 H/W
Gargoyle 1.11.x on TP-Link Archer C7 V2 H/W
Re: 1.12.0.x gargoyle-ispy 2020-March-02 06
Those stats not showing up are usually accompanied by log entries along the lines of "device IMQ0 does not exist"
Which indicates that the IMQ driver failed to start correctly.
Usually saving QOS again causes it to restart and therefore attempt to reinsert the driver.
I need to put some try, wait, fail code around the IMQ driver but I don't have a reliable way of making it fail to load so I can't test it.
Which indicates that the IMQ driver failed to start correctly.
Usually saving QOS again causes it to restart and therefore attempt to reinsert the driver.
I need to put some try, wait, fail code around the IMQ driver but I don't have a reliable way of making it fail to load so I can't test it.
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.