From owner-freebsd-current Sun Mar 10 13:09:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19520 for current-outgoing; Sun, 10 Mar 1996 13:09:24 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA19513 for ; Sun, 10 Mar 1996 13:09:20 -0800 (PST) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id NAA09871; Sun, 10 Mar 1996 13:07:08 -0800 (PST) Message-Id: <199603102107.NAA09871@precipice.shockwave.com> To: Andrew Foster cc: current@FreeBSD.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Sun, 10 Mar 1996 21:46:05 -1000." <2.2.32.19960311074605.00a4bb08@mail.fl.net.au> Date: Sun, 10 Mar 1996 13:07:08 -0800 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Your xylogics terminal server has a broken TCP implementation, it can't handle transaction tcp apparently. You can turn off tcp extensions, but I'd send them a bug report with a tcpdump of the conversation and explicitly note that you are sending a SYN packet with data and a FIN. Paul From: Andrew Foster Subject: finger and 2.2-960303-SNAP Hi, It seems that finger is broken (partially) in this SNAP. I cannot finger my Xylogics Remote Annex 4000, but other hosts seem to work. I receive : [annex1.fl.net.au] finger: read: Connection reset by peer However, telnetting to the finger port works fine, as does running finger on a 2.1.0-R system. I have run the 2.1.0-R binary on this SNAP and it works fine (and does not have the Connection reset by peer error). The finger output is quite long for that site - feel free to try it out yourself. Thanks, Andrew ----------- Andrew Foster Sydney, Australia