Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!MORGUL.PSC.EDU!Eugene.Hastings
From: Eugene.Hastings@MORGUL.PSC.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Networks unreachable
Message-ID: <1988.6.13.17.20.22.Eugene.Hastings@morgul>
Date: 13 Jun 88 17:25:40 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26

Yea, verily, and after a restart, the Router In Question passes previously
barfed traffic. Thanks, and a tip of the bashed hat. Yet another reminder
that confession can be good for one's productivity, let alone one's soul.

Thanks again,
Gene
- - - - Begin forwarded message - - - -
Date: Mon, 13 Jun 88 08:25:13 PDT
From: dlw@violet.Berkeley.EDU (David Wasley)
Message-Id: <8806131525.AA24652@violet.berkeley.edu>
To: Eugene.Hastings@morgul.psc.edu
Subject: p4200 bug

We (actually Milo Medin) found what may be that bug when we installed 7.4
here, and Proteon generated 7.4b for us as a result. Basically, if the
box had an explicit route for a net, and it became unreachable (ie 16),
the box wouldn't take default but would claim the net was explicitly
unreachable.

There is a mailing list for p4200 users that Scott Brim started long ago:
p4200@devvax.tn.cornell.edu  --  some of those folks may have other
bug information re 7.4. We've been using 7.4b since January.

	David Wasley
	U C Berkeley

- - - - End forwarded message - - - -