From owner-freebsd-security  Tue Oct  6 01:13:22 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA29273
          for freebsd-security-outgoing; Tue, 6 Oct 1998 01:13:22 -0700 (PDT)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29267
          for <freebsd-security@FreeBSD.ORG>; Tue, 6 Oct 1998 01:13:21 -0700 (PDT)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
	by time.cdrom.com (8.8.8/8.8.8) with ESMTP id BAA17500;
	Tue, 6 Oct 1998 01:13:22 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: "Jan B. Koum " <jkb@best.com>
cc: freebsd-security@FreeBSD.ORG
Subject: Re: Negative IP Packets - Risky? (fwd) 
In-reply-to: Your message of "Tue, 06 Oct 1998 00:57:46 PDT."
             <Pine.BSF.4.02A.9810060054010.651-100000@shell6.ba.best.com> 
Date: Tue, 06 Oct 1998 01:13:22 -0700
Message-ID: <17497.907661602@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> By sending negative IP packets to a network, you can crash the server.

Ah yes, the old negative IP packets.  There's nothing worse than a
packet with a BAD ATTITUDE and those negative ones can be downright
gloomy.  I filter them with HappyBridge(R) 1.0.

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message