Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "david" <david@suarapembaruan.co.id>
To: netfilter@lists.netfilter.org
Subject: Re: block port 137
Date: Wed, 4 Aug 2004 10:00:30 +0700	[thread overview]
Message-ID: <00d601c479cf$352a91f0$858310ac@suarapembaruan.com> (raw)
In-Reply-To: 200408030717.59289.Antony@Soft-Solutions.co.uk

Dear Antony,
I agree with you, i must block all traffic and accept one-by-one rules that
i want, but the problem is i don't know how to do this ...., btw.. this in
my rules

iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to-source 202.46.146.161
iptables -t nat -A PREROUTING -p tcp -i eth0 -d 202.46.146.164 --dport
110 -j DNAT --to 172.16.128.50
iptables -t nat -A PREROUTING -p tcp -i eth0 -d 202.46.146.164 --dport 25 -j
DNAT --to 172.16.128.50
iptables -t nat -A PREROUTING -p tcp -i eth0 -d 202.46.146.165 --dport 25 -j
DNAT --to 172.16.128.125
iptables -t nat -A PREROUTING -p tcp -i eth0 -d 202.46.146.165 --dport
110 -j DNAT --to 172.16.128.125
iptables -t nat -A PREROUTING -p tcp -i eth0 -d 202.46.146.166 --dport 80 -j
DNAT --to 172.16.131.6
iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -t nat -A PREROUTING -p tcp -i eth0 -d 202.46.146.167 --dport 21 -j
DNAT --to 172.16.128.79bie
iptables -t nat -A PREROUTING -p tcp -i eth0 -d 202.46.146.168 --dport 21 -j
DNAT --to 172.16.131.29

iptables -A FORWARD -p udp -s 0/0 --dport 137 -j DROP

I know this rules is very weak.... can you help me to make my firewall
strongger......

Thank's a lot

David Kandou
Newbie

----- Original Message ----- 
From: "Antony Stone" <Antony@Soft-Solutions.co.uk>
To: <netfilter@lists.netfilter.org>
Sent: Tuesday, August 03, 2004 1:17 PM
Subject: Re: block port 137


> 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.
>
> Try ACCEPTing the packets you *want* to go through the firewall, and DROP
> everything else.
>
> Don't create individual rules to DROP the traffic you think you don't want
> (you will always forget something, or there will be a new problem next
week
> which requires a new rule, etc).
>
> Instead create individual rules to ACCEPT the traffic you need, and DROP
> anything which doesn't fit that description.
>
> Regards,
>
> Antony.
>
> > On Tue, 2004-08-03 at 10:37, david wrote:
> > > Dear all,
> > > How to block outgoing traffic over network that using port 137 udp,
> > > because my isp tell me that my network broadcast virus using port 137
> > > udp, i want to make all traffic (port 137) do go outside my network,
> > > so i plan to blocking that traffic from my gateway.
> > >
> > > I already try to do this rules, but not working :
> > > #iptables -A FORWARD -p udp -s 0/0 --dport 137 -j DROP
> > >
> > >
> > >
> > >
> > > Regards,
> > > David Kandou
>
> -- 
> If builders made buildings the way programmers write programs, then the
first
> woodpecker to come along would destroy civilisation.
>
>                                                      Please reply to the
list;
>                                                            please don't CC
me.
>
>
>



  parent reply	other threads:[~2004-08-04  3:00 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
2004-08-04  3:00       ` david [this message]
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='00d601c479cf$352a91f0$858310ac@suarapembaruan.com' \
    --to=david@suarapembaruan.co.id \
    --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