From: "Manfred Bartz" <md-lartc@logi.cc>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shaping incoming traffic?
Date: Sun, 18 Nov 2001 14:17:10 +0000 [thread overview]
Message-ID: <marc-lartc-100609302925685@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100608970116427@msgid-missing>
Martin Devera <devik@cdi.cz> writes:
> It is nerly FAQ. You can use Ingres qdisc to do it and attach
> policers here.
Ah ok, I found the SYN flood example in the HOWTO. :)
But that seems to work by dropping packets rather than queueing them,
which is not so good if your bandwidth is very limited (modem dialup).
> It would be nice to be able to attach every qdisc to incoming interface
> but it is not possible. There is always problem - when packet already
> hitted your box why do you want to drop/delay it ?
Because some of the traffic is for this box (doesn't go out) and I
don't want it to ``steal' all the bandwidth from traffic that is
forwarded through the box. Also, the traffic is mostly asymmetric,
lots of data coming in and only ACKs going out.
> On your virtual-host note. I already did patch (called IMQ) which
> implements virtual inteface allowing to attach single qdisc to multiple
> outgoing devices.
Could you post the URL for that?
> It should be relatively easy to extend it to catch incoming packets
> too
> - only there is no time to do it.
Hmm, lack of time is a universal problem me thinks... ;)
--
Manfred
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-11-18 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 13:21 [LARTC] Shaping incoming traffic? Manfred Bartz
2001-11-18 13:48 ` Martin Devera
2001-11-18 14:17 ` Manfred Bartz [this message]
2001-11-18 23:50 ` Michael T. Babcock
2001-11-19 10:42 ` Fredrik Björk
2001-11-19 11:07 ` devik
2001-11-20 7:12 ` Kristian Hoffmann
2001-11-20 9:12 ` Martin Devera
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-100609302925685@msgid-missing \
--to=md-lartc@logi.cc \
--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