All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jay Wineinger" <shad@wnoc.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] marking
Date: Tue, 28 Jan 2003 03:55:27 +0000	[thread overview]
Message-ID: <marc-lartc-104372660214533@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101665894626463@msgid-missing>

> It's not clear to me how your setup look like and what you want to do.
>
> Stef
>

Ok, what I want to do is setup 4 or 5 classes for traffic headed out my
external interface(eth0).  They should be something like interactive (icmp,
ssh, etc), mail (smpt,pop,imap), web (http/https), and bulk.   My problem
right now is figuring out the correct configuration so that I do not limit
traffic that is only destined FOR the QoS box, which also does DHCP, nat,
samba, etc for the internal nat'd subnet (eth1).  I also run a squid caching
proxy server for the network's http/https connections.

Im having trouble figuring where the correct place to mark each packet would
be. Do i need to do some in -t mangle PREROUTING or INPUT or FORWARD?  Im
confused as to how to differentiate between packets destined for the outside
world (out eth0) and those that are staying on the internal network.

This is what Ive pulled out of my butt for my qdisc setup:

# Create new root qdisc on eth1 and parent for everything
$TC qdisc add dev eth1 root handle 1: htb default 2022
$TC class add dev eth1 parent 1: classid 1:1 htb rate 95mbit ceil 95mbit

# Create parent class for outbound
$TC class add dev eth1 parent 1:1 classid 1:10 htb rate 350kbps burst 2k
ceil 350kbps
  # Create subclasses on outbound traffic for interactive,mail,www,bulk
  $TC class add dev eth1 parent 1:10 classid 1:101 htb rate 50kbps burst 2k
prio 0    [interactive]
  $TC class add dev eth1 parent 1:10 classid 1:102 htb rate 50kbps burst 2k
prio 1    [mail]
  $TC class add dev eth1 parent 1:10 classid 1:103 htb rate 50kbps burst 5k
prio 2    [ www is limited farther upstream anyway =(   ]
  $TC class add dev eth1 parent 1:10 classid 1:104 htb rate 70kbps burst 2k
prio 3 ceil 125kbps    [bulk]

# Create parent class for internal subnet traffic
$TC class add dev eth1 parent 1:1 classid 1:20 htb rate 60mbit ceil 90mbit
  # Create subclasses on internal traffic for interactive and bulk traffic
  $TC class add dev eth1 parent 1:20 classid 1:201 htb rate 150kbps burst 2k
prio 0    [local interactive]
  $TC class add dev eth1 parent 1:20 classid 1:202 htb rate 50mbit prio 1
ceil 55mbit
    # Create subclasses on internal bulk traffic (1:202) for www and other
    $TC class add dev eth1 parent 1:202 classid 1:2021 htb rate 25mbit prio
0    [local webserver traffic]
    $TC class add dev eth1 parent 1:202 classid 1:2022 htb rate 25mbit prio
1    [bulk]

Am i going about this all wrong?

thanks for any help/suggestions
jay





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

  parent reply	other threads:[~2003-01-28  3:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20 21:14 [LARTC] Marking Ali badilli
2002-03-21 21:06 ` Viktor Kemmet
2003-01-27  4:50 ` [LARTC] marking Jay Wineinger
2003-01-27 18:17 ` Stef Coene
2003-01-28  3:55 ` Jay Wineinger [this message]
2003-01-28  9:52 ` Stef Coene
2003-01-28 19:56 ` Stef Coene
2003-01-28 21:47 ` Jay Wineinger
2003-01-29 17:33 ` Stef Coene

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-104372660214533@msgid-missing \
    --to=shad@wnoc.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.