Date: Fri, 20 Sep 96 10:47:44 EST From: M C Wong <mcw@hpato.aus.hp.com> To: pjchilds@imforei.apana.org.au Cc: questions@freebsd.org Subject: Re: odd problem with 2.1R NNTP access Message-ID: <199609200047.AA189830474@relay.hp.com> In-Reply-To: <199609190746.RAA20172@al.imforei.apana.org.au>; from "Peter Childs" at Sep 19, 96 5:16 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 ? I think u meant RFC1323, right ? The same reason is causing me unable to access www.etinc.com and timeout during smtp session. So, does it mean in general the following are true for 2 FreeBSD boxes: 1) Both boxes have tcp_extension enabled and they should talk happily 2) Both boxes have tcp_extension disabled and they should talk happily 3) One has tcp_extension enabled and one disabled and there is no gurantee of the connection ? I believe etinc.com is using FreeBSD, but I do get this problem before when I have the tcp_extension stuff enabled. > 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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609200047.AA189830474>