From owner-freebsd-current Mon Mar 20 05:04:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA25585 for current-outgoing; Mon, 20 Mar 1995 05:04:41 -0800 Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA25551 for ; Mon, 20 Mar 1995 05:04:23 -0800 Received: from utis156.cs.utwente.nl by utrhcs.cs.utwente.nl (5.0/csrelayMX-SVR4_1.0/RB) id AA08564; Mon, 20 Mar 1995 14:03:47 --100 Received: by utis156.cs.utwente.nl (4.1/RBCS-1.0.1) id AA13022; Mon, 20 Mar 95 13:40:28 +0100 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 Date: Mon, 20 Mar 1995 13:40:23 +0100 Message-Id: <13021.795703223@utis156.cs.utwente.nl> From: Andras Olah content-length: 681 Sender: current-owner@FreeBSD.org Precedence: bulk On Sat, 18 Mar 1995 13:17:44 PST, "Justin T. Gibbs" wrote: > 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? I'd like to investigate it to see if it's caused by the T/TCP changes. I need a little bit more details. Justin, could you please send me tcpdumps from both ends of the failed connection and please use -s 96 for tcpdump to get all the options. Andras