From owner-freebsd-hackers Fri Jun 12 07:39:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21502 for freebsd-hackers-outgoing; Fri, 12 Jun 1998 07:39:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21460 for ; Fri, 12 Jun 1998 07:39:34 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id HAA11334; Fri, 12 Jun 1998 07:39:28 -0700 (PDT) (envelope-from jdp) Message-Id: <199806121439.HAA11334@austin.polstra.com> To: hans@brandinnovators.com Subject: Re: TCP sequence numbers In-Reply-To: <199806120831.KAA00529@truk.brandinnovators.com> References: <199806120831.KAA00529@truk.brandinnovators.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Fri, 12 Jun 1998 07:39:28 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199806120831.KAA00529@truk.brandinnovators.com>, Hans Zuidam wrote: > For a particularly nasty TCP problem I have with an embedded target > I would like to have the ability to always use the same initial > sequence number on a particular connection. It would make it easier > to compare tcpdump traces. Are you sure? Tcpdump prints TCP sequence numbers in relative form, relative to the initial one, unless you give it the "-S" option. Your traces should match already, except for the initial packet from each side. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message