Subject: | |
From: | |
Reply To: | Genute, Thomas |
Date: | Thu, 14 May 1998 10:14:44 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Whether or not you use a default gateway depends on your own preferences and
environment. A default gateway is not necessary. Yes, hardcoded gateways
should enhance security. OTOH, if you have 1100 sessions coming from over
150 subnets (internal and external) this adds another administrative job and
there are other ways to provide security. My problem was that I depend on
the default gateway for most of my connections and it stopped working with
PP4 until I cleaned up my configuration.
-----Original Message-----
From: Tracy Johnson [mailto:[log in to unmask]]
Sent: Wednesday, May 13, 1998 12:51 PM
To: [log in to unmask]
Subject: Re: ftp and inetd
I'm confused, I don't understand why NOT having a default
gateway is a
problem. The other side of the coin is having hardcoded
gateways which
should still work and enhance security. Or am I going down
a merry path?
On Wed, 13 May 1998, Genute, Thomas wrote:
> There are problems with Telnet and problems with NS with
PP4. With NS the
> default gateway stopped working. If, as defined in NMMGR,
the default
> gateway has any reachable network defined other than "@",
it is not
> recognized as a default gateway. NETTOOL has some
enhancements such as
> GATELIST, GATEUP and GATEDOWN. The plus is that when a
router went down, it
> is indicated with the GATELIST command. The minus is that
when the router
> came back up, the 3k didn't recognize we manually brought
it up with GATEUP.
> The Telnet problems are more insidious. ...
|
|
|