All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Heider <a.heider@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] ingress/imq shaping setup
Date: Mon, 04 Jul 2005 10:40:11 +0000	[thread overview]
Message-ID: <42C9120B.2040605@gmail.com> (raw)

hi list,

i'm about to setup traffic shaping on a server and got some small
questions about the setup. i read alot of docs/howto's but there are
still some questions i'd like to ask.

setup on the box is:
- external if is ppp0 (dsl)
- internal if in eth0 (with ~15 nat'ed boxes)
- openvpn at tun1

since all ppl on the lan feel like they have to use p2p i decided to
drop all p2p coming from eth0 using layer7 and put mldonkey on the
server. to shape this local traffic and the traffic from ppp0->eth0 it
seems like imq is the only solution to me. my idea on imq0 was something
like this:

- 1: qdisc hfsc default 50
  - 1:1 class hfsc
    - 1:10 class hfsc (high prio like ssh, vpn)
    - 1:20 class hfsc (local traffic)
      - 1:21 class hfsc (p2p)
      - 1:22 class hfsc (all other local)
    - 1:30 class wrr (lan boxes)
    - 1:50 class hfsc (all other)

if i understood something wrong and this doesnt make any sense please
advise me ;)

1) the traffic is already marked, can i simply switch to CLASSIFY (for
keeping the script small) or should i use tc filter by fw handle?

2) should i use ingress on ppp0? (although any incoming packet is going
through imq)

3) do i simply put all ppp0->eth0 traffic in the wrr class and it does
its job? or can i add subclasses for each box and it shapes fair between
those? (idea is to add sfq as leaf to take tos into account).

4) is esfq instead of wrr more suitable for my situation (sorry for that
question, but docs are pretty rare for those 2)

any comments are appreciated

thx in advance
andre
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

                 reply	other threads:[~2005-07-04 10:40 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=42C9120B.2040605@gmail.com \
    --to=a.heider@gmail.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.