netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: hadi@cyberus.ca
Cc: netdev@oss.sgi.com
Subject: Re: IMQ / new Dummy device post.
Date: Thu, 15 Apr 2004 20:35:01 +0100	[thread overview]
Message-ID: <407EE3E5.8060200@dsl.pipex.com> (raw)
In-Reply-To: <1082031313.1039.13.camel@jzny.localdomain>

jamal wrote:
> On Thu, 2004-04-15 at 05:42, Andy Furniss wrote:
> 
> 
>>The only reason I use IMQ (+ NAT patch) is that I need to shape ingress 
>>(I know I can't shape it "properly" from the wrong end of the bottleneck 
>>without an intelligent app, but the ingress policer does not let me 
>>share local and forwarded bandwidth and is not fair per user if I just 
>>throttle the whole link).
>>
>>I am not sure if dummy will sort this for me, there may be some other way?
> 
> 
> The summary is dummy can do what IMQ used to; it is however not related
> to iptables/netfilter. 
> 
> 
>>Basically all I need is something I can use HTB on where the qos ingress 
>>box is on this diagram.
> 
> 
> Yes you can attach a HTB. Look at the posted example in the previous
> email and replace prio with HTB. 
> Not sure i answered your questions.

What I want to know is what state IP packets will be in if I 
filter/shape with dummy - In my case I would need them to have been 
demasqued so I can tell the difference between local and to be forwarded 
ingress traffic.

Ie. where on the KPTD would dummy be - IMQ appears twice and by using 
the IMQ nat patch I can use the prerouting one to filter/shape the 
packets after they are denatted.

Andy.

> 
> Again to emphasize: I will send patches only to people interested.
> People have to ask directly;
> this is my way of monitoring what is being tested. At some point i will
> make the latest patches available to everyone.
> 
> cheers,
> jamal

  reply	other threads:[~2004-04-15 19:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15  9:42 IMQ / new Dummy device post Andy Furniss
2004-04-15 12:15 ` jamal
2004-04-15 19:35   ` Andy Furniss [this message]
2004-04-16  3:52     ` jamal
2004-04-16 19:35       ` Andy Furniss
     [not found]         ` <1082145341.1026.125.camel@jzny.localdomain>
2004-04-17 10:39           ` Andy Furniss
2004-04-17 12:09             ` jamal
2004-04-17 21:56               ` Andy Furniss
2004-04-18 14:28                 ` jamal
2004-04-18 16:35                   ` Andy Furniss
2004-04-18 20:34                     ` Andy Furniss
2004-04-18 21:07                       ` jamal
2004-04-18 21:31                         ` Andy Furniss
2004-04-18 21:45                           ` Andy Furniss
2004-04-18 20:53                     ` jamal
2004-04-18 21:23                       ` Martin Josefsson
2004-04-18 21:58                         ` Andy Furniss
2004-04-19  8:14                           ` Martin Josefsson
2004-04-19 12:33               ` syrius.ml
  -- strict thread matches above, loose matches on Subject: below --
2004-04-19 14:22 syrius.ml
2004-04-20  2:15 ` jamal
2004-04-21  1:43   ` syrius.ml
2004-04-21 12:49     ` syrius.ml
2004-04-21 20:19       ` syrius.ml
2004-04-22 13:16         ` jamal
2004-04-22 17:43           ` syrius.ml
2004-04-23 11:29             ` jamal

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=407EE3E5.8060200@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).