×
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.
What you want is Packet Filters.
Open iNav then navigate down to Network -> IP Policies -> Packet Rules
Rules can be places on any or all interfaces into your system.
There is an editor there and a wizard. Do not play here if you don't
know IP addressing and subnet masks!!
But remember the 'Foghorn Leghorn' ("Fortunately I keep my feathers
numbered for just such an Emergency!") command: RMVTCPTBL *ALL.. This
is entered on the console when you activate a packet rule that
disconnects all your iNav functions so that you can't fix them! The
command doesn't delete them simply de-activates them so you can get back
in and fix them. Don't ask how I know this command. :-)
- Larry
Diana Hicks wrote:
We have a firewall but I would like to add another layer of security to our
system (AS/400, iSeries, i5, System i, etc.). I would like to specify a couple
of IP ranges on the system and only allow connections from those addresses.
Any other IP address that attempts to connect to the system would be denied.
This would be at the interface level and include all services since our system
is not on the internet. All suggestions will be appreciated.
Thanks.
--
Diana Hicks
As an Amazon Associate we earn from qualifying purchases.
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.