QoS (Download)Active Congestion Control Firmware v1.3.5

[stilllearning]

Hi All,

This is a New Feature which has been added to Gargoyle Version 1.3.5, to get a better understanding of how it works I would appreciate and explanation on the following.

Congestion Control Status

State:

Link limit:

Fair Link limit:

Link load:

Ping:

Filtered ping:

Ping time limit:

Classes Active:

The reason for this question is that it is unique, and is an excellent feature which works very well.

Cheers

[pbix]

Did you expand the "more info" tag just below this section? It has specifics on the meaning of these fields.

Also you can read
http://www.gargoyle-router.com/phpbb/vi ... =754#p3659


Take a look and post back any other questions you might have.

[pbix]

If any of you Gargoyle users have tried to use this feature please drop a post here to let me know how it went.

[elyask87]

I am currently using the new QoS feature on my WRT54GL and so far I am really impressed! However I think I might be experiencing some sort of bug maybe?

1. I get high CPU usage by "qosmon" (usually 70%+), load average over 1.3 whether or not there is traffic going through the router. Assuming I reboot the router, the load may or may not be high while qosmon is active (its random).

2. Turning off the new QoS feature doesn't seem to turn off qosmon. I can still see it running when I check "top". Load similar to above when it is "off". It shows disabled inside the status section.

3. I do not always get the information under "Congestion Control Status" when it is on. I have to turn it off and on again to get information in that section.

4. If I change the IP address inside the "non-standard ping target", I get 2 qosmon processes running, one with the old IP and another with the new IP entered.

I have tried reflashing and resetting the configuration, but the issues above persist. I worked around 1,2 and 4 by killing any qosmon process and enabling the feature once again in the QoS section.

Other than the issues above it is working great at managing my rules .

[pbix]

Well none of the things you reported should be happening. After I saw your report I investigate both things on my WRT54G-TM. I cannot reproduce either of these so that a little frustrating for me.

The QOS script runs "killall qosmon" when QOS is stopped or restarted. This should kill all qosmon processes. When qosmon is running try running that from the command line and see if you get any messages. Check to make sure it kills the process. What are you using to kill qosmon when you do it?

The CPU load used by qosmon is extremely small as it sleeps most of the time. There is no situation in which it would cause a 70% CPU itself. Did you use top to determine this? I use htop which you can get by doing an "opkg update" & "opkg install htop" because top does not even show sleeping process so often it does not show qosmon. Does htop show that qosmon is using 70% of the CPU all the time or only in special circumstances?

I appreciate your feedback.

[elyask87]

Thanks for checking out the problems.

I killed qosmon by running "kill -9 pid". I just did a "killall qosmon" and qosmon was gone when I did a ps. So the kill script should have been working I guess.

Once doing the above I have installed htop and enabled the feature once again from the web interface. Top and htop show qosmon using 0% CPU and just a bit of memory (the stability that should be expected). Note that I had previously killed qosmon earlier in order to work around the problem, so this instance of qosmon was a good one.

I rebooted my router and left it running (no network traffic) for a while to stabilize, and the load was high. htop shows qosmon using 96% cpu. I visit the download QoS page and it shows nothing under congestion control status, but it is ticked along with the IP address I had entered to use for pings.

I unticked the box to disable congestion control, but qosmon continues to run. Running "killall qosmon" this time has no effect, qosmon continues to run. I used kill -9 to stop qosmon, ticked the box to re-activate and it works as it should now: no high cpu usage and information shown in the status section.

I am guessing something is happening as the router is booting that is causing this issue.

[pbix]

So it seems this happens only at boot time. Interesting input and gives me a hint of where to look. If you see something to the contrary let me know.

Can you tell me about your setup. What kind of WAN connection do you have?

That part might be different than mine.

[elyask87]

My connection is WiMAX, setup is something like this:

Motorola CPEi750 (WiMAX modem/router) <---> WRT54GL v1.1 <---> Devices on my network.

In this setup I suffer from double NAT, the Motorola is also a router (nothing can be done until Motorola and my ISP decide to allow disabling NAT in the settings). So I have TCP/UDP ports 1-65535 forwarded from the Motorola to the WRT, so the WRT handles forwarding to devices on my network.

The WRT's WAN IP is a private IP address in the Motorola's range (192.168.15.x). My ISP assigns the Motorola a public IP, so I use my ISP's gateway IP in the congestion control section (a public IP). I get assigned a static IP so the gateway doesn't change if I lose sync/disconnect.

I did not notice any noticeable QoS performance degradation, if any, when qosmon was running in high or normal CPU usage. I actually thought it was normal for the high load and left it running that way for days before deciding to investigate it further.

[pbix]

elyask87,

I have created a special test version of qosmon and attached it. If you could please uncompress it and replace the file of the same name in /usr/sbin on your WRT54GL.

Then see if you can reproduce the situation you describe. While qosmon is taking the 70% CPU time copy the file /tmp/qosmon.status and send it to me at pbix@bigfoot.com

This I hope will give me a clue as to where exactly qosmon is getting hung up.

[elyask87]

Just put in the new qosmon file and rebooted my router, qosmon started using high CPU again. I checked out qosmon.status in /tmp and these are the only lines inside (as shown by cat and vi):

Checking Args
Begin inet_addr
getprotobyname
open socket
tc_core_init
check for imq0
daemonize

I was expecting more numbers !

I will keep it running for a while this way and check if anything else comes up in the file.