From owner-freebsd-current Tue Jan 23 08:22:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA29804 for current-outgoing; Tue, 23 Jan 1996 08:22:16 -0800 (PST) Received: from trout.nosc.mil (trout.nosc.mil [128.49.16.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA29795 for ; Tue, 23 Jan 1996 08:22:09 -0800 (PST) Received: from cod.nosc.mil by trout.nosc.mil (4.1/SMI-4.1) id AA08688; Tue, 23 Jan 96 08:21:56 PST Received: from [128.49.16.48] (aegis.nosc.mil) by cod.nosc.mil (4.1/SMI-4.1) id AA20974; Tue, 23 Jan 96 08:21:30 PST X-Sender: gshaffer@cod.nosc.mil Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 23 Jan 1996 08:22:19 -0800 To: current@freebsd.org From: gshaffer@nosc.mil (Greg Shaffer) Subject: Re: finger problem going from 2.1R to -current Cc: gshaffer@nosc.mil Sender: owner-current@freebsd.org Precedence: bulk I have been following this thread for awhile, no let me throw some fuel on the fire! I've had some problems over the past several weeks with what appeared to be some routing problems, but I now believe they are related to the T/TCP (more specificly RFC 1644) implementation in FreeBSD 2.1R. To help illustrate my problem here is a simple network diagram. A B +-------+--------+ | (Ethernet) (FW) | +--+-------C | | | | (PPP) | +-------D | | +-------E Where: Machine C, D and E are FreeBSD 2.1R. Machine A is SunOS. Machine B is Solaris 2.5. Machine A, B, C and D are all within the same domain behind a firewall. Machine E is outside on the Internet. Here is the problem. >From machine D I could ping and traceroute to machine C and E. I could not use and other services (e.g. ftp, rlogin, telnet, http, etc). I would have to go through and intermediate machine (e.g. A or B) to get to C. When ever I tried to access one of these machines (C or E) from D the connection appeared to startup up and then hang. Netstat showed that the connection had been made but output at the terminal never completed (i.e. I never saw the login prompt). For a while I thought I had a routing problem, but when I boot machine D using Windows I could get to machine C and E with no problems. When I first read this thread I felt the problem might be remotely related. When I disabled RFC 1644 support on machine C and D I was able to get into both C and E from D without any problems. Forgive me if this sounds like a silly question, but did anybody test T/TCP between two FreeBSD 2.1R machines? Greg Shaffer