Tom Eastep wrote:
> Fajar Priyanto wrote:
>> On Thursday 03 May 2007 05:51, Fajar Priyanto wrote:
>>> Hi all,
>>> I'm trying bandwidth management feature of shorewall-3.4.1-3 on Centos 4.4
>>> with no updates.
>>>
>>> I've checked the kernel conf (make menuconfig), that TC support for htb,
>>> sfq, e32, etc are modularized supported.
>>>
>>> I've checked that all these kernel modules are loaded:
>>> sch_prio                4545  0
>>> sch_sfq                 5313  0
>>> sch_ingress             4165  0
>>> sch_cbq                16449  0
>>> sch_htb                21953  0
>>> cls_fw                  4417  0
>>> cls_u32                 7493  0
>>>
>>> And that the tc command is compiled with htb and cbq support?
>>> [EMAIL PROTECTED] sched]# which tc
>>> /sbin/tc
>>> You have new mail in /var/spool/mail/root
>>> [EMAIL PROTECTED] sched]# strings /sbin/tc | grep htb
>>> htb2
>>> Usage: ... qdisc add ... htb [default N] [r2q N]
>>> ... class add ... htb rate R1 [burst B1] [mpu B] [overhead O]
>>> htb: failed to calculate ceil rate table.
>>> htb: failed to calculate rate table.
>>> htb_util
>>> htb2_util
>>>
>>> I follow the configuration from the howto:
>>> tcdevices:
>>> #INTERFACE      IN-BANDWITH     OUT-BANDWIDTH
>>> eth0            300kbps         64kbps
>>>
>>> tcclasses:
>>> #INTERFACE      MARK    RATE    CEIL    PRIORITY        OPTIONS
>>> eth0            1       full    full    1
>>> tcp-ack,tos-minimize-delay
>>> eth0            2       5kbps   15kbps  2
>>> eth0            3       2kbps   4kbps   3               default
>>>
>>> tcrules:
>>> 1:F     0.0.0.0/0       0.0.0.0/0       icmp    echo-request
>>> 1:F     0.0.0.0/0       0.0.0.0/0       icmp    echo-reply
>>> 1:F     10.0.0.1/24     0.0.0.0/0       all
>>> 2:F     10.0.0.4/24     0.0.0.0/0       all
>>>
>>> shorewall.conf:
>>> TC_ENABLE = Internal
>>>
>>> However, when I restart shorewall, I got this error:
>>>
>>> May  4 22:30:14 gateway shorewall: Setting up TC Rules...
>>> May  4 22:30:14 gateway shorewall: Setting up Traffic Control...
>>> May  4 22:30:14 gateway shorewall: Unknown qdisc "htb", hence option
>>> "default" is unparsable
>>> May  4 22:30:14 gateway shorewall:    ERROR: Command "tc qdisc add dev eth0
>>> root handle 1: htb default 13" Failed
>>> May  4 22:30:14 gateway shorewall:    WARNING: DISABLE_IPV6=Yes in
>>> shorewall.conf but this system does not appear to have ip6tables
>>> May  4 22:30:14 gateway shorewall: /sbin/shorewall: line 484: 11922
>>> Terminated $SHOREWALL_SHELL ${VARDIR}/.restart $debugging restart
>>> May  4 22:30:15 gateway shorewall: Processing /etc/shorewall/stop ...
>>> May  4 22:30:15 gateway shorewall: IP Forwarding Enabled
>>> May  4 22:30:15 gateway shorewall: Processing /etc/shorewall/stopped ...
>>> May  4 22:30:15 gateway shorewall: shorewall startup failed
>>>
>>> Has anyone experienced this?
>>> Any clues are appreciated. Thank you very much.
>> Anyone please?
> 
> Are you sure that your PATH is set so that Shorewall is using the same
> version of tc that you checked?
> 

The message you are getting seems to be an indication that tc itself doesn't
have htb support; witness this test:

[EMAIL PROTECTED]:~/shorewall-shell-3.9.4# tc qdisc add dev eth0  root handle 1:
foo default 13
Unknown qdisc "foo", hence option "default" is unparsable
[EMAIL PROTECTED]:~/shorewall-shell-3.9.4#

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ [EMAIL PROTECTED]
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to