knetfilter is a iptables GUI, so support to QoS is limited just to cbq with firewall based packet classifier. Mainly it needs a lot of more tests, and users should very well know what they are going to do, but the GUI is stable and consistent :). All parameters are checked so that users are forced to supply them, but they must be fully coerent. The GUI pays a lot of attention if all parameters are fully coerent, but it may still make some mistake. Actually a lot of more stuff about QoS support has been developed inside of knetfilter, as, for example, the possibility to delete a class or a qdisc, and a monitor to see which qdiscs, classes and filters have been configured. They are all cool features, but probably a save function will not be developed for now. I am not complitelly sure that knetfilter 3.1 should keep QoS support, it will depend on feedbacks and contributions (really I need them). To access to traffic shaper GUI you have just to click on the "traffic shaper" voice inside of the menu "Options". If you have not installed iproute you will see nothing, since you will not see the "traffic shaper" voice inside any menu. Obviously Linux kernel has to be compiled with support for QoS enabled. Not all options are needed. Here is the correct configuration requested by knetfilter: # # QoS and/or fair queueing # CONFIG_NET_SCHED=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NET_SCH_CBQ=m # CONFIG_NET_SCH_CSZ is not set # CONFIG_NET_SCH_PRIO is not set # CONFIG_NET_SCH_RED is not set # CONFIG_NET_SCH_SFQ is not set # CONFIG_NET_SCH_TEQL is not set # CONFIG_NET_SCH_TBF is not set # CONFIG_NET_SCH_GRED is not set CONFIG_NET_SCH_DSMARK=m # CONFIG_NET_SCH_INGRESS is not set CONFIG_NET_QOS=y CONFIG_NET_ESTIMATOR=y CONFIG_NET_CLS=y # CONFIG_NET_CLS_TCINDEX is not set # CONFIG_NET_CLS_ROUTE4 is not set CONFIG_NET_CLS_FW=m # CONFIG_NET_CLS_U32 is not set # CONFIG_NET_CLS_RSVP is not set # CONFIG_NET_CLS_RSVP6 is not set # CONFIG_NET_CLS_POLICE is not set Thanx God, QoS modules can be loaded by kmod. So enjoy.
