From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Re - NAT to client
Date: Sun, 1 May 2005 17:58:02 -0400 [thread overview]
Message-ID: <20050501215802.GA8642@bender.817west.com> (raw)
In-Reply-To: <8187f8816eb6.816eb68187f8@vsnl.net>
On Fri, Apr 29, 2005 at 07:13:37PM +0500, varun_saa@vsnl.net wrote:
> >> # Generated by iptables-save v1.2.9 on Tue Apr 26 14:50:01 2005
> >> *nat
> >> :OUTPUT ACCEPT [0:0]
> >> :PREROUTING ACCEPT [0:0]
> >> :POSTROUTING ACCEPT [0:0]
> >> -A POSTROUTING -o eth0 -j MASQUERADE
>
> so you MASQ all outbound traffic
>
> Well should I or not.
that's the only question you have from my post?
> I have a static IP and my subnets are
>
> 192.168.0.0/24
>
> 192.168.21.0/24
>
> Is it possible to reflect them in my masq rule ?
my only point was that since you don't actually do any *_filtering_* in
your filter rules, and allow all traffic to be MASQ'd to a public IP,
that there would be nothing stopping a client from doing whatever they
wanted to do--which was your original question.
if you actually *_filter_* traffic in the filter chains, there's nothing
wrong with having an outbound SNAT/MASQ rule that matches all traffic,
as only packets that pass through the filters will ever make it that
far.
i would suggest you go read:
http://iptables-tutorial.frozentux.net/iptables-tutorial.html
seven times.
-j
--
"Salesman: Well, we found out what the problem with your vacuum
cleaner was: Apparently there was a meatball lodged inside.
Peter: Did you save the meatball?
Salesman: Ummm, no...?
Peter: You bastard."
--Family Guy
prev parent reply other threads:[~2005-05-01 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 14:13 Re - NAT to client varun_saa
2005-05-01 21:58 ` Jason Opperisano [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=20050501215802.GA8642@bender.817west.com \
--to=opie@817west.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox