Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Aug 1997 09:18:30 +0930 (CST)
From:      Greg Lehey <grog@lemis.com>
To:        jwm@CSUA.Berkeley.EDU
Cc:        hackers@FreeBSD.ORG
Subject:   Re: Routing problems
Message-ID:  <199708072348.JAA15962@freebie.lemis.com>
In-Reply-To: <199708071757.KAA24249@soda.CSUA.Berkeley.EDU> from John Milford at "Aug 7, 97 10:56:49 am"

next in thread | previous in thread | raw e-mail | index | archive | help
John Milford writes:
>
> 	A new 2.2.2 machine has recently been droping off the net
> for some unknown reason.  This can take from 15 min. to 24 hour to
> happen and the only way to bring it back is to reboot.   At least that
> is the only way I have found.  I have found that the routing table
> looks a little strange when this happens:
>
> (etc)
>
> 	I have been looking at the source, but have not come up with
> anything.  I have found that with just the 3c590 (vx0) that this does
> not occur, and in fact that when this problem occurs the machine can
> be acessed from the 134 net (vx0).
>
> 	Is it possible that the Intel card is causing the routing
> table to get munged like this?

That would be my guess.  I suspect that you're looking in the wrong
place.  Check out the board with ifconfig--you may find it's down.
You could also try doing:

  # ifconfig fxp0 down
  # ifconfig fxp0 up

I've found this to unwedge my controllers (ed0, ep0) on occasion.

Greg



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708072348.JAA15962>