All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Akos Szalkai" <szalkai@2fkft.com>
To: netfilter@lists.netfilter.org
Subject: Re: mangle after nat in the postrouting chain
Date: Fri, 28 Nov 2003 19:13:58 +0100	[thread overview]
Message-ID: <20031128181358.GK5232@2fkft.com> (raw)
In-Reply-To: <7C9884991ADAE0479C14F10C858BCDF5122EAA@alderaan.smgtec.com>

On Fri, Nov 28, 2003 at 09:50:46AM -0800, Daniel Chemko wrote:
> You are off basis. The System already routes twice.

Yes, I know that.  This is not my problem.

> The problem is that it SNAT's after you've already routed the packet.

This is much closer to my problem, see below.

>                 There is also the ROUTE patch, but it doesn't do what I
> want it to do (change the packet's route!!).

Yes, I am heavily using the ROUTE patch.  It does change the packet's
route.  I don't think you can live without it in a multiple independent
internet link environment.  Still, ROUTE targets are in the mangle
table, so still, it is SNAT-ed after you reroute the packets with a
ROUTE rule.

I can get around this by making a more complex rulebase, but it would be
much neater if I could mangle packets after NATing.  (The iproute2
solution you mentioned is also a possibility, but it has the drawback
that you have to use something else besides netfilter.  The ROUTE patch
is very similar but IMHO more manageable.)

Akos

-- 
Akos Szalkai <szalkai@2f.hu>
IT Consultant, CISA
2F 2000 Szamitastechnikai es Szolgaltato Kft.
Tel: (+36-1)-4887700  Fax: (+36-1)-4887709  WWW: http://www.2f.hu/


  reply	other threads:[~2003-11-28 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28 17:50 mangle after nat in the postrouting chain Daniel Chemko
2003-11-28 18:13 ` Akos Szalkai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-28 17:33 Akos Szalkai
2003-11-28 17:55 ` Jeffrey Laramie

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=20031128181358.GK5232@2fkft.com \
    --to=szalkai@2fkft.com \
    --cc=netfilter@lists.netfilter.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.