Christopher Holmes wrote:
>
> Is there any kind of QOS built into Dachstein? I noticed a fairq chain in
> the packet fileter rules.
# grep -i 'qos\|fairq' /etc/network.conf
# Simple QoS/fair queueing support
eth0_FAIRQ=NO
# Complex QoS - Enable all of these + above to turn it on
eth1_FAIRQ=NO
#eth2_FAIRQ=NO
# Simple QoS support
#fr498_FAIRQ=YES
# Complex FR QoS - Enable ALL of these + above to turn it on
#ppp_FAIRQ=YES
# fairq chain
CLS_FAIRQ="${MRK_CRIT}_89_0/0 ${MRK_CRIT}_udp_0/0_route
${MRK_CRIT}_tcp_0/0_bgp ${MRK_CRIT}_tcp_0/0_domain
${MRK_CRIT}_udp_0/0_domain ${MRK_IA}_tcp_0/0_telnet
${MRK_IA}_tcp_0/0_ssh"
eval local FAIRQ=\${"$1"_FAIRQ:-""}
ip_frQoS $1
ip_QoS $1
# Clean up any QoS/fair queuing stuff
ip_QoSclear $1
# QoS/Fariqueing functions
ip_QoSclear () {
ip_frQoS () {
eval local FAIRQ=\${"$1"_FAIRQ:-""}
if [ "$FAIRQ" != "YES" -a "$FAIRQ" != "Yes" -a "$FAIRQ" != "yes"
]
ip_QoS () {
eval local FAIRQ=\${"$1"_FAIRQ:-""}
if [ -z "$FAIRQ" -a -n "$2" ]; then
local FAIRQ=$2
if [ "$FAIRQ" != "YES" -a "$FAIRQ" != "Yes" -a "$FAIRQ" != "yes"
]
--
Best Regards,
mds
mds resource
888.250.3987
Dare to fix things before they break . . .
Our capacity for understanding is inversely proportional to how much we
think we know. The more I know, the more I know I don't know . . .
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
