Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!seismo!nbires!opus!chm From: chm@opus.UUCP Newsgroups: comp.protocols.tcp-ip Subject: 4.3 TCP keep-alive question Message-ID: <751@opus.UUCP> Date: Mon, 13-Apr-87 18:31:09 EST Article-I.D.: opus.751 Posted: Mon Apr 13 18:31:09 1987 Date-Received: Wed, 15-Apr-87 03:59:46 EST Organization: NBI Inc., Boulder, CO. Lines: 25 Keywords: TCP keep-alive The 4.2 TCP keep-alive implementation is described two different ways. According to the comment in tcp_timer.h, when the TCPT_KEEP timer expires we should send the following segment to elicit a response from our peer: But, the actual implementation in our version of tcp_timer.c sends: Note that the first segment contains an invalid SEQ and the second contains both an invalid SEQ and an invalid ACK. My question is, do we really need to lie about what we've received by sending an invalid ACK or is the invalid SEQ enough to elicit a response? -- Paul Chmielewski NBI Inc., Boulder, CO chm@nbires.UUCP or chm@nbires.NBI.COM (303) 444-5710 -- Paul Chmielewski NBI Inc., Boulder, CO chm@nbires.UUCP or chm@nbires.NBI.COM (303) 444-5710