Welcome, Guest. Please login or register.
Did you miss your activation email?
Sunday 01 December 2024, 03:15:20 am

Login with username, password and session length

Download the latest community FREE version  HERE
14261 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  EFW 2.4 QoS not working?
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: EFW 2.4 QoS not working?  (Read 9724 times)
pnacci
Jr. Member
*
Offline Offline

Posts: 7


« on: Monday 01 November 2010, 06:54:48 am »

I tried to configure QOS (with bandwidth, classes, and services) but it's not working at all.
Restarting QoS with restartqos.py the output is this:

2010-10-31 20:47:08,089 - restartqos.py[21482] - INFO - Loading configuration
2010-10-31 20:47:08,267 - restartqos.py[21482] - INFO - Setting QOS of device: eth3 [UPLOAD=20480, DOWNLOAD=20480]
2010-10-31 20:47:09,332 - restartqos.py[21482] - INFO - Setting QOS of device: eth4 [UPLOAD=2048, DOWNLOAD=2048]
2010-10-31 20:47:10,352 - restartqos.py[21482] - INFO - Setting QOS of device: tap1 [UPLOAD=4096, DOWNLOAD=4096]
2010-10-31 20:47:10,634 - restartqos.py[21482] - ERROR - RETURNCODE [ip link set dev ifb2 up] 255
2010-10-31 20:47:10,768 - restartqos.py[21482] - ERROR - RETURNCODE [tc filter add dev tap1 parent ffff: protocol ip u32 match u32 0 0 flowid 5:1 action mirred egress redirect dev ifb2 > /dev/null 2>&1] 1
2010-10-31 20:47:10,879 - restartqos.py[21482] - ERROR - RETURNCODE [tc qdisc add dev ifb2 root handle 5: htb default 2] 1
2010-10-31 20:47:10,941 - restartqos.py[21482] - ERROR - RETURNCODE [tc class add dev ifb2 parent 5: classid 5:1 htb rate 3932kbit ceil 3932kbit] 1
2010-10-31 20:47:11,001 - restartqos.py[21482] - ERROR - RETURNCODE [tc class add dev ifb2 parent 5:1 classid 5:2 htb rate 3932kbit ceil 3932kbit prio 0] 1
2010-10-31 20:47:11,056 - restartqos.py[21482] - ERROR - RETURNCODE [tc qdisc add dev ifb2 parent 5:2 handle 502: sfq perturb 10 ] 1


A bug? Any suggestion?
 Huh
Logged
pnacci
Jr. Member
*
Offline Offline

Posts: 7


« Reply #1 on: Tuesday 02 November 2010, 12:07:20 pm »

Problem is with TAP interface (OpenVPN lan2lan)  Angry
There is no ifb device linked to tap1 so restartqos fails.
I need to set qos for vpn tunnel (VoIP traffic): is there another way to ensure priority for VoIP packets?
Logged
pnacci
Jr. Member
*
Offline Offline

Posts: 7


« Reply #2 on: Saturday 06 November 2010, 09:12:07 am »

Solved!

Default number of ifb devices is 2, and I had 3 qos devices (green, red, vpn).
If you have more than 2 QoS devices you have to modify /etc/modprobe.conf and add a line:

options ifb numifbs=X (where X is the number of qos devices you need)

Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.066 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com