From owner-freebsd-security Fri Nov 17 17:26:45 2000 Delivered-To: freebsd-security@freebsd.org Received: from mail.kyx.net (unknown [24.113.50.147]) by hub.freebsd.org (Postfix) with ESMTP id B3B8F37B4C5 for ; Fri, 17 Nov 2000 17:26:35 -0800 (PST) Received: from smp.kyx.net (unknown [10.22.22.45]) by mail.kyx.net (Postfix) with SMTP id 9105B1DC09; Fri, 17 Nov 2000 17:29:46 -0800 (PST) From: Dragos Ruiu Organization: kyx.net To: nate@yogotech.com (Nate Williams), Nate Williams , Buliwyf McGraw Subject: Re: Napster Port Date: Fri, 17 Nov 2000 17:24:06 -0800 X-Mailer: KYX-CP/M [version core00-mail-92] Content-Type: text/plain Cc: security@FreeBSD.ORG References: <14869.55781.674921.949509@nomad.yogotech.com> In-Reply-To: <14869.55781.674921.949509@nomad.yogotech.com> MIME-Version: 1.0 Message-Id: <00111717251704.29995@smp.kyx.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Napster protocol description: url: http://opennap.sourceforge.net/napster.txt cheers, --dr On Fri, 17 Nov 2000, Nate Williams wrote: > > Hi to everyone! > > This is my question: > > - I want to deny all access to Napster from my subnet. I'm using ip > > filter... but i dont know what is the port that i need to block... > > Any sugestion about the right rule in my gateway??? > > This is the best I've got so far... > > # Disable Napster > /sbin/ipfw add 600 deny log tcp from any to 208.178.163.56/29 via ${netif} > /sbin/ipfw add 610 deny log tcp from any to 208.178.175.128/29 via ${netif} > /sbin/ipfw add 620 deny log tcp from any to 208.49.239.240/28 via ${netif} > /sbin/ipfw add 630 deny log tcp from any to 208.49.228.0/24 via ${netif} > /sbin/ipfw add 640 deny log tcp from any to 208.184.216.0/24 via ${netif} > /sbin/ipfw add 650 deny log tcp from any to 64.124.41.0/24 via ${netif} > /sbin/ipfw add 660 deny log tcp from any 8888 to any via ${netif} > > {where 'netif' is the network interface for the internet} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message