Gargoyle Forum

Posted: **Sun Aug 01, 2010 3:49 pm**

No trouble.
I noticed I couldn't disable the " Enable active congestions control (Download Direction) " as when I unticked the checkbox and hit save changes it automatically ticked itself again.

Idle:

Code: Select all

root@router:/# cat /tmp/qosmon.status 
State: WAIT
Link limit: 900 (kbps)
Fair Link limit: 900 (kbps)
Link load: 0 (kbps)
Ping: off
Filtered ping: 0 (ms)
Ping time limit: 0 (ms)
ID FFFF, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14304518239131261772, work: 14304518239131261772
ID 801B, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14304518239131261772, work: 14304518239131261772
ID 801C, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 16374847, xbytes: 14304518239131261772, work: 14304518239131261772
ID 801D, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14304518239131261772, work: 14304518239131261772

Load (1 download):

Code: Select all

root@router:/# cat /tmp/qosmon.status 
State: WAIT
Link limit: 900 (kbps)
Fair Link limit: 900 (kbps)
Link load: 0 (kbps)
Ping: off
Filtered ping: 0 (ms)
Ping time limit: 0 (ms)
ID FFFF, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14304518239131261772, work: 14304518239131261772
ID 801B, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14304518239131261772, work: 14304518239131261772
ID 801C, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 2800495, xbytes: 14304518239131261772, work: 14304518239131261772
ID 801D, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14304518239131261772, work: 14304518239131261772
2

Load: 2 downloads:

Code: Select all

root@router:/# cat /tmp/qosmon.status 
State: WAIT
Link limit: 900 (kbps)
Fair Link limit: 900 (kbps)
Link load: 0 (kbps)
Ping: off
Filtered ping: 0 (ms)
Ping time limit: 0 (ms)
ID FFFF, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14304518239131261772, work: 14304518239131261772
ID 801B, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14304518239131261772, work: 14304518239131261772
ID 801C, Active , Backlog       , BW bps (filtered): 0.00     
nbytes: 13715669, xbytes: 14304518239131261772, work: 14304518239131261772
ID 801D, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14304518239131261772, work: 14304518239131261772

Posted: **Sun Aug 01, 2010 3:55 pm**

After reboot:

Idle:

Code: Select all

State: WAIT
Link limit: 863 (kbps)
Fair Link limit: 863 (kbps)
Link load: 0 (kbps)
Ping: off
Filtered ping: 0 (ms)
Ping time limit: 0 (ms)
ID FFFF, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14353318963229834060, work: 14353318963229834060
ID 8004, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14353318963229834060, work: 14353318963229834060
ID 8005, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 588311, xbytes: 14353318963229834060, work: 14353318963229834060
ID 8006, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14353318963229834060, work: 14353318963229834060
0

Load (1)

Code: Select all

State: WAIT
Link limit: 863 (kbps)
Fair Link limit: 863 (kbps)
Link load: 0 (kbps)
Ping: off
Filtered ping: 0 (ms)
Ping time limit: 0 (ms)
ID FFFF, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14353318963229834060, work: 14353318963229834060
ID 8004, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14353318963229834060, work: 14353318963229834060
ID 8005, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 3754963, xbytes: 14353318963229834060, work: 14353318963229834060
ID 8006, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14353318963229834060, work: 14353318963229834060

Load (2):

Code: Select all

State: WAIT
Link limit: 863 (kbps)
Fair Link limit: 863 (kbps)
Link load: 0 (kbps)
Ping: off
Filtered ping: 0 (ms)
Ping time limit: 0 (ms)
ID FFFF, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14353318963229834060, work: 14353318963229834060
ID 8004, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14353318963229834060, work: 14353318963229834060
ID 8005, Active , Backlog 
                          , BW bps (filtered): 0.00     
nbytes: 8076580, xbytes: 14353318963229834060, work: 14353318963229834060
ID 8006, Active , Backlog , BW bps (filtered): 0.00     
nbytes: 0, xbytes: 14353318963229834060, work: 14353318963229834060

Posted: **Sun Aug 01, 2010 8:14 pm**

Delpinus,

Give the attached a go. Seems the problem is related to using kernel v2.6 vs. v2.4 like I have. Hopefully this will fix it otherwise I will have to work on it some more this week.

Posted: **Sun Aug 01, 2010 8:37 pm**

thats working!

root@router:/tmp# cat qosmon.status
State: FREE
Link limit: 1000 (kbps)
Fair Link limit: 900 (kbps)
Link load: 867 (kbps)
Ping: off
Filtered ping: 0 (ms)
Ping time limit: 1 (ms)
Classes Active: 1
ID FFFF, Active 0, Backlog 0, BW bps (filtered): 0
ID 8015, Active 0, Backlog 0, BW bps (filtered): 0
ID 8016, Active 1, Backlog 0, BW bps (filtered): 867375
ID 8017, Active 0, Backlog 0, BW bps (filtered): 0

gotta duck out, will report more later

Posted: **Sun Aug 01, 2010 9:08 pm**

Well the bandwidth looks right but the ping limit does not.

Yesterday you had a ping limit of 54ms which is reasonable. Did you change the WAN setup? Why would the ping response in these tests be so fast?

Posted: **Sun Aug 01, 2010 10:03 pm**

You're right, that far too low.

What host does it actually ping?

Posted: **Mon Aug 02, 2010 7:11 am**

It pings your WAN gateway as shown on the Status screen.

Try the ping from the command line of your Linux box and your router and see what that reports.

Posted: **Mon Aug 02, 2010 2:40 pm**

I've made no WAN changes during this testing so not sure what it got the 43ms from originally.

1ms is accurate, I'm on a wireless connection, and the gateway I connect to is just across town.

Posted: **Mon Aug 02, 2010 4:45 pm**

That is really fast response. My link must really suck since its doesn't go faster than 25ms ever on this.

Run a test for me a start a ping to the gateway then simultaneously saturate your downlink by download a big file. What happens to the ping times?

Do this with QoS disabled.

Posted: **Mon Aug 02, 2010 10:17 pm**

Delpinus,

There is an assumption in this controller that a high ping time indicates congestion which can be eliminated by lowering the throughput of the WAN link. Hopefully this will hold true in your wireless LAN but we shall have to see.

One thing I can say is that a pinglimit of 1ms is not going to allow the controller to operate. Please try the attached alix-madwifi version by replacing the same in /usr/sbin. This version will enforce a minimum pinglimit of 35ms regardless of what the controller measures at initialization. This should give the controller a chance to work.

I will look forward to your report.

Gargoyle Forum

QoS the next generation

Re: QoS the next generation

Re: QoS the next generation

Re: QoS the next generation

Re: QoS the next generation

Re: QoS the next generation

Re: QoS the next generation

Re: QoS the next generation

Re: QoS the next generation

Re: QoS the next generation

Re: QoS the next generation