Re: Implementing Port Restrictions -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Implementing Port Restrictions
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Fri, 24 Jun 2016 09:58:52 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 6/24/2016 8:42 AM, Rich Loeber wrote:

Does anyone have suggestions on getting started with port
restrictions? What ports to leave open and which ones to close. When
you close a port, does it get reopened after an IPL?

I would advise that they get a dedicated firewall and not try to do it on the i.

As for ports on the i, I would suggest just starting the servers that are needed and shutting down those that aren't necessary.

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Implementing Port Restrictions , Rob Berendt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.