From owner-freebsd-current Sat Mar 18 22:27:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA00904 for current-outgoing; Sat, 18 Mar 1995 22:27:31 -0800 Received: from balboa.eng.uci.edu (balboa.eng.uci.edu [128.200.61.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id WAA00898 for ; Sat, 18 Mar 1995 22:27:30 -0800 Received: from localhost.uci.edu by balboa.eng.uci.edu with SMTP id AA05788 (5.65c/IDA-1.4.4 for current@freebsd.org); Sat, 18 Mar 1995 22:27:26 -0800 Message-Id: <199503190627.AA05788@balboa.eng.uci.edu> To: "Justin T. Gibbs" Cc: current@FreeBSD.org Subject: Re: TCP connections over SLIP are still a problem In-Reply-To: Your message of "Sat, 18 Mar 1995 13:17:44 PST." <199503182117.NAA23923@estienne.cs.berkeley.edu> Date: Sat, 18 Mar 1995 22:27:25 -0800 From: Steven Wallace Sender: current-owner@FreeBSD.org Precedence: bulk > I still can't talk to another FreeBSD machine when the traffic > goes out my SLIP interface. Connections to a FreeBSD machine > on the same local ether work fine. Connections to non-FreeBSD > machines over the SLIP line work fine. In the case of telnet, > I get the connection, but then nothing more. > > Here's what tcpdump has to say. Anyone have any ideas? > > 20:32:10.130049 narnia.hip.berkeley.edu.1058 > estienne.CS.Berkeley.EDU.telnet: .... You might have found a TCP/IP bug in FreeBSD that is only seen connected to another FreeBSD machine. I have noticed differences in TCP when connected to SunOS 4.1 and Solaris machines, so your observation may be a real BSD problem and not a site-specific problem. Steven