Modify

Opened 11 years ago

Closed 8 years ago

Last modified 2 years ago

#1745 closed defect (wontfix)

qos script killing all traffic

Reported by: anonymous Owned by: developers
Priority: normal Milestone: 0.9/rc6
Component: packages Version:
Keywords: Cc: rob@…

Description

After upgrading the qos-scripts on my (x-wrt) white russian to 1.1.1-1, after some hours/days of running, all traffic is almost completely killed.
I have upload and download ratios on bulk channels of about 0.01 kb/s, and normal traffic also gets degraded down to a tenth.

This stops once I disable qos (but comes back after).

I also experience the following warning when en-/disabling qos (just before the failure disappears):
RED: WARNING. Burst 2 seems to be to large.

Attachments (0)

Change History (9)

comment:1 Changed 11 years ago by denis

Hello

I noted a problem with qos-script and wifidog when I install qos-script on my access point qos-script blocks the accesses has certain port which functioned before without qos.

I do not know if it is a dependent problem has wifidog or with qos-script

thank

PS: I tested with the version 0.9.4-1 and 1.1.0.1 (revision 6947) of qos-script

denis

comment:2 Changed 11 years ago by nbd

  • Resolution set to fixed
  • Status changed from new to closed

fixed in [7783]

comment:3 Changed 11 years ago by anonymous

  • Resolution fixed deleted
  • Status changed from closed to reopened

hello

I come from compiled the last version of qos-script. When I manually launch the s50qos I have this message

root@openwrt:/etc/init.d# /etc/init.d/S50qos
/etc/config/qos: 1: config_get_bool: not found
root@openwrt:/etc/config#

I does not know if it's a bug

thank

comment:4 Changed 11 years ago by nbd

  • Resolution set to fixed
  • Status changed from reopened to closed

added in [7808], thanks

comment:5 Changed 11 years ago by denis

  • Resolution fixed deleted
  • Status changed from closed to reopened

hello

I always have the same problem with version qos-script 1.2.0 and wifidog. Only the port informed in validating-users (wifidog.conf) function. The additional ports added in validating-users (wifidog.conf) does not function if qos active.

I do not know if it is a dependent problem has wifidog or with qos-script.

Denis

comment:6 Changed 11 years ago by nbd

could it be that wifidog messes with the netfilter mangle table?

comment:7 Changed 11 years ago by denis

I don't know.

I also posted a ticket on the trac of the wifidog project because it would be really although these two application can functioned together.

http://dev.wifidog.org/ticket/351#comment:2

still thank you for your work ndb

comment:8 Changed 11 years ago by denis

I did not test with kamikaze but I think that the problem must be similar.

comment:9 Changed 8 years ago by nbd

  • Resolution set to wontfix
  • Status changed from reopened to closed

0.9 is unmaintained, closing.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.