From: Georgi Alexandrov <tehlists@hotpop.com>
To: netfilter@lists.netfilter.org
Subject: Re: is there a way to discriminate the ESTABLISHED traffic?
Date: Mon, 04 Apr 2005 15:11:14 +0300 [thread overview]
Message-ID: <42512EE2.1090603@hotpop.com> (raw)
In-Reply-To: <425124D1.3080501@lorenzutti.com.ar>
Guido Lorenzutti wrote:
> Georgi Alexandrov wrote:
>
>> Guido Lorenzutti wrote:
>>
>>> How can i discriminate the traffic that my firewall is answering
>>> from a NEW request from a network from the ESTABLISHED traffic that
>>> my firewall is making from a NEW request from him?
>>>
>>> In rules, to allow traffic TO my box from the lan 10.0.0.0/32
>>>
>>> 1 ipt -A INPUT -s 10.0.0.0/32 -m state --state NEW -j ACCEPT
>>> 2 ipt -A INPUT -s 10.0.0.0/32 -m state --state ESTABLISHED -j ACCEPT
>>> 3 ipt -A OUTPUT -d 10.0.0.0/32 -m state --state ESTABLISHED -j ACCEPT
>>>
>>> Now, to allow traffic FROM my box to the lan 10.0.0.0/32
>>>
>>> 4 ipt -A OUTPUT -d 10.0.0.0/32 -m state --state NEW -j ACCEPT
>>> 5 ipt -A OUTPUT -d 10.0.0.0/32 -m state --state ESTABLISHED -j ACCEPT
>>> 6 ipt -A INPUT -s 10.0.0.0/32 -m state --state ESTABLISHED -j ACCEPT
>>>
>>> The 3 and 5 rules are exactly the same. Is there a way to
>>> discriminate this or the things are just like this and there is
>>> nothing to do about it?
>>>
>>> Tnxs in advance.
>>>
>>>
>> btw 10.0.0.0/32 ?!
>>
>>
>
> Yeah.. what? I make my 10.0.0.0 subnet a class C :) It's Ok to do
> that, try it!! :P
>
You probably mean 10.0.0.0/24 then ?
regards,
Georgi Alexandrov
prev parent reply other threads:[~2005-04-04 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:51 is there a way to discriminate the ESTABLISHED traffic? Guido Lorenzutti
2005-04-04 3:46 ` Grant Taylor
2005-04-04 8:17 ` John A. Sullivan III
2005-04-04 13:10 ` Jozsef Kadlecsik
2005-04-04 9:00 ` Georgi Alexandrov
[not found] ` <425124D1.3080501@lorenzutti.com.ar>
2005-04-04 12:11 ` Georgi Alexandrov [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=42512EE2.1090603@hotpop.com \
--to=tehlists@hotpop.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