From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: netfilter@vger.kernel.org
Subject: Re: Rules PREROUTING doesn't work
Date: Wed, 17 Mar 2010 08:14:43 -0500 [thread overview]
Message-ID: <hnqkk4$62v$1@dough.gmane.org> (raw)
In-Reply-To: <1c1b5a0f1003162027s73fe4756yefd48b436375b04b@mail.gmail.com>
On 03/16/2010 10:27 PM, Angel Motta wrote:
> Hi List
> This is my first time the I write to this list. I have a problem case
> with rules PREROUTING.
> I am creating a rule PREROUTING from a range of port which request
> openvpn client and the problem is that when I apply this rules and
> only rules NATs are runing (PREROUTING and POSTROUTING the output of
> #> iptables -L is blank) the clients openvpn still conect to the
> Firewall and not to the SERVERVPN, all requests are processed for
> firewall.
>
> this is the rule:
> $IPT -t nat -A PREROUTING -i $IF_EXT -d $TESTVPN -p udp --dport
> 5000:6000 -j DNAT --to-destination $IP_DMZ_SERVERVPN
That listing command needs to be "iptables -t nat -L". The default is
to display only the filter table, which doesn't include the above rule.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
next prev parent reply other threads:[~2010-03-17 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 3:27 Rules PREROUTING doesn't work Angel Motta
2010-03-17 6:21 ` Michele Petrazzo - Unipex
2010-03-17 13:14 ` Robert Nichols [this message]
2010-03-17 13:20 ` Jan Engelhardt
2010-03-17 15:20 ` Angel Motta
2010-03-17 20:25 ` Richard Horton
2010-03-18 0:20 ` Robert Nichols
2010-03-18 1:14 ` Jan Engelhardt
2010-03-18 4:48 ` Robert Nichols
2010-03-18 5:53 ` Angel Motta
2010-03-18 11:15 ` Mart Frauenlob
2010-03-18 15:36 ` Angel Motta
[not found] ` <1268931387.3763.31.camel@casper.meteor.dp.ua>
2010-03-19 5:11 ` Angel Motta
2010-03-19 8:01 ` Mart Frauenlob
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='hnqkk4$62v$1@dough.gmane.org' \
--to=rnicholsnospam@comcast.net \
--cc=netfilter@vger.kernel.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.