Path: utzoo!utgpu!watmath!clyde!att!ucbvax!ORVILLE.NAS.NASA.GOV!lekash
From: lekash@ORVILLE.NAS.NASA.GOV (John Lekashman)
Newsgroups: comp.sys.proteon
Subject: p4200 routing
Message-ID: <8812301946.AA07422@orville.nas.nasa.gov>
Date: 30 Dec 88 19:46:05 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 21


   As to the p4200s having to examine every packet, extensive validity/
   conformance examinations are already being made by p4200 logic.  We
   regularily examine p4200 error messages.  This procedure is often
   the first indicator of a mis-configured host on the network.  With
   numerous campus departmental host and LAN administrators (with a great
   range of experience and inexperience) I find p4200 error diagnostics
   quite valuable.  One more check could hardly make much performance
   difference.

I also have found that Proteon Gateway complaints are an excellent
source for determining misconfigured hosts.  Proteon might consider more
extensive filtering capability and information about traffic activity.
However, the key is the degree of user configurability of it.  The
statement that one more check could hardly make a difference can
just lead on forever.  We also use Vitalink bridge products a great
deal, and have found one of the major wins on these pieces of
equipment is the ability to create user defined packet characteristics
about what gets forwarded.

							john