Page 1 of 2

1.11.0.x gargoyle-ispy 2019-April-26 20

Posted: Sun Apr 28, 2019 2:37 am
by ispyisail
USE AT YOUR OWN RISK

WARNING: DO NOT PRESERVE SETTINGS

Now includes packages

Do not install on 4MB routers

1.11.0.x gargoyle-ispy 2019-April-26 20.torrent
Torrent
http://bit.ly/2UNTQTT

magnet:?xt=urn:btih:11b3538925d771f26522bf18320af8bc3f47c61a&dn=1.11.0.x%20gargoyle-ispy%202019-April-26%2020.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/2IO5BZc



Changelog
(see creation date for commit date)

https://github.com/ericpaulbishop/gargo ... its/master

Re: 1.11.0.x gargoyle-ispy 2019-April-26 20

Posted: Mon Apr 29, 2019 11:36 am
by JohnPeterson
Linksys WRT1900AC - working great - upgraded from last ispy

Re: 1.11.0.x gargoyle-ispy 2019-April-26 20

Posted: Tue Apr 30, 2019 5:10 pm
by CBx86
Im receiving some ipt_bandwidth crazy timezone and sh while in Bandwidth Usage.

Code: Select all

Tue Apr 30 17:12:12 2019 kern.warn kernel: [10268.172078] ipt_bandwidth: timezone shift of 180 minutes detected, adjusting
Tue Apr 30 17:12:12 2019 kern.warn kernel: [10268.179262]                old minutes west=180, new minutes west=0
Tue Apr 30 17:12:13 2019 kern.warn kernel: [10269.172275] ipt_bandwidth: timezone shift of 180 minutes detected, adjusting
Tue Apr 30 17:12:13 2019 kern.warn kernel: [10269.179452]                old minutes west=0, new minutes west=180
Tue Apr 30 17:12:32 2019 kern.warn kernel: [10288.170329] ipt_bandwidth: timezone shift of 180 minutes detected, adjusting
Tue Apr 30 17:12:32 2019 kern.warn kernel: [10288.177490]                old minutes west=180, new minutes west=0
Tue Apr 30 17:12:33 2019 kern.warn kernel: [10289.188172] ipt_bandwidth: timezone shift of 180 minutes detected, adjusting
Tue Apr 30 17:12:33 2019 kern.warn kernel: [10289.195376]                old minutes west=0, new minutes west=180
Tue Apr 30 17:16:50 2019 kern.warn kernel: [10546.177661] ipt_bandwidth: timezone shift of 180 minutes detected, adjusting
Tue Apr 30 17:16:50 2019 kern.warn kernel: [10546.184846]                old minutes west=180, new minutes west=0
Tue Apr 30 17:16:51 2019 kern.warn kernel: [10547.177667] ipt_bandwidth: timezone shift of 180 minutes detected, adjusting
Tue Apr 30 17:16:51 2019 kern.warn kernel: [10547.184850]                old minutes west=0, new minutes west=180
Tue Apr 30 17:19:57 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:19:57 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:19:57 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:19:57 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:19:58 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:19:58 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:19:58 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:19:58 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:20:04 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:20:04 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:20:04 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:20:04 2019 daemon.err uhttpd[19906]: sh: write error: Broken pipe
Tue Apr 30 17:34:14 2019 kern.warn kernel: [11590.166763] ipt_bandwidth: timezone shift of 180 minutes detected, adjusting
Tue Apr 30 17:34:14 2019 kern.warn kernel: [11590.173947]                old minutes west=180, new minutes west=0
Tue Apr 30 17:34:15 2019 kern.warn kernel: [11591.203516] ipt_bandwidth: timezone shift of 180 minutes detected, adjusting
Tue Apr 30 17:34:15 2019 kern.warn kernel: [11591.210721]                old minutes west=0, new minutes west=180
Fresh install, not preserved config.

Re: 1.11.0.x gargoyle-ispy 2019-April-26 20

Posted: Tue Apr 30, 2019 5:22 pm
by Lantis
I’ll check the Timezone triggers. It’s intentional behaviour but it isn’t supposed to trigger that often.
It will only do this while on the bandwidth page. I’d recommend not sitting on that page for a long time at the moment. There’s a small risk it will corrupt the data I suppose.

The sh errors mean nothing.

Re: 1.11.0.x gargoyle-ispy 2019-April-26 20

Posted: Tue Apr 30, 2019 5:25 pm
by CBx86
Cheking i find my localtime symbolic is broken.
localtime -> /tmp/localtime
This is right? I dont remember.

The error 'sh' seems to happen more frequently with full load!

Re: 1.11.0.x gargoyle-ispy 2019-April-26 20

Posted: Tue Apr 30, 2019 5:28 pm
by Lantis
It’s happening because when it detects the Timezone shift it has to rewrite all of your bandwidth data to the new Timezone which takes a long time.
During this time the bandwidth module can’t read the bandwidth data so it errors (broken pipe).

Re: 1.11.0.x gargoyle-ispy 2019-April-26 20

Posted: Tue Apr 30, 2019 5:34 pm
by CBx86
Lantis, localtime -> /tmp/localtime is a broken symbolic ?

I reconfigured the TZ.

Re: 1.11.0.x gargoyle-ispy 2019-April-26 20

Posted: Tue Apr 30, 2019 5:58 pm
by Lantis
That should not matter.

Re: 1.11.0.x gargoyle-ispy 2019-April-26 20

Posted: Tue Apr 30, 2019 8:12 pm
by CBx86
You are right. :lol:

Re: 1.11.0.x gargoyle-ispy 2019-April-26 20

Posted: Wed May 01, 2019 6:18 am
by Lantis
Should be a bit better in the next version, sorry about that.
https://github.com/ericpaulbishop/gargo ... 235bda3d9d

Hopefully this one causes less issues (it should, it is much closer to the original code).