From owner-freebsd-net Wed Mar 29 18:56: 1 2000 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 8C8A037B917 for ; Wed, 29 Mar 2000 18:55:54 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id UAA35767; Wed, 29 Mar 2000 20:59:06 -0600 (CST) (envelope-from jlemon) Date: Wed, 29 Mar 2000 20:59:06 -0600 (CST) From: Jonathan Lemon Message-Id: <200003300259.UAA35767@prism.flugsvamp.com> To: morganw@engr.sc.edu, net@freebsd.org Subject: Re: 5.0 tcp weirdness X-Newsgroups: local.mail.freebsd-net In-Reply-To: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >In 5.0 since sometime last weekend, I have been experiencing some very >strange TCP problems. Complete inability to connect to some machines, poor >throughput, etc. I first noticed that my nameserver was having trouble >talking to some other nameservers, and at first thought @home was using >some very weird filtering, or maybe had set up something to require some >sort of DHCP validation (I don't bother with DHCP since my IP is virtually >static). After running dhclient, the nameserver lookups seemed to improve, >but there were still a few sites I could not connect to. Here is some data >I gathered: Hmm. What's your routing table look like? I was seeing some really weird problems like this (some connections okay, some not), when I had my default route set to whatever gateway that @home gave me. After I changed it to an interface route, the problems went away. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message