All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex" <alex@hostingcenter.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: HTB and metro+int. limits
Date: Wed, 01 Oct 2003 16:00:09 +0000	[thread overview]
Message-ID: <marc-lartc-106502418030187@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106495028017660@msgid-missing>

I'm sorry, but I'm still confused about assigning separate limits for metro
and international traffic.
After I mark metro traffic with --set-mark 6 and int. traffic
with --set-mark 5 what's the next step?
Can someone give me an example? It seems that my approach is somehow wrong
after marking of the packets.

Thanks again.

Alex
----- Original Message ----- 
From: "Stef Coene" <stef.coene@docum.org>
To: "Alex" <alex@hostingcenter.ro>; "Lartc" <lartc@mailman.ds9a.nl>;
<cmulcahy@avesi.com>
Sent: Wednesday, October 01, 2003 12:59 PM
Subject: Re: [LARTC] Re: HTB and metro+int. limits


> On Tuesday 30 September 2003 21:27, Alex wrote:
> > Thanks for your replay, it really helps, but to take the question
further,
> > from what you have seen in my sample script, how should I classify
packets
> > with "tc" ? I don't know  how to put them in separate classes,. What I
have
> > in my script will only shape metro traffic, but for international how
would
> > the "tc" command be?
> > Something like:
> > /sbin/tc class add dev eth2 parent 1:2 classid 2:11 htb rate 50kbit ceil
> > 100kbit prio 5
> > /sbin/tc filter add dev eth2 parent 1:0 protocol ip prio 5 u32 match ip
dst
> > 192.168.254.10 flowid 1:11
> > Would this be the correct commands?
> No.  You create a class with a wrong number.  If the parent class is 1:x,
the
> class name has to be 1:y.
>
> > Thanks again.
> >
> > Alex
> > ---begin my script----
> > sbin/tc qdisc add dev eth2 root handle 1: htb default 10
> > /sbin/tc class add dev eth2 parent 1: classid 1:1 htb rate 10M
> > #metro
> > /sbin/tc class add dev eth2 parent 1:1 classid 1:10 htb rate 10M
> > /sbin/tc filter add dev eth2 protocol ip parent 1:10 prio 3 handle 6
flowid
> > 1:10
> This filter will not do much (typo?).  You attach it to class 1:10 (the
parent
> parameter).  This should be 1: so all packets leaving eth2 will be checked
> against this filter.
> And is 10M working?  Normally 10mbit is used.
>
> Stef
>
> -- 
> stef.coene@docum.org
>  "Using Linux as bandwidth manager"
>      http://www.docum.org/
>      #lartc @ irc.openprojects.net
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


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

      parent reply	other threads:[~2003-10-01 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 19:27 [LARTC] Re: HTB and metro+int. limits Alex
2003-10-01  9:59 ` Stef Coene
2003-10-01 16:00 ` Alex [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-106502418030187@msgid-missing \
    --to=alex@hostingcenter.ro \
    --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.