From: Raido Kurel <raido@elin.ttu.ee>
To: netfilter@lists.netfilter.org
Subject: dnat problem in transparent firewall
Date: Wed, 4 Aug 2004 10:10:32 +0300 [thread overview]
Message-ID: <200408041010.32442.raido@elin.ttu.ee> (raw)
Sorry, about not beeing in the thread. I just subscribed and can see message
just in archive...
> > Needs:
> > To change destination IP of some packets coming from Internet. ie to
> > change destination IP from aaa.aaa.aaa.12 to aaa.aaa.aaa.13
...
> > iptables -t nat -A PREROUTING -d aaa.aaa.aaa.12 -j DNAT --to-dest
> > aaa.aaa.aaa.13
>
> 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.
I thought, that -j DNAT should pass packet for next nat PREROUTING rule for
logging. According to http://ebtables.sourceforge.net/br_fw_ia/PacketFlow.png
packet should next go to ebtables filter table input or forward chains, but
nothing reaches there in case of the iptables -t nat -A PREROUTING -j DNAT
rule.
Raido
next reply other threads:[~2004-08-04 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 7:10 Raido Kurel [this message]
2004-08-04 8:45 ` dnat problem in transparent firewall Antony Stone
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=200408041010.32442.raido@elin.ttu.ee \
--to=raido@elin.ttu.ee \
--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.