Date: Thu, 25 May 1995 10:36:35 -0700 From: "Justin T. Gibbs" <gibbs@freefall.cdrom.com> To: Poul-Henning Kamp <phk@ref.tfs.com> Cc: pritc003@maroon.tc.umn.edu (Mike Pritchard), hackers@FreeBSD.org Subject: Re: Speeding up your slip link Message-ID: <199505251736.KAA01924@freefall.cdrom.com> In-Reply-To: Your message of "Thu, 25 May 95 10:21:11 PDT." <199505251721.KAA26940@ref.tfs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Just in case anyone is interested, one way I found to squeeze a >> few more bytes through your SLIP link is to set "tcp_extensions=NO" >> in your /etc/sysconfig file. This disables the RFC1323 & RFC1644 >> extensions, which are really intended for high speed links. >> In fact, RFC1323 even suggests disabling it on slow links. >> >> If you don't normally connect to other hosts that support RFC1323 >> and RFC1644 then you won't see any difference. To determine if >> a host you are connecting to supports RFC1323, try examining >> some traffic to/from that machine with "tcpdump". If it indicates >> that the "timestamp" option was present, then it is sending >> the extra RFC1323 data. > >I guess we really should have a "bandwidth" for each interface and link >it to that... It needs to be a per device option anyway since its a pitty to lose the TTCP advantage on your local ethernet just because you have a slip line to a crusty annex that doesn't support either RFC. >-- >Poul-Henning Kamp <phk@login.dknet.dk> -- TRW Financial Systems, Inc. >'All relevant people are pertinent' && 'All rude people are impertinent' >=> 'no rude people are relevant' -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ==============================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505251736.KAA01924>