From owner-freebsd-current Fri Jan 22 03:20:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26991 for freebsd-current-outgoing; Fri, 22 Jan 1999 03:20:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rnocserv.urc.ac.ru (rnocserv.urc.ac.ru [193.233.85.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26983 for ; Fri, 22 Jan 1999 03:20:44 -0800 (PST) (envelope-from joy@urc.ac.ru) Received: from urc.ac.ru (y.urc.ac.ru [193.233.85.37]) by rnocserv.urc.ac.ru (8.8.8/8.8.8) with ESMTP id QAA08559 for ; Fri, 22 Jan 1999 16:20:17 +0500 (ES) (envelope-from joy@urc.ac.ru) Message-ID: <36A85EF1.444A86B@urc.ac.ru> Date: Fri, 22 Jan 1999 16:20:17 +0500 From: Konstantin Chuguev Organization: Southern Regional Center of FREEnet X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: T/TCP in FreeBSD-3.x Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Has FreeBSD-3.x a correct implementation of T/TCP? There is some bug mentioned in Squid FAQ (http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2), about brokenness of T/TCP in FreeBSD-2.2.2. Why I'm asking about this, is because I recently read an advice in one of the FreeBSD mailing lists, about "Why my dial-up PPP connection from a FreeBSD box is so slow comparing with Windows NT (about ten times slower)?" And the advice was (without explanations): "Try to switch off the TCP_EXTENSIONS in /etc/rc.conf". So, is it safe to use T/TCP (at least for Squid) for RELENG_3? RELENG_2_2? And what about MBUF size (mentioned at the same page of the Squid FAQ)? Do I need to patch Squid as it shown at the page? Thanks. -- Konstantin V. Chuguev. System administrator of Southern http://www.urc.ac.ru/~joy/ Ural Regional Center of FREEnet, mailto:joy@urc.ac.ru Chelyabinsk, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message