All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Jalsovsky <admin@postel.sk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ and outgoing traffic.
Date: Tue, 28 Jan 2003 08:07:31 +0000	[thread overview]
Message-ID: <marc-lartc-104374132226085@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104373009917232@msgid-missing>


Hello,

	please keep in mind that there is a BUG in IMQ code so you can't
add ingress and egress packets into the same IMQ device from the same
physical device.
e.g.
iptables -t mangle -A POSTROUTING -o eth0 -j IMQ
iptables -t mangle -A PRETROUTING -i eth0 -j IMQ

You will get kernel panic (I tested it with 2.4.20-ac1 and latest
IMQ/HTB).

Is this problem solved?

	Thomas

On Mon, 27 Jan 2003, Martin A. Brown wrote:

> Leszek,
>
>  : Configuring IMQ for egress traffic, it is not possible
>  : to specify interfaces which we want use to shape.
>
> I'm afraid I'll have to disagree!  :)  Try adding the "-o interface" flag
> to your iptables command to select based on the output interface.
> Instead of:
>
>   iptables -t mangle -A POSTROUTING -j IMQ
>
> Use:
>
>   iptables -t mangle -A POSTROUTING -o eth0 -j IMQ
>   iptables -t mangle -A POSTROUTING -o eth1 -j IMQ
>   iptables -t mangle -A POSTROUTING -o eth2 -j IMQ
>
> As long as you don't write an iptables command which matches packets
> leaving eth3 (and directs them to IMQ), you should have what you desire.
>
> -Martin
>
> --
> Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-01-28  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28  5:00 [LARTC] IMQ and outgoing traffic Leszek A.Szczepanowski
2003-01-28  5:27 ` Martin A. Brown
2003-01-28  8:07 ` Thomas Jalsovsky [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-104374132226085@msgid-missing \
    --to=admin@postel.sk \
    --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.