From: Guy Van Den Bergh <guy.vandenbergh@pandora.be>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Sharing bandwidth between two interfaces
Date: Thu, 05 Apr 2001 21:59:43 +0000 [thread overview]
Message-ID: <marc-lartc-98650805214838@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98620649426867@msgid-missing>
Christian Worm Mortensen wrote:
>
> What in fact is the ingress qdisc? Accoring to the howto it limits _incomming_ bandwidth. But a basic principple of qdiscs is that they handle _outgoing_ packets. How does this make sence?
>
Indeed, it is normally not done, but if you want to shape incoming bandwidth, it is perfectly
possible to create a queue for incoming packets, and to do ingress policing by means of this queue.
That's what the ingress policing qdisc does...
One major application of ingress policing is only letting a limited rate of icmp or
tcp syn packets coming into your network. That will keep your network less vulnerable
for ping floods and dos attacks.
>
> Christian
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
_______________________________________________
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-04-05 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 10:14 [LARTC] Sharing bandwidth between two interfaces
2001-04-02 18:21 ` Christian Worm Mortensen
2001-04-04 8:14 ` Vladimir Smelhaus
2001-04-04 10:48 `
2001-04-05 14:16 ` worm
2001-04-05 17:41 ` Guy Van Den Bergh
2001-04-05 20:42 ` Christian Worm Mortensen
2001-04-05 21:59 ` Guy Van Den Bergh [this message]
2001-04-06 6:24 ` Christian Worm Mortensen
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-98650805214838@msgid-missing \
--to=guy.vandenbergh@pandora.be \
--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