From owner-freebsd-security  Thu Aug 24 23:58:23 2000
Delivered-To: freebsd-security@freebsd.org
Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82])
	by hub.freebsd.org (Postfix) with ESMTP id 51B9237B43C
	for <freebsd-security@freebsd.org>; Thu, 24 Aug 2000 23:58:21 -0700 (PDT)
Received: from 149.211.6.64.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 24 Aug 2000 23:57:11 -0700
Received: (from cjc@localhost)
	by 149.211.6.64.reflexcom.com (8.9.3/8.9.3) id XAA62613;
	Thu, 24 Aug 2000 23:58:17 -0700 (PDT)
	(envelope-from cjc)
Date: Thu, 24 Aug 2000 23:58:17 -0700
From: "Crist J . Clark" <cjclark@reflexnet.net>
To: Kurt Wuensche <kwuensche@yahoo.com>
Cc: freebsd-security@FreeBSD.ORG
Subject: Re: Route strangeness
Message-ID: <20000824235817.A62475@149.211.6.64.reflexcom.com>
Reply-To: cjclark@alum.mit.edu
References: <20000825034824.11470.qmail@web4701.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000825034824.11470.qmail@web4701.mail.yahoo.com>; from kwuensche@yahoo.com on Thu, Aug 24, 2000 at 08:48:24PM -0700
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Thu, Aug 24, 2000 at 08:48:24PM -0700, Kurt Wuensche wrote:
> I have recently been having strange occurences
> related to FBSD 2.2.5 routing.  I am running static
> routing with icmp redirects turned off.  What happens
> is that for no apparent reason the default route no
> longer works.  The weird part is that netstat -nr and
> ifconfig show the default route still USGc and that
> the interface
> is up.  I can even ping the gateway on my isp, but the
> packets go no further.

What do you mean? If you ping it, the packets shouldn't go further. Do
you mean that you have trouble trying to ping machines past it? What
does a 'traceroute -n' return for those?

> Thinking it was an isp problem
> I called the isp.  Their routing is apparently ok.
> Still pings from them sometimes
> don't come back.  When this happens my host is also
> not visible
> from the internet, with a ping to an ip address
> returning
> request timeout errors.

The exact messages please.

> Even weirder is that a telnet
> by ip number
> to the machine remotely eventually shows a login
> prompt, but only
> after waiting for almost two minutes!  I have run
> route
> monitor and tcpdump and examined messages.  So far
> tcpdump has not shown any clues while route monitor
> occassionally shows RTM_LOSING messages from pid 0 and
> the user ppp process.  messages shows nothing.  Then
> for no reason, routing will work again.  A reset also
> seems to fix the problem.  I have a friend running
> 2.2.8 and the same identical things are happening to
> him.  Any ideas?

DNS problems?
-- 
Crist J. Clark                           cjclark@alum.mit.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message