Bug 15515
| Summary: | Firewall/FIltering Problems | ||
|---|---|---|---|
| Product: | Base System | Reporter: | matheny <matheny> |
| Component: | misc | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
matheny
1999-12-16 14:50:01 UTC
On Thu, Dec 16, 1999 at 06:41:11AM -0800, matheny@cs.purdue.edu wrote: > > On a freebsd 3.3 firewall the ipfw rule is set to open. However, > ports r137-139 appear as filtered when a portscan is done. > What do you mean by "appear as filtered"? > 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? > Either you're using non-stock version of /etc/rc.firewall, or nothing is listening on 137-139. What do the following commands output: # ipfw show # netstat -an -finet | awk '$4 ~ "13[7-9]$" {print $0}' Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age State Changed From-To: open->closed Cannot reproduce, and originator does not respond within a reasonable amount of time (one month). Believed to be a pilot error. |
