From owner-freebsd-questions  Sun Apr  5 19:43:57 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA02342
          for freebsd-questions-outgoing; Sun, 5 Apr 1998 19:43:57 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02332
          for <questions@FreeBSD.ORG>; Sun, 5 Apr 1998 19:43:52 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id TAA17732;
	Sun, 5 Apr 1998 19:42:52 -0700 (PDT)
Message-Id: <199804060242.TAA17732@implode.root.com>
To: Joe McGuckin <joe@via.net>
cc: questions@FreeBSD.ORG
Subject: Re: 2.2.6-RELEASE problem ? 
In-reply-to: Your message of "Sun, 05 Apr 1998 18:29:18 PDT."
             <199804060129.SAA21982@monk.via.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sun, 05 Apr 1998 19:42:52 -0700
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>We have this intermittant problem with 2.2.6. Our web server 
>has about 60 IP addresses aliased to fxp0. At random times, several 
>(actually, many) of the addresess become unreachable, unpingable. Re-running
>/etc/start_if.fxp0 seems to kick the machine into behaving. For a whie,
>at least.
>
>Has anyone else seen this? Could this be a defective fxp card?

   It's a software problem of some kind, probably in the route management code
or perhaps in the if-address code. I suspect that it's not that random...

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

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