From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb causes roaring penguin's pppoe daemon to terminate
Date: Sat, 09 Feb 2002 21:05:43 +0000 [thread overview]
Message-ID: <marc-lartc-101328874921647@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101328197705968@msgid-missing>
> 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
Are you using the same htb patch ? 2.4.17 has done rather big
changes .. This is not the first incompatibility I've seen.
> 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.
you could try cbq instead. But I think that the problem is that
htb will accumulate too many packets and pppoe checks for it.
I've had similar problems during htb testing from userspace.
> Maybe someone experienced the same problem or can give me a hint what
> I should try to eliminate the problem.
use tc -s class show ethXX and tc -s qdisc and send me the results. I'm
interested in backlog sizes.
devik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-02-09 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 19:07 [LARTC] htb causes roaring penguin's pppoe daemon to terminate connection Thomas Heinz
2002-02-09 21:05 ` Martin Devera [this message]
2002-02-09 22:24 ` 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-101328874921647@msgid-missing \
--to=devik@cdi.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox