All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Heinz <josef.k@mytomorrow.de>
To: lartc@vger.kernel.org
Subject: [LARTC] htb causes roaring penguin's pppoe daemon to terminate connection
Date: Sat, 09 Feb 2002 19:07:06 +0000	[thread overview]
Message-ID: <marc-lartc-101328197705968@msgid-missing> (raw)

Hi

I know, the subject sounds quite strange. Well, here is the situation.

I'm using 2.4.17 with the htb patch and the latest h323 patch from the
netfilter cvs. I've been using htb and h323 on 2.4.16 and never experienced
any problems but with 2.4.17 the pppoe daemon from roaring penguin that
I'm using sometimes terminates with the error message:
pppoe[pid]: send (sendPacket): No buffer space available

This situation arises when my upstream is full. When I flush the htb rules
everything's fine.

Maybe someone experienced the same problem or can give me a hint what
I should try to eliminate the problem.

Thank you for your interest.


Thomas

Here is my htb script (based on the howto):


#!/bin/bash

DOWNLINKv5
UPLINK\x125
DEV=ppp0
PHYS=eth1 # underlying physical device

ifconfig $DEV txqueuelen 200
ifconfig $PHYS txqueuelen 2

tc qdisc del dev $DEV root    > /dev/null 2>&1
tc qdisc del dev $DEV ingress > /dev/null 2>&1

# some shortcuts
ADDQDISC="tc qdisc add dev $DEV"
ADDCLASS="tc class add dev $DEV"
ADDFILTER="tc filter add dev $DEV"

########## uplink #############

$ADDQDISC root handle 1: htb default 900

$ADDCLASS parent 1: classid 1:1 htb rate ${UPLINK}kbit burst 1540

   $ADDCLASS parent 1:1 classid 1:10 htb rate 40kbit ceil 100kbit burst 1540  \
   prio 1
     $ADDCLASS parent 1:10 classid 1:100 htb rate 20kbit ceil 100kbit \
     burst 1540 prio 1
     $ADDCLASS parent 1:10 classid 1:200 htb rate 20kbit ceil 100kbit \
     burst 1540 prio 2

   $ADDCLASS parent 1:1 classid 1:30 htb rate 15kbit ceil ${UPLINK}kbit \
   burst 1540 prio 2

   $ADDCLASS parent 1:1 classid 1:40 htb rate 70kbit ceil ${UPLINK}kbit \
   burst 1540 prio 3
      $ADDCLASS parent 1:40 classid 1:800 htb rate 40kbit ceil ${UPLINK}kbit \
      burst 1540 prio 1
      $ADDCLASS parent 1:40 classid 1:900 htb rate 30kbit ceil ${UPLINK}kbit \
      burst 1540 prio 2


# all get Stochastic Fairness except icmp/tos traffic
$ADDQDISC parent 1:100 handle 100: sfq perturb 10
$ADDQDISC parent 1:200 handle 200: sfq perturb 10
$ADDQDISC parent 1:30 handle 30: pfifo limit 5
$ADDQDISC parent 1:800 handle 800: sfq perturb 10
$ADDQDISC parent 1:900 handle 900: sfq perturb 10

$ADDFILTER parent 1:0 protocol ip prio 1 handle 1 fw flowid 1:100
$ADDFILTER parent 1:0 protocol ip prio 2 handle 2 fw flowid 1:200
$ADDFILTER parent 1:0 protocol ip prio 3 u32 match ip tos 0x10 0xff flowid 1:30
$ADDFILTER parent 1:0 protocol ip prio 3 u32 match ip protocol 1 0xff \
  flowid 1:30

$ADDFILTER parent 1:0 protocol ip prio 3 u32 \
    match ip protocol 6 0xff \
    match u8 0x05 0x0f at 0 \
    match u16 0x0000 0xffc0 at 2 \
    match u8 0x10 0xff at 33 \
    flowid 1:30

$ADDFILTER parent 1:0 protocol ip prio 4 handle 3 fw flowid 1:800




########## downlink #############

$ADDQDISC handle ffff: ingress

$ADDFILTER parent ffff: protocol ip prio 50 u32 match ip src \
    0.0.0.0/0 police rate ${DOWNLINK}kbit burst 5k drop flowid :1

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

             reply	other threads:[~2002-02-09 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09 19:07 Thomas Heinz [this message]
2002-02-09 21:05 ` [LARTC] htb causes roaring penguin's pppoe daemon to terminate Martin Devera
2002-02-09 22:24 ` [LARTC] htb causes roaring penguin's pppoe daemon to terminate connection Thomas Heinz
2002-02-09 22:41 ` [LARTC] htb causes roaring penguin's pppoe daemon to terminate Martin Devera
2002-02-10 14:47 ` [LARTC] htb causes roaring penguin's pppoe daemon to terminate connection Thomas Heinz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-101328197705968@msgid-missing \
    --to=josef.k@mytomorrow.de \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.