Date: Tue, 16 Jun 1998 18:44:09 -0400 From: "Stephen A. Derdau" <sderdau@bit-net.com> To: questions@FreeBSD.ORG Cc: adrl@whoweb.com Subject: [Fwd: tcp_extensions] Message-ID: <3586F539.C0AFA6CE@bit-net.com>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------4D0A83F0939CFA6F843617C6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I may be wrong in asking my isp to see if they have a fix for the tcp_extensions for their equipment.. However I am not technical enough to respond back to the isps reply which follows. I've installed communicator 4.05 and running tcp extensions on my end I still cannot get to sites like www.freebsd.org. So I have to disable tcp_extensions. Here is the email that has passed between us. > > >From where are you quoting? > > I assume you're quoting from something for FreeBSD and talking > about RFC1323 and RFC1644 ? > > RFC1323: > TCP Window scale option > > RFC1644: > TCP Extensions for Transactions > > Both of these are TCP extensions. They would only be relevant > to our Bay Networks Remote Access Concentrators if you were > making a tcp connection _with_ the RAC. But you're not, you're > routing IP packets _through_ the RAC and our Cisco routers, > and MCI's routers, etc. > > What matters is that both endpoints of the TCP connection > properly implement the RFC's. If you can't talk to certain > websites with the extensions turned on, then one end or the other > has a problem. RFC1323 is a negotiated option. If the remote > end doesn't support the window scale option, it won't be ack'd. > > Try http://www.whoweb.com . It's a freebsd box > running the TCP extensions. > > Jon Thisis what I sent him from the FreeBSD FAQ search ****** > > 10.14. I'm having problems talking PPP ......" . > > > > Try disabling the TCP extensions in /etc/rc.conf by changing the > > following variable to NO: > > > > tcp_extensions=NO > > > > > > Xylogic's Annex boxes are also broken in this regard and you must use > > the above change to connect > > thru them. > > This is what I asked him ****** > > ***** Any Idea when the patch for your Annex system will > > be put in so that I can start using tcp_extensions on my end? > > As it is now with tcp_extensions enabled I cannot get to certain > > websites. I understand it's a known problem and has been for a time. > > Do expect them to send / make a fix for this and if there is a fix now > > will this be applied to your equipment ******* > > > > Thank You > > -- > > "FreeBSD It's That and Much Much More" > > Find out Why @ http://www.freebsd.org > > Stephen A. Derdau > > http://sderdau.bit-net.com > > Running: FreeBSD 2.2.6-STABLE #0: Mon Jun 8 20:16:08 EDT 1998 > > --------------4D0A83F0939CFA6F843617C6 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Received: from localhost (localhost [127.0.0.1]) by mail.bit-net.com (8.8.8/8.8.8) with SMTP id JAA14482; Tue, 16 Jun 1998 09:49:12 -0400 (EDT) From: Jon Fraser <jfraser> Message-Id: <199806161349.JAA14482@mail.bit-net.com> X-Authentication-Warning: mail.bit-net.com: localhost [127.0.0.1] didn't use HELO protocol To: "Stephen A. Derdau" <sderdau@bit-net.com> cc: help@bit-net.com Subject: Re: tcp_extensions In-reply-to: Your message of "Tue, 16 Jun 1998 08:34:45 EDT." <35866665.41C67EA6@bit-net.com> Date: Tue, 16 Jun 1998 09:49:12 -0400 X-Mts: smtp >From where are you quoting? I assume you're quoting from something for FreeBSD and talking about RFC1323 and RFC1644 ? RFC1323: TCP Window scale option RFC1644: TCP Extensions for Transactions Both of these are TCP extensions. They would only be relevant to our Bay Networks Remote Access Concentrators if you were making a tcp connection _with_ the RAC. But you're not, you're routing IP packets _through_ the RAC and our Cisco routers, and MCI's routers, etc. What matters is that both endpoints of the TCP connection properly implement the RFC's. If you can't talk to certain websites with the extensions turned on, then one end or the other has a problem. RFC1323 is a negotiated option. If the remote end doesn't support the window scale option, it won't be ack'd. Try http://www.whoweb.com . It's a freebsd box running the TCP extensions. Jon > 10.14. I'm having problems talking PPP ......" . > > Try disabling the TCP extensions in /etc/rc.conf by changing the > following variable to NO: > > tcp_extensions=NO > > > Xylogic's Annex boxes are also broken in this regard and you must use > the above change to connect > thru them. > > ***** Any Idea when the patch for your Annex system will > be put in so that I can start using tcp_extensions on my end? > As it is now with tcp_extensions enabled I cannot get to certain > websites. I understand it's a known problem and has been for a time. > Do expect them to send / make a fix for this and if there is a fix now > will this be applied to your equipment ******* > > Thank You > -- > "FreeBSD It's That and Much Much More" > Find out Why @ http://www.freebsd.org > Stephen A. Derdau > http://sderdau.bit-net.com > Running: FreeBSD 2.2.6-STABLE #0: Mon Jun 8 20:16:08 EDT 1998 > --------------4D0A83F0939CFA6F843617C6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3586F539.C0AFA6CE>