gargoyle-ispy 2015-May-28 15:49.torrent

[ispyisail]

USE AT YOUR OWN RISK

gargoyle-ispy 2015-May-28 15:49.torrent
https://goo.gl/iNYMbk

Mirror
http://goo.gl/VN1hTc

Supported routers
https://goo.gl/5rE7Dz

Fix another bug with QMI pointed out by tanemann on the forum, devnames=>

[simono_pl]

Thanks, downloading now

[scrmtrey]

Working ok, no problem so far (1 day of usage).

What i notice is that this firmware (general openwrt) slows down wifi a bit, not with speed or something. But page loading and stuff.

On stock is quick with no delay. Here is a little delay before page is showing up.


Maybe because of QOS.

[simono_pl]

From previous build sometimes I can't connect to Gargoyle GUI. Connection to router via ssh works without any problem. Seems GUI consumes sometimes too much RAM.
I have switched WiFi off on router. I olny use QOS, firewall rules, etc, vpn off, I don't use samba or ftp server on router.

This is what I see when I cannot connect to GUI:
total used free shared buffers
Mem: 28952 27316 1636 0 1996
-/+ buffers: 25320 3632
Swap: 0 0 0

When I restart process uhttpd I again can access GUI.

After restart uhttpd
total used free shared buffers
Mem: 28952 25756 3196 0 1380
-/+ buffers: 24376 4576
Swap: 0 0 0

[Lantis]

I have experienced that once.
I recall that I checked and uhttpd wasn't actually running at all!
Once I started it everything was ok.

Did you check if it was actually running?

[Rog66]

I've had the same on a few recent builds on a wdr4300 - I've had to restart uhttpd to gain access to the GUI .

[simono_pl]

I have experienced that once.
I recall that I checked and uhttpd wasn't actually running at all!
Once I started it everything was ok.

Did you check if it was actually running?

No I didn't check. When this will appear again I will check.

[simono_pl]

Ones again I can't access GUI. How can I check if uhttpd is running?

[Lantis]

i use "top" and look through the process list.

[nworbnhoj]

On Gargoyle 1.6.2 my GUI works fine but I do not see uhttpd using top or ps.

I do however see httpd_gargoyle

Has it changed in 1.7.x ?