Gargoyle Forum

Hi,
This is a problem I experience UPNP, earlier I tested the problem - unfortunately, not solved. Tested devices: TL-WR1043ND V1 = problem, TL-WR1043ND V2 = no problem. The error is also in OpenWRT BB
viewtopic.php?f=3&t=6557&p=26911

Hello, small problem, a) only when the system upgrade file /etc/banner does not change and b) is not included in the backup file. When restoring from a backup file, the file /etc/banner does not change. If I may suggest a change of touch /etc/banner to touch /etc/crontabs/root (this file is included...

Thank you for the new build, very good.

Thank you for the correction and also congratulations ispyisail and waiting for more router images.

Hi,
time and date - the error still persists, I expect sometime after shutdown reboot loop (time in /usr/data/wbmon/ are newer than those in /etc) .

Roman

Dear Roman Jesteś z Polski? ;) Yes, I am connected to UPC in Poland with 250/20Mbps and I have said with Gargoyle 1.6.2 I have got c.a. 250/20Mbps without any problems, but with Gargoyle 1.7.1 only 125/20Mbps. When I disable BWMon from ssh, then I have 185/20Mbps. I wish I have 250/20Mbps with 1.7....

Dear Friends TL-WR1043ND v.2 with 1.7.1 is working without any problems, but... ...bandwidth is decreased by half (50%) comapring to version 1.6.2. I have got (via ethernet cable) 250/20Mbps with 1.6.2, but with 1.7.1 only 125/20Mbps (via ethernet cable). When I type in ssh: /etc/init.d/bwmon_gargo...

Hi all,
Reboot loop news:
I tested it and it has something to do with the date and time. Data /usr/data/bwmon/* not damaged. My temporary modification (sysfixtime) works. You may need to fine-tune the script.

Roman

In that case, I have tried to adjust the script (/etc/init.d/sysfixtime) as follows (8th line): #!/bin/sh /etc/rc.common # Copyright (C) 2013-2014 OpenWrt.org START=00 boot() { local curtime="$(date +%s)" local maxtime="$(find /usr/data -type f -exec date -r {} +%s \; | sort -nr | hea...

Info for all us beginners, and sort of checking if this ok. As I am using the router with 1.7.1 in a production environment, (That is, me using this as my primary router for work), it is not good to have the system go into an endless loop. Here is how I have implemented a TEMPORARY workaround. I ha...