Date: Thu, 16 Dec 1999 06:41:11 -0800 (PST) From: matheny@cs.purdue.edu To: freebsd-gnats-submit@freebsd.org Subject: misc/15515: Firewall/FIltering Problems Message-ID: <19991216144111.C1F2F14E17@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 15515 >Category: misc >Synopsis: Firewall/FIltering Problems >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Dec 16 06:50:01 PST 1999 >Closed-Date: >Last-Modified: >Originator: Blake Matheny >Release: 3.3 i386 >Organization: Purdue University >Environment: FreeBSD newfirewall.sdatebooks.com 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Thu Oct 7 13:37:40 EST 1999 root@sdatebooks.com:/usr/src/sys/compile/FIREWALL i386 >Description: On a freebsd 3.3 firewall the ipfw rule is set to open. However, ports 137-139 appear as filtered when a portscan is done. We have checked with the DSL provider and the DSL modem manufacturer to see if the modem has filtering capabilities or the service provider filters and the answer to these questions was no. Question: Why would the ports come back with filtered if were not using a tcp wrapper and the firewall type is open? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991216144111.C1F2F14E17>