From: Grant Taylor <gtaylor@riverviewtech.net>
To: Guido Lorenzutti <guido@lorenzutti.com.ar>
Cc: netfilter@lists.netfilter.org
Subject: Re: travelling the tables and chains...
Date: Sun, 03 Apr 2005 22:30:08 -0500 [thread overview]
Message-ID: <4250B4C0.5050405@riverviewtech.net> (raw)
In-Reply-To: <4250A5A6.6040509@lorenzutti.com.ar>
If I understand you correctly, you are wanting traffic that is not DNATed to pass through your FORWARD_WAN_TO_LAN chain? If that is the case you should try something like this:
iptables -A FORWARD -i $WAN -o $LAN -m state --state INVALID,NEW,UNTRACKED -j FORWARD_WAN_TO_LAN
iptables -A FORWARD -i $WAN -o $LAN -m state --state ESTABLISHED,RELATED -j ACCEPT
This should cause all traffic (if I understand correctly) that is not recognized by DNAT... (as I type this I'm thinking SNAT, but DNAT *may* behave the same way too) ...to be send to the FORWARD_WAN_TO_LAN and any traffic that is recognized by DNAT to be plainly ACCEPTED.
Does any one else have any comments on this?
Grant. . . .
Guido Lorenzutti wrote:
> Hi people, i would like to clean up my firewall script by creating new
> chains in the filter table. Like this:
>
> iptables -N FORWARD_WAN_TO_LAN
>
> Then, call the traffic in the FORWARD chain:
>
> iptables -A FORWARD -i $WAN -o $LAN -j FORWARD_WAN_TO_LAN
>
> Now how can i discriminate the DNATed packets from that rule? It's OK if
> i MARK them in the PREROUTING chain and create a rule BEFORE in the
> FORWARD chain to check if the packet im MARKed then -j DNATED_WAN_TO_LAN?
>
> Any better ideas?
>
next prev parent reply other threads:[~2005-04-04 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:25 travelling the tables and chains Guido Lorenzutti
2005-04-04 3:30 ` Grant Taylor [this message]
2005-04-05 4:28 ` Jason Opperisano
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=4250B4C0.5050405@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=guido@lorenzutti.com.ar \
--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