From owner-freebsd-security@FreeBSD.ORG Wed Apr 21 13:35:49 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE67516A4CF for ; Wed, 21 Apr 2004 13:35:48 -0700 (PDT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA3EB43D45 for ; Wed, 21 Apr 2004 13:35:48 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (8.12.6/MantshX 2.0) with ESMTP id i3LKZmZe022665; Wed, 21 Apr 2004 13:35:48 -0700 (PDT) Received: from [10.1.1.193] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)i3LKZl3Z024557; Wed, 21 Apr 2004 13:35:47 -0700 (PDT) In-Reply-To: <6.0.3.0.0.20040421161217.05453308@209.112.4.2> References: <6.0.3.0.0.20040420125557.06b10d48@209.112.4.2> <6.0.3.0.0.20040420144001.0723ab80@209.112.4.2> <200404201332.40827.dr@kyx.net> <20040421111003.GB19640@lum.celabo.org> <6.0.3.0.0.20040421121715.04547510@209.112.4.2> <20040421165454.GB20049@lum.celabo.org> <6.0.3.0.0.20040421132605.0901bb40@209.112.4.2> <48FCF8AA-93CF-11D8-9C50-000393C94468@sarenet.es> <6.0.3.0.0.20040421161217.05453308@209.112.4.2> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <75226E9B-93D3-11D8-90F9-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 21 Apr 2004 16:35:41 -0400 To: Mike Tancsa X-Mailer: Apple Mail (2.613) cc: freebsd-security@freebsd.org Subject: Re: Other possible protection against RST/SYN attacks (was Re: TCP RST attack X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2004 20:35:49 -0000 On Apr 21, 2004, at 4:14 PM, Mike Tancsa wrote: > What side effects if any are there? Why is the default 64 and not > some other number like 255... The default TTL gets decremented with every hop, which means that a packet coming in with a TTL of 255 had to be sent by a directly connected system. [ip_ttl is an octet, so it can't hold a larger TTL value.] A packet with a TTL of 64 could have been many hops away. -- -Chuck