From owner-freebsd-hackers Fri Jun 4 8:42:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id EBE0415491 for ; Fri, 4 Jun 1999 08:42:47 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id LAA05300 for ; Fri, 4 Jun 1999 11:42:45 -0400 (EDT) Message-Id: <199906041542.LAA05300@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 04 Jun 1999 10:39:18 -0400 To: hackers@freebsd.org From: Dennis Subject: Continuing 3.x woes Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There seems to be a socket-level problem with 3.x...I havent tested it in 3.1 yet but I do see it in 3.2. 2 Freebsd boxes connected back to back...one is 2.2.8 and the other is 3.2. The 2.2.8 machine is pinging the 3.2 machine...the link is brought down. The 2.2.8 machine starts printing "sendto: network down" messages until the 3.2 machine is brought back up, and then pinging resumes normally. However, when pinging from the 3.2 machine, the 2.2.8 machine is brought down and the 3.2 machine just stops (no messages as if it doesnt detect the link down)....then when the 2.2.8 machine is brought back up the ping does not resume. A new ping session from the 3.2 box works normally indicating the the link is working properly. It seems that something was done, perhaps to eliminate the "Sendto" messages that keeps applications from coming back up if the link goes down and comes back up. This is pretty bad if major network services exhibit the same behaviour. Anyone have any ideas? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message