From: George Alexandru Dragoi <waruiinu@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: another quick question
Date: Mon, 20 Sep 2004 11:48:04 +0300 [thread overview]
Message-ID: <3063e5040920014819196810@mail.gmail.com> (raw)
In-Reply-To: <a0f69e50409200102455b0172@mail.gmail.com>
It is strongly related to the other question, same RPC/DCOM problems.
On Mon, 20 Sep 2004 14:02:57 +0600, Askar <askarali@gmail.com> wrote:
> hi again
> My second question of the day is pls first check these few rules from
> our firewall scirpt
>
> iptables -A INPUT -p TCP -s 0/0 -d 0/0 --dport 135:140 -j DROP
> iptables -A INPUT -p UDP -s 0/0 -d 0/0 --dport 135:140 -j DROP
> iptables -A FORWARD -p TCP -s 0/0 -d 0/0 --dport 135:140 -j DROP
> iptables -A FORWARD -p UDP -s 0/0 -d 0/0 --dport 135:140 -j DROP
> iptables -t nat -A PREROUTING -p TCP -s 0/0 -d 0/0 --dport 135:140 -j DROP
> iptables -t nat -A PREROUTING -p UDP -s 0/0 -d 0/0 --dport 135:140 -j DROP
>
> aren't there are unnecessary repitions ? port that is Dropped in
> FOWARD chain is again Dropped in PREROUTING chain, and also why he (my
> predecssor) droping such port in INPUT table ? aren't it unnecessary,
> coz it a linux box no port 135:140 are open on our fw machine.
>
> Today I just deletes are PREROUTING rules and now im getting counts
> for packets drops on FOWARD table.
>
> regards
> askar
>
> --
> (after bouncing head on desk for days trying to get mine working, I'll make
> yer life a little easier)
>
>
--
Bla bla
next prev parent reply other threads:[~2004-09-20 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 8:02 another quick question Askar
2004-09-20 8:48 ` George Alexandru Dragoi [this message]
2004-09-20 10:02 ` Chris Brenton
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=3063e5040920014819196810@mail.gmail.com \
--to=waruiinu@gmail.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