All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matteo Brusa <miagi@tiscali.it>
To: lartc@vger.kernel.org
Subject: [LARTC] Shaping incoming traffic on the other interface
Date: Thu, 10 Jun 2004 12:35:21 +0000	[thread overview]
Message-ID: <40C85589.10907@tiscali.it> (raw)

Hi,
I have a typical configuration for my firewall/gateway box: single network card, with a pppoe 
connection to the DSL modem.
I'm already successfully shaping the uplink (how come that the wondershaper.htb doesn't use the ceil 
parameter? It should implement bandwidth borrowing!) but i found the ingress policy a little bit rough.
I'd like to keep the traffic categories i have in the uplink: ssh, web and batch.
The goal is to discard packets of the lowest class first, then the middle, and so on.
I've implemented a simmetrical downlink version of the uplink shaping on eth0, the other interface. 
However, i get this error (warning?) in the log:
	pppoe[29606]: send (sendPacket): No buffer space available
It looks like the interface queue is complaining that it cannot deliver a packet (the uplink queue 
being full) and therefore discarding some packet. This is not the behaviour i meant.
Anybody has ideas/suggestions/comments?

As an alternative, it would be a pretty good solution to tell the polishing filter to discard only 
packets where the source port is !22. But i'd rather stay away of a ingress policer, because i had 
problems with it.

Thanks in advance,

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

                 reply	other threads:[~2004-06-10 12:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40C85589.10907@tiscali.it \
    --to=miagi@tiscali.it \
    --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.