From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: block port 137
Date: Tue, 3 Aug 2004 09:41:11 +0100 [thread overview]
Message-ID: <200408030941.11162.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <1091518405.4693.15.camel@dc.nucleussoftware.com>
On Tuesday 03 August 2004 8:33 am, Dhananjoy Chowdhury wrote:
> On Tue, 2004-08-03 at 11:47, Antony Stone wrote:
> >
> > I disagree.
> >
> > Try ACCEPTing the packets you *want* to go through the firewall, and DROP
> > everything else.
>
> 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
That is not the same rule as "iptables -I FORWARD......"
I suspect he has a rule somewhere in the ruleset which is allowing the packets
(perhaps based on source address?), which adding a rule at the end will not
solve. Putting the DROP rule at the top of the ruleset makes a big
difference.
If the problem is packets to random destination ports, *from* UDP port 137,
then it doesn't sound like what the ISP originally complained about, and
what's the threat anyway (since destination port is what matters in terms of
vulnerabilities and exploits)?
Regards,
Antony.
--
If the human brain were so simple that we could understand it,
we'd be so simple that we couldn't.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-08-03 8:41 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 [this message]
2004-08-03 9:16 ` Frank Gruellich
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=200408030941.11162.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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