Acee Lindem <acee@raleigh.ibm.com> Thu, 21 November 1996 17:13 UTC
Received: from cnri by ietf.org id aa14585; 21 Nov 96 12:13 EST
Received: from merit.edu by CNRI.Reston.VA.US id aa14171; 21 Nov 96 12:13 EST
Received: (from daemon@localhost) by merit.edu (8.7.6/merit-2.0) id LAA11432
for idr-outgoing; Thu, 21 Nov 1996 11:41:53 -0500 (EST)
Received: from interlock.ans.net (interlock.ans.net [147.225.5.5]) by
merit.edu (8.7.6/merit-2.0) with SMTP id LAA11423 for <bgp@merit.edu>;
Thu, 21 Nov 1996 11:41:50 -0500 (EST)
Received: by interlock.ans.net id AA09134
(InterLock SMTP Gateway 3.0 for bgp@ans.net);
Thu, 21 Nov 1996 11:41:47 -0500
Received: by interlock.ans.net (Internal Mail Agent-3);
Thu, 21 Nov 1996 11:41:47 -0500
Received: by interlock.ans.net (Internal Mail Agent-2);
Thu, 21 Nov 1996 11:41:47 -0500
Received: by interlock.ans.net (Internal Mail Agent-1);
Thu, 21 Nov 1996 11:41:47 -0500
Message-Id: <9611211642.AA14872@heavens-gated.raleigh.ibm.com>
To: May Tang <May_Tang@baynetworks.com>
Cc: bgp@ans.net
Reply-To: acee@raleigh.ibm.com
Date: Thu, 21 Nov 96 11:42:13 -0500
From: Acee Lindem <acee@raleigh.ibm.com>
Sender: owner-idr@merit.edu
Precedence: bulk
-------- May_Tang@baynetworks.com (May Tang) writes: > Does anyone know what is a " bad seg " TCP packet ?? > It mostly likely means you received a TCP packet with data (send sequence number plus length) that does not fall within the expected window of the session logging the error. Acee