Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Prioritize packets at user space
Date: Thu, 06 Mar 2008 23:47:45 -0600	[thread overview]
Message-ID: <47D0D701.9010605@riverviewtech.net> (raw)
In-Reply-To: <7b4d898c0803052100x75f7d47fv53059b19ded04e48@mail.gmail.com>

On 3/5/2008 11:00 PM, Ling Deng wrote:
> I want to add a priority on the firewall. To prioritize the packets, 
> deep packet inspection is needed, then packets need to be put in 
> different queues depending on the caller and callee numbers.

If you can separate out the calls or mark them somehow, you could use 
Traffic Control to divide things in to different queues for you.  I'd 
suggest looking at SIP Express Router (presuming you are using SIP) as a 
local gateway to route the calls.  If you can get S.E.R. to either mark 
the packets of a call or to send them to different destinations (IP and 
/ or port) you could then use TC to prioritize.  You just have to help 
get the traffic split out (de-multiplexed) so that TC can work with it. 
  Presently TC does not (to my knowledge) have any way to identify what 
calls are what.  However I suppose you could get really creative with 
either the u32 or layer 7 matches and look for specific strings in the 
packet stream and decide what to do with them that way.  If you can get 
IPTables match extensions to differentiate your calls, you can mark them 
so that TC can work with them.

> Thank you very much,

You are welcome, and good luck.



Grant. . . .

      reply	other threads:[~2008-03-07  5:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06  5:00 Prioritize packets at user space Ling Deng
2008-03-07  5:47 ` Grant Taylor [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=47D0D701.9010605@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox