Return-Path: william@bourbon.usc.edu Delivery-Date: Thu Oct 23 22:47:41 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m9O5leOM030883 for ; Thu, 23 Oct 2008 22:47:40 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m9O5vib0009000 for ; Thu, 23 Oct 2008 22:57:44 -0700 Message-Id: <200810240557.m9O5vib0009000@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: keepalive Date: Thu, 23 Oct 2008 22:57:44 -0700 From: Bill Cheng Someone wrote: > I understand that you have to send a KeepAlive message (or any other message > on that socket) every (keepalive/2) seconds. > > But what should be the course of action if you do not hear anything > (messages or keepalives) from one of your neighbors for a keepalive timeout, > will you terminate the connection with the neighbor ? Yes. That connection is considered dead. -- Bill Cheng // bill.cheng@usc.edu