All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] My filter setting is right?
Date: Sun, 20 Apr 2003 21:36:54 +0000	[thread overview]
Message-ID: <marc-lartc-105087466825886@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105082371731870@msgid-missing>

On Sunday 20 April 2003 09:27, openings wrote:
> dear, folks.
>
> I want to following policy.
>
> ========= policy which i want  (eth0)=======>
>                                                eth0
>                                               HTB(1:0)
>
>                                                  1:1
>                                              /          \
>                                           /               \
>                                        /                     \
>                        1:10                                          1:11
>                     host 1(dst)                               host 2(dst)
>                    /   |   \                                   /   |   \
>                  /     |     \                               /     |     \
>                /       |      \                            /       |      \
>              /         |        \                        /         |       
> \ 1:21      1:22    1:23                   1:31      1:32     1:33 port80  
> port22    etc.                port80   port22    etc.
>
> =========================>
> i use following filter setting (pseudo setting).
>
> is this right?
>
> # for traffic to host1
> filter add dev eth0 , prio 0 , match ip dst [host1 IP],match ip dport 80,
> flowid 1:21 filter add dev eth0 , prio 1 , match ip dst [host1 IP],match ip
> dport 22, flowid 1:22 filter add dev eth0 , prio 2 , match ip dst [host1
> IP],flowid 1:23
>
> #for traffic to host2
> filter add dev eth0 , prio 0 , match ip dst [host2 IP],match ip dport 80,
> flowid 1:31 filter add dev eth0 , prio 1 , match ip dst [host2 IP],match ip
> dport 22, flowid 1:32 filter add dev eth0 , prio 2 , match ip dst [host2
> IP],flowid 1:33
>
> ===========================
>
> all etc traffic which destined to host1 must classify to class 1:23.
> my filter's priority setting is right?
The different prio's in the filters are not needed.  You only need them to 
determine the order of the filters.  In your case, order doesn't mather for 
the prio0 and the prio1 filters.  
I'm not sure myself, but the lower the prio, the higher the priority.  So in 
your filter setup, your catch-all filter should have the lowest prio.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

      reply	other threads:[~2003-04-20 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-20  7:27 [LARTC] My filter setting is right? openings
2003-04-20 21:36 ` Stef Coene [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-105087466825886@msgid-missing \
    --to=stef.coene@docum.org \
    --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.