On 02/22/03 03:27 PM, Louis LeBlanc sat at the `puter and typed:
> > <SNIP>
>
> I did notice one interesting thing. When I reconfigured Apache to
> listen on port 8080, it worked fine. What I only just realized, is
> that I never put a rule in the firewall to explicitly open port 8080.
This was because of a firewall rule that should have opened every port
to the machine in particular. When that rule was commented out, the
firewall looked like this:
For OSScan assuming that port 21 is open and port 113 is closed and
neither are firewalled
Interesting ports on pool-68-160-158-62.bos.east.verizon.net
(68.160.158.62):
(The 1592 ports scanned but not shown below are in state: filtered)
Port State Service
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
113/tcp closed auth
143/tcp open imap2
443/tcp open https
993/tcp open imaps
8080/tcp open http-proxy
27374/tcp closed subseven
This is more like what I want it to look like, but port 80 still seems
to be filtered. But what the heck is filtered? I don't explicitly
block any ports until the last line of the firewall script:
${fwcmd} add 65000 deny ip from any to any in via ${oif}
So if I change deny to reset, will that give me an idea what ports are
filtered by me and what is filtered by the ISP?
Lou
--
Louis LeBlanc [EMAIL PROTECTED]
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://www.keyslapper.org ԿԬ
Finagle's Eleventh Law:
No matter what occurs, someone believes it happened according to
his pet theory.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
