Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!NCNOC.TUCC.EDU!jrr
From: jrr@NCNOC.TUCC.EDU (Joe Ragland)
Newsgroups: comp.sys.proteon
Subject: Re: p4200 routing
Message-ID: <8812271428.AA08167@ncnoc.tucc.edu>
Date: 27 Dec 88 14:28:38 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 22

Milo, yes net 127 loopback is a BSD-ism.  But, it is now an Ultrix-ism,
a SunOS-ism, an etc-ism...  I can appreciate having a 'clean' generic
gateway uncorrupted by -isms but maybe somebody ought to redefine what
generic means occasionally as the IP world evolves.

As I recall the last time I found it necessary to use the filter list
to protect my net from some bogon generator (or to relieve another net
from our bogons) one does not get 'process 2' diagnostic messages
relating to the filter at default log level (76).  I'd like to know in
such cases if the filter is being used (or when the bogons cease).
Also, adding filters or changing log level requires a restart or reboot of
the gateway for changes to take effect, an event I'd rather avoid
especially at busy times.  Maybe a message stating 'packet filtered'
would be beneficial in such cases without having to lower the log
level to the point that you are done in with too much info.  I suspect
there is a bit of tweaking of p4200 logic in this area that might
make the process easier to deal with and less disruptive.

We'll let the 127 loopback issue be.  Thanks for your and Keith's
input.

--Joe