From owner-freebsd-hackers Sun Jun 4 17:11:33 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA23023 for hackers-outgoing; Sun, 4 Jun 1995 17:11:33 -0700 Received: from rover.village.org (rover.village.org [198.137.146.49]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA22916 for ; Sun, 4 Jun 1995 17:11:00 -0700 Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.11/8.6.6) with SMTP id SAA03549; Sun, 4 Jun 1995 18:05:52 -0600 Message-Id: <199506050005.SAA03549@rover.village.org> To: PowerTrip@aol.com Subject: Re: I call it the "NT sniper bug". (fwd) Cc: julian@tfs.com, hackers@FreeBSD.ORG, tonym@citrix.com In-reply-to: Your message of Fri, 02 Jun 1995 23:34:31 EDT Date: Sun, 04 Jun 1995 18:05:51 -0600 From: Warner Losh Sender: hackers-owner@FreeBSD.ORG Precedence: bulk : (under , , select the items, and check them out. (may : be as "TCP/IP", or "SIMPLE TCP/IP:, or as WINS : and DHCP. can't remember off hand. I can check at work monday. : we have 5 NT Server 3.5 servers, with IP being used, and : 4 Tektronix X-Terminals, and all seems ok so far. I believe that the original poster in comp.protocols.tcp-ip said that it was basically a bug in NT with a SMC Ultra Elite where it would sometimes pass up to the NT stack packets that weren't for the Ultra's MAC. NT would get confused and send out the sniper packet.... Warner