From: Frank Gruellich <frank@home.manuelm.org>
To: netfilter@lists.netfilter.org
Subject: Re: block port 137
Date: Tue, 3 Aug 2004 11:16:58 +0200 [thread overview]
Message-ID: <20040803091658.GC1067@der-frank.org> (raw)
In-Reply-To: <1091518405.4693.15.camel@dc.nucleussoftware.com>
* Dhananjoy Chowdhury <dhananjoy@nucleussoftware.com> 3. Aug 04:
> On Tue, 2004-08-03 at 11:47, Antony Stone wrote:
> > On Tuesday 03 August 2004 7:04 am, Dhananjoy Chowdhury wrote:
> > > try dropping packets both with dport 137 and also with sport 137.
> > I disagree.
Me too.
> Your terminology is very much true but David has already applied the
> rule
> #iptables -A FORWARD -p udp -s 0/0 --dport 137 -j DROP
> but then also he isn't able to stop output traffic through port 137.
> So in this scenario he should appply the above rule for both --sport
> and --dport.
> #iptables -I FORWARD -p udp -s 0/0 --dport 137 -j DROP
> #iptables -I FORWARD -p udp -s 0/0 --sport 137 -j DROP
Well, from my point of view he should add to these rules:
# iptables -P FORWARD DROP
# iptables -F FORWARD
Then he should fix his network by imaging compromised hosts for further
analysis, flatting them and installing them from trusted sources. Later
he should look for an appropriate L.A.R.T. for the users of the machines
and maybe go online again.
YMMV,
regards, Frank.
--
Sigmentation fault
next prev parent reply other threads:[~2004-08-03 9:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 0:20 SMB auth and Iptables Steve Wakelin
[not found] ` <"002401c 4 7917$d0a6fd70$858310ac"@suarapembaruan.com>
2004-08-03 5:07 ` block port 137 david
2004-08-03 6:04 ` Dhananjoy Chowdhury
2004-08-03 6:17 ` Antony Stone
2004-08-03 7:33 ` Dhananjoy Chowdhury
2004-08-03 8:41 ` Antony Stone
2004-08-03 9:16 ` Frank Gruellich [this message]
2004-08-04 3:00 ` david
2004-08-04 7:03 ` Antony Stone
2004-08-04 10:01 ` david
2004-08-04 7:41 ` Frank Gruellich
2004-08-03 6:15 ` Antony Stone
2004-08-03 18:31 ` Zoup
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=20040803091658.GC1067@der-frank.org \
--to=frank@home.manuelm.org \
--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 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.