From: Martijn Lievaart <m@rtij.nl>
To: Brett Curtis <dashnu@gmail.com>
Cc: Netfilter Lists <netfilter@lists.netfilter.org>
Subject: Re: DNAT Question & ULOG Question
Date: Fri, 16 Jun 2006 12:09:45 +0200 [thread overview]
Message-ID: <44928369.4060803@rtij.nl> (raw)
In-Reply-To: <EB7DBACA-57BF-4FB5-9C71-03AA7D6C2C54@gmail.com>
Brett Curtis wrote:
> A couple questions before I try to push out my new firewall.
>
> Creating a PREROUTING rule on a DROP all policy like so.
I assume you mean DROP all policy on INPUT, FORWARD and OUTPUT.
>
> $IPT -t nat -A PREROUTING -i $EXTIF -d $HOST_EXTIP -p tcp --dport 22 \
> -j DNAT --to-destination $HOST_INTIP:22
Fine.
>
> This allows the packets to pass through my external nic so I would
> only need a forward rule like so to complete the request?
>
> $IPT -A FORWARD -o $INTIF -d $HOST_INTIP -p tcp --dport 22
Yes.
>
> From what I read the routing decision happens after PREROUTING but I
> am not sure if the request has traversed pass my external interface
> at this time.
> Not sure if I need to specify both interface or in my case it would
> be the same if I specified none.
I'm not sure what you mean, but it is quit simple. The rule is valid. In
the FORWARD chain, both -i and -o can be used. In this case, it is
redundand, but it doesn't hurt either.
> My question related to ULOG.... Is ULOG the only way to get iptables
> logging out of my dmesg ? Every time I type dmesg I find it
> overloaded with iptables logging.
>
Yes. Although the logging infrastructure is being rewritten for
x_tables, however, that most probably does not apply to you (you know it
if it does).
HTH,
M4
prev parent reply other threads:[~2006-06-16 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 14:50 DNAT Question & ULOG Question Brett Curtis
2006-06-16 10:09 ` Martijn Lievaart [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=44928369.4060803@rtij.nl \
--to=m@rtij.nl \
--cc=dashnu@gmail.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.