From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 2 Questions on filtering incoming stuff
Date: Tue, 18 May 2004 00:25:26 +0000 [thread overview]
Message-ID: <40A957F6.5050509@snapgear.com> (raw)
In-Reply-To: <40A92F1A.4030706@wildgooses.com>
Hi Ed,
> First is: Can I prioritise my "drops" on incoming traffic when the link
> is overloaded. ie instead of just tail dropping, can I "prefer" to drop
> certain classes of traffic? If so, do I do this by setting up, say, a
> HTB tree like on the incoming, but the only action at the leaf is to drop?
You can't set up a HTB or any classful qdiscs on incoming traffic, you can only
create ingress policer filters. You can setup different filters with different
priorities, to try and drop one particular type of traffic moreso than others.
If you're using a linux gateway onto your lan, then you can use a HTB qdiscs
on the outgoing (lan) interface which would do a better job.
regards
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer email: damion@snapgear.com
SnapGear - A CyberGuard Company --- ph: +61 7 3435 2809
| Custom Embedded Solutions fax: +61 7 3891 3630
| and Security Appliances web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Free Embedded Linux Distro at http://www.snapgear.org ---
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-05-18 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 21:31 [LARTC] 2 Questions on filtering incoming stuff Ed Wildgoose
2004-05-17 23:19 ` Andy Furniss
2004-05-18 0:25 ` Damion de Soto [this message]
2004-05-18 1:55 ` Andreas Klauer
2004-05-18 6:54 ` Ed Wildgoose
2004-05-18 7:18 ` Damion de Soto
2004-05-18 7:21 ` Ed Wildgoose
2004-05-18 7:56 ` Ed Wildgoose
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=40A957F6.5050509@snapgear.com \
--to=damion@snapgear.com \
--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.