Gargoyle 1.35 & Tp-Link TL-WR1043ND Bugs

[Mitar]

I discovered few bugs.

1) Web Usage : after some time it shows ips instead of hostnames also ips are writed wrong , for example instead of 192.168.0.2 it is writed 2.0.168.192

2) Connected hosts : sometimes displays some wierd ip ( only one ) with hostname: (unknown)

3) Connection - Basic : sometimes displays "Current Lease Expires" with wrong date (year 1970)

4) Connection - Wireless Mac filter : don't works , allows all MAC addresses to connect

5) System - Time : always when I set my timezone ( UTC+01:00 ), it shows UTC-08:00 on webpage as default picked , but Current Date & Time is correct

6) Backup / Restore : Backup works ok , but displays errors in log :

Code: Select all

mini_fo: nondir_unmod_to_mod: ERROR creating sto file.
mini_fo_setattr: ERROR changing states.

7) Update Firmware : Doesn't seems to work ? wanted to test DD-WRT , it was saying that firmware is uploading but nothing happened for long time , nothing in log , after rebooted router via reboot in web interface there was still Gargoyle on router

8) Opkg points at

Code: Select all

http://downloads.openwrt.org/backfire/10.03/ar71xx/packages/

, but when trying to install something it gives error :

Code: Select all

Not downgrading package kernel on root from 2.6.32.16-1 to 2.6.32.10-1.

Seems Opkg should look at

Code: Select all

http://downloads.openwrt.org/backfire/10.03.1-rc3/ar71xx/packages/

instead of this first.

9) Maybe not a bug but would like to have more wireless options via web interface like wireless modes ( n , g , ng)

Thats all I can see for now.
Anyway Gargoyle works very nice and most probably will stick with it

[Eric]

(1) and (5) were fixed a while ago. Are you SURE this was version 1.3.5???

I just tested again with ar71xx and 1.3.5, and this behavior does not show up.

(6) Isn't a bug unless the backup or restore fails. I don't care about log errors unless something isn't working.

(7) Is not a bug, because Gargoyle is only designed to be able to upgrade to either another version of Gargoyle or OpenWrt. If DD-WRT releases any OpenWrt compatible images, they will be supported, but only then.

(8) Is really an upstream issue. When it gets updated in OpenWrt backfire branch SVN it will get updated in Gargoyle.

[Mitar]

(1) and (5) were fixed a while ago. Are you SURE this was version 1.3.5???

yes it is 1.3.5 , not at beginning but after 4-5 hours it starts to show like that. (1)
and (5) is always showing like that.

[Xarlith]

I think there is another bug. I can't create new QoS rule using one of the layer7 protocols. Clicking on 'Apply rule' brungs up an following error message:

There is an error in Application (Layer7) Protocol
Could not add classification rule.

Same thing happens when I edit existing rule.

I hope you understood me. I'm still learning English .

[Mitar]

Stability unfortunely isn't good , it restarts every 12-20 Hours.
Just to compare , on WRT54GL with Tomato I had more than 30 days days uptime without any problems.

[Eric]

I've managed to find and fix (1), and (3)-(5) now. Fixes are committed to the source repository and will be included in the next release. You're right (1) and (5) were different from the bugs I caught before (but they should be fixed now).

I can't replicate (2).

I'm not sure what could be causing the instability you see. I've had this running on an ath9k device (wrt160nl) with no down time since I released 1.3.5. Could you elaborate further on your setup? I.e. what features/configuration are you using?

[Mitar]

So I found another bug .

10 ) Active Congestion Control hangs .
it have status : WAIT and link load is not changing , even when downloading something it shows old low value ( 17 kbps for me).
Maybe it was reason of unstable work ?
Anyway will test it.
Disabled it in morning and so far works stable - 14 hours uptime.

[elyask87]

I think there is another bug. I can't create new QoS rule using one of the layer7 protocols. Clicking on 'Apply rule' brungs up an following error message:

There is an error in Application (Layer7) Protocol
Could not add classification rule.

Same thing happens when I edit existing rule.

I hope you understood me. I'm still learning English .

I am also getting the above error when I try to add or edit a QoS rule using one of the L7 filters (on a WRT54GL v1.1). Strange thing is that when I first installed 1.3.5 I set up a few L7 rules successfully, then decided to drop them, and now can't add/modify L7 rules. I'm guessing that might be a way to reproduce.

[Xarlith]

I had this from the beginning.

[pbix]

Regarding the trouble adding L7 rules.

I think this is a bug introduced in v1.3.5. The attached should resolve the issue and I would appreciate if you could test it for me.

Please download and uncompress the attachment. Then replace the file of the same name in /www/js of the same name.

Let me know your results.