From: Tom van Leeuwen <tom.van.leeuwen@saasplaza.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: "C. L. Martinez" <carlopmart@gmail.com>,
"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Problems with a forward rule
Date: Sat, 12 May 2012 22:53:14 +0200 [thread overview]
Message-ID: <4FAECDBA.9030302@saasplaza.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1205121746300.5922@frira.vanv.qr>
Indeed do iptables-save for the complete ruleset and tell us what you
want and expect.
On 12-5-2012 17:47, Jan Engelhardt wrote:
> On Friday 2012-05-11 17:04, C. L. Martinez wrote:
>
>> Hi all,
>>
>> I have setup the following rules in a centos6 gateway:
>> [ugly iptables -L]
> *Use* iptables-save and provide a *full* ruleset.
>
>> All works ok, except when I try to restrict one host to go out via
>> external interface. My problem is with the following rule:
>>
>> 0 0 ACCEPT all -- * * 172.24.50.3
>> 0.0.0.0/0 state NEW
>>
>> If I try to restrict destination, doesn't works. For example using this rule:
>>
>> iptables -A FORWARD -s 172.24.50.3 -d 1.1.1.0/24 -m state --state NEW -j ACCEPT
>>
>> only works if I do:
>>
>> iptables -A FORWARD -s 172.24.50.3 -m state --state NEW -j ACCEPT
>>
>> then, what am I doing wrong??
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-05-12 20:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 15:04 Problems with a forward rule C. L. Martinez
2012-05-12 15:47 ` Jan Engelhardt
2012-05-12 20:53 ` Tom van Leeuwen [this message]
2012-05-14 5:45 ` C. L. Martinez
2012-05-14 6:33 ` Tom van Leeuwen
2012-05-14 6:40 ` C. L. Martinez
2012-05-14 7:03 ` Tom van Leeuwen
2012-05-14 7:06 ` C. L. Martinez
2012-05-14 7:24 ` Tom van Leeuwen
2012-05-14 16:47 ` carlopmart
2012-05-14 7:26 ` Neal Murphy
2012-05-14 8:18 ` C. L. Martinez
2012-05-14 17:55 ` Neal Murphy
2012-05-14 19:35 ` carlopmart
2012-05-14 21:12 ` Neal Murphy
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=4FAECDBA.9030302@saasplaza.com \
--to=tom.van.leeuwen@saasplaza.com \
--cc=carlopmart@gmail.com \
--cc=jengelh@inai.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox