From owner-freebsd-questions Thu Sep 19 00:47:09 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA26498 for questions-outgoing; Thu, 19 Sep 1996 00:47:09 -0700 (PDT) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA26398 for ; Thu, 19 Sep 1996 00:46:59 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.7.6/8.7.3) id RAA20172; Thu, 19 Sep 1996 17:16:47 +0930 (CST) Date: Thu, 19 Sep 1996 17:16:47 +0930 (CST) From: Peter Childs Message-Id: <199609190746.RAA20172@al.imforei.apana.org.au> To: mcw@hpato.aus.hp.com, freebsd-questions@freebsd.org Subject: Re: odd problem with 2.1R NNTP access X-Newsreader: TIN [version 1.2 PL2] Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199609190222.AA191889729@hp.com> you wrote: : RFC1373 is about DUAs, how does that affect NNTP ? : Or is it a side effect of RFC1373 implementation into 2.1R ? Some hardware doesn't handle, or handles incorrectly the TCP extensions available. Stuff like the annex 4000 at the melbourne apana hub just (in my experience) screws connections up. Other known mishandlers of these extensions are linux machines (someone posted a list of offenders a while ago) Trying to get a NNTP feed of the apana.* groups from hock to sa's newsserver just would not happen, until we turned off these extensions. The connection would extablish.. and then just hang and timeout. YMMV. Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key Drag me, drop me, treat me like an object!