All of lore.kernel.org
 help / color / mirror / Atom feed
From: GW <WGxxx@web.de>
To: lartc@vger.kernel.org
Subject: [LARTC] How to priorize incoming traffic
Date: Wed, 13 Mar 2002 21:54:23 +0000	[thread overview]
Message-ID: <marc-lartc-101605667320132@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101605815724806@msgid-missing>

Hello,

I think of how to priorize incoming traffic.

Therefor I read different web pages and found two different meanings.

On http://www.docum.org/stef.coene/qos/docs/BB/BB.html:

You can do traffic shaping with the Linux kernel. It's very important 
that you understand that you can only shape the outgoing bandwidth.

On http://www.docum.org/stef.coene/qos/docs/mail_2.html:

# suppose you want to limit incoming web traffic (you are the client not 
the server so the _source_ port is 80) mark the packets with 1 in netfilter
# the handle seems to require to have value ffff (why ???)
/sbin/iptables -A PREROUTING -i eth0 -t mangle -p tcp --sport 80 -j MARK 
--set-mark 1
# then add the queuing discipline
tc qdisc add dev eth0 handle FFFF: ingress
# limit bw to 64kbit. I'm not really sure of the burst and mtu values...
tc filter add dev eth0 parent ffff: protocol ip prio 50 handle 1 fw 
police rate 64kbit burst 2400 mtu 9k drop flowid :1

Well, does anybody know whether it is possible to limit/manage incoming 
traffic in this way mentioned above or not?

Thanks,
Georg

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

      reply	other threads:[~2002-03-13 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 21:19 [LARTC] How to priorize incoming traffic Stef Coene
2002-03-13 21:54 ` GW [this message]

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-101605667320132@msgid-missing \
    --to=wgxxx@web.de \
    --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.