Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: dnat problem in transparent firewall
Date: Wed, 4 Aug 2004 09:45:19 +0100	[thread overview]
Message-ID: <200408040945.19567.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <200408041010.32442.raido@elin.ttu.ee>

On Wednesday 04 August 2004 8:10 am, Raido Kurel wrote:

> > Do you have a FORWARD rule allowing packets through to aaa.aaa.aaa.13
> > after they've been NATted?
>
> Yes.
> Also packets from Internet to aaa.aaa.aaa.13 reach destination.
> I am more worried about fact, that
> -t nat -A PREROUTING -j DNAT ...
> and then
> -t nat -A PREROUTING -j LOG ...
> does not log anything. Without the first rule logging works.

That's because the DNAT target does not return to the chain.   The LOG target 
is almost the only target I can think of which *does* return back to the 
chain for further processing - all other targets are the "final outcome" for 
the packet.

Put the two rules the other way round and you'll get both LOGging and 
DNATting.

Regards,

Antony.

-- 
Most people are aware that the Universe is big.

 - Paul Davies, Professor of Theoretical Physics

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-08-04  8:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04  7:10 dnat problem in transparent firewall Raido Kurel
2004-08-04  8:45 ` Antony Stone [this message]
2004-08-04 11:14   ` Raido Kurel
2004-08-04 11:30     ` Antony Stone
2004-08-04 12:05       ` Raido Kurel
  -- strict thread matches above, loose matches on Subject: below --
2004-08-03 11:36 Raido Kurel
2004-08-03 12:33 ` Antony Stone

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=200408040945.19567.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox