All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Salatiel Filho <salatiel.filho@gmail.com>
Cc: Jan Engelhardt <jengelh@medozas.de>,
	Jarek Poplawski <jarkao2@gmail.com>, "Y. D." <duyuyang@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: IMQ bug: kernel reboot immediately
Date: Thu, 23 Apr 2009 13:22:19 +0200	[thread overview]
Message-ID: <49F04F6B.7010709@trash.net> (raw)
In-Reply-To: <beb91d720904230412j4dea4034o61f2d0682ff76d1a@mail.gmail.com>

Salatiel Filho wrote:
> On Thu, Apr 23, 2009 at 07:28, Patrick McHardy <kaber@trash.net> wrote:
>> I'm aware of those claims, but not of the details. If this is true,
>> people should raise those issues and help resolve them. I wouldn't
>> hold my breath waiting for IMQ to get fixed.
>>
> 
> I would love to see a way to change where IFB hooks [if "hook" is the
> right term ], till now i dont think i am able to hook it after nat in
> prerouting and before nat in postrouting. Is there a way to do this ?
> What i basically do with IMQ is:
> 
> 
>                          eth0 [192.168.0.0/24]
> ppp0   <---->       eth1 [192.168.1.0/24]
>                          eth2 [192.168.2.0/24]
> 
> Using imq i can shape upload on ppp0 [postrouting] while still having
> the internal private ips from the hosts, and i can shape download in
> ppp0 [prerouting] after get the correct nat'ed addresses.
> 
> Is there a way to achieve this in IFB ? in a simple way ... :)

Currently not, the conntrack association is done at a later point.
We could add a classifier or TC action that performs the lookup
during ingress classification.

Alternatively classifiers using conntrack information (like cls_flow)
could perform the lookup directly, but that would probably get a bit
ugly since some validation needs to be performed previously and it
would add a module dependency on conntrack.


  reply	other threads:[~2009-04-23 11:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 15:27 IMQ bug: kernel reboot immediately Y. D.
2009-04-23  8:43 ` Jarek Poplawski
2009-04-23 10:20   ` Patrick McHardy
2009-04-23 10:23     ` Jan Engelhardt
2009-04-23 10:28       ` Patrick McHardy
2009-04-23 11:12         ` Salatiel Filho
2009-04-23 11:22           ` Patrick McHardy [this message]
2009-04-23 11:40             ` Jarek Poplawski
2009-04-23 11:46               ` Patrick McHardy
2009-04-23 12:11                 ` Jarek Poplawski
2009-04-23 12:13                   ` Patrick McHardy
2009-04-23 12:37             ` Salatiel Filho
2009-04-23 12:41               ` Patrick McHardy
2009-04-23 23:32                 ` Salatiel Filho
2009-04-24 14:49                   ` Patrick McHardy
2009-04-24 14:55                     ` Denys Fedoryschenko
2009-04-24 15:14                       ` Salatiel Filho
2009-04-24 15:19                         ` Patrick McHardy
2009-04-24 15:23                           ` Salatiel Filho
2009-04-24 15:29                             ` Patrick McHardy
2009-04-23 12:29     ` Y. D.
2009-04-23 12:46       ` Jarek Poplawski
2009-05-02 12:03 ` pud

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=49F04F6B.7010709@trash.net \
    --to=kaber@trash.net \
    --cc=duyuyang@gmail.com \
    --cc=jarkao2@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=salatiel.filho@gmail.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 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.