Warning: overlong message.
I'm moving this to questions@ from security@ as it's a usage issue.
Anyone wishing to follow the up to here can read from:
http://lists.freebsd.org/pipermail/freebsd-security/2007-December/004541.html
On Fri, 21 Dec 2007, W. D. wrote:
> Date: Fri, 21 Dec 2007 01:30:1
At 08:49 12/22/2007, Ian Smith wrote:
>Warning: overlong message.
> > > > >W. D. wrote:
> > OK, sorry. I guess I just assumed that it would be obvious
> > that this is a Web server. ("Never assume anything, my good
> > fellow" - Sherlock Holmes).
> > By the way, it is/will be running Plesk
On Sat, 29 Dec 2007, W. D. wrote:
> At 08:49 12/22/2007, Ian Smith wrote:
> >Warning: overlong message.
> > > > > >W. D. wrote:
[.. slashing mercilessly ..]
> >Ok, so your nameserver will be making upstream requests too, and you'll
> >need to do TCP 53 traffic with your secondary nameserver/
At 08:34 12/30/2007, Ian Smith, wrote:
>On Sat, 29 Dec 2007, W. D. wrote:
> > At 08:49 12/22/2007, Ian Smith wrote:
> > >Warning: overlong message.
> > >access to only your LAN. Will this webserver later have a public IP
> > >address, or run behind NAT with port forwarding?
> >
> > Public IP.
>
I don't think that below shall ever replace this:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-ipfw.html
---
#1. i suggest you should really consider moving check-state earlier so
legitimate packets get in asap.
#2. its never too late to start using tables
#/sbin/ipfw tabl
>Date: Sun, 23 Dec 2007 06:04:02 -0800 (PST)
>From: Nash Nipples <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: IPFW: Blocking me out. How to debug?
>
>Dear W.D.
>
>oh come on. i have the same problem.
Which problem are we talking about?
>cut and pas
