All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alin Nonosel" <alin@polar.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] imq question
Date: Tue, 24 Aug 2004 15:16:26 +0000	[thread overview]
Message-ID: <000f01c48a3f$119c5f90$195a09c2@alin> (raw)
In-Reply-To: <marc-lartc-102061821314701@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]

Hmm.. After a few hour of reading and testing finally it's working. IMQ upload limiting and tc with ip filter. What do you mean by that? It is working.. And so far seems stable..

  ----- Original Message ----- 
  From: Roy 
  To: Alin Nonosel ; lartc@mailman.ds9a.nl 
  Sent: Monday, August 23, 2004 6:45 AM
  Subject: Re: [LARTC] imq question


  You cant shape router upload or imq will crash.
  also that imq will not be able to shape traffic per each loacal ip with filters, but you can easily mark packets with iptables in forward of prerouting chain.



    ----- Original Message ----- 
    From: Alin Nonosel 
    To: lartc@mailman.ds9a.nl 
    Sent: Tuesday, August 24, 2004 1:32 AM
    Subject: [LARTC] imq question


    Hi

    I've a stupid question. How can I shape upload using IMQ?
    Instead of putting a rule in iptables in PREROUTING should i use POSTROUTING?
    And another question is, can I make routing rule based on ip addresses assigned by iptables to an imq device?
    The idea is, let's say i have some rules in iptables like: -t mangle -A PREROUTING -s 192.168.0.0/16 -j IMQ --todev 0
    Can i route this class thru another ip, something like fwmark is doing? with iptables marking the packets and ip rule fwmark?

    Best regards,
    Alin

[-- Attachment #2: Type: text/html, Size: 3578 bytes --]

      parent reply	other threads:[~2004-08-24 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-05 17:02 [LARTC] IMQ question Ciprian Niculescu
2002-05-05 17:55 ` Martin Devera
2004-08-23 12:46 ` [LARTC] imq question Alin Nonosel
2004-08-23 13:45 ` Roy
2004-08-24 15:16 ` Alin Nonosel [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='000f01c48a3f$119c5f90$195a09c2@alin' \
    --to=alin@polar.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.