All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom van Leeuwen <tom.van.leeuwen@saasplaza.com>
To: "C. L. Martinez" <carlopmart@gmail.com>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Problems with a forward rule
Date: Mon, 14 May 2012 08:33:22 +0200	[thread overview]
Message-ID: <4FB0A732.4070909@saasplaza.com> (raw)
In-Reply-To: <CAEjQA5LAwmxTwAGWJH5A5Bs57h8=BSXWwiWegYmVKSM7ZtvtmA@mail.gmail.com>

Alright,
Judging your ruleset the only relevant lines for your host 172.24.50.3 
would be:

:FORWARD DROP [2:80]
-A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s 172.24.50.3/32 -m state --state NEW -j ACCEPT
-A FORWARD -j LOG --log-prefix "IPT FORWARD packet died: "

And you said that restricting destination does not work. Your rule:
iptables -A FORWARD -s 172.24.50.3 -d 1.1.1.0/24 -m state --state NEW -j 
ACCEPT

You say it does not work. If that is the case, your packets are logged 
and dropped.
Could you paste the log entries for your host 172.24.50.3?

On 05/14/2012 07:45 AM, C. L. Martinez wrote:
> On Sat, May 12, 2012 at 10:53 PM, Tom van Leeuwen
> <tom.van.leeuwen@saasplaza.com>  wrote:
>> 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.
>>>
> Ok, here they are. I want to allow connections from host 172.24.50.3
> to one specific network only.

  reply	other threads:[~2012-05-14  6:33 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
2012-05-14  5:45     ` C. L. Martinez
2012-05-14  6:33       ` Tom van Leeuwen [this message]
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=4FB0A732.4070909@saasplaza.com \
    --to=tom.van.leeuwen@saasplaza.com \
    --cc=carlopmart@gmail.com \
    --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.