All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: How to classify a port range?
Date: Thu, 24 Nov 2016 23:29:16 +0000	[thread overview]
Message-ID: <583777CC.8020207@gmail.com> (raw)
In-Reply-To: <2cc58282-00cf-0fb5-9583-3ebc86f7eedd@itlabs.bg>

Yassen Damyanov wrote:
> Hello LARTC guys,
>
> I am working on an OSS Python wrapper library intended to help with
> expressing a traffic control structure as a tree of Python objects. This
> structure should later be able to represent itself as a series of tc
> commands. (Your suggestions for getting this thing useful would be
> invaluable.)
>
> I have questions, inevitably. Currently heaviest part seems to be the
> issue of classifying a set of tcp or udp ports to get shaped under a
> common rate limit. (I need to later simulate packet loss for flows on
> these ports, but first things first.)
>
> Can you help me get on the right direction here? Using u32 seems
> daunting for this particular case. Is there another way to do the match?
>
> I've read the relevant parts of the LARTC HowTo and couple more
> documents but still cannot get it right.
>
> Any help would be much appreciated!
> Thanks in advance,
> Yassen D.
>

I've never used ematch so don't know if this is correct or not, but -

http://serverfault.com/questions/231880/how-to-match-port-range-using-u32-filter


  reply	other threads:[~2016-11-24 23:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 10:56 How to classify a port range? Yassen Damyanov
2016-11-24 23:29 ` Andy Furniss [this message]
2016-11-25 14:52 ` Yassen Damyanov
2016-11-25 17:19 ` Andy Furniss
2016-11-25 18:34 ` Yassen Damyanov
2016-12-17 16:12 ` Yassen Damyanov
2016-12-17 22:43 ` Andy Furniss

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=583777CC.8020207@gmail.com \
    --to=adf.lists@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.