[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?

Subject: Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
From: "Dan" <daniel@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 1 May 2001 17:16:08 +0100
List-id: Mailing list for users to address network security on Cobalt products. <cobalt-security.list.cobalt.com>

> Just a suggestion; look at the routing table 'route'
> and delete the entries that are troubling you.
> Gerald
>

Thanks, but where is this "route" table? I've tried to "locate" it but
couldn't find it?

Dan

Follow-Ups:
- Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
  - From: Gerald Waugh

References:
- [cobalt-security] RaQ3-All-Kernel-4.0.1-2.216C24III.pkg
  - From: Fred
- [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
  - From: Dan
- Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
  - From: Gerald Waugh

Prev by Date: Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
Next by Date: RE: [cobalt-security] RaQ3-All-Kernel-4.0.1-2.216C24III.pkg
Previous by thread: Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?
Next by thread: Re: [cobalt-security] Why does PortSentry continue to log ports 137 and 138 even though I've told it not to?

Sun Cobalt Security Message Index

Sun Cobalt Security Thread Index