Re: IP filtering -- 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: IP filtering
From: "Steve McKay" <steve.mckay@xxxxxxxxxxxxxx>
Date: Fri, 9 Jan 2004 11:07:49 -0600
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

"Tom Liotta" <qsrvbas@xxxxxxxxxxxx> wrote in
message news:12DF30CA.22DCABEC.0021C8A2@xxxxxxxxxxxxxxx
>
> If the two are "...on the same subnet (10.10.18.x)", what's between them?
How are you routing between "the same subnet"? Just curious.
>
Tom -

As I've gone further down this road, I've come to believe that I need to
have the two boxes on separate subnets and that System A (the frontend box)
needs to have two NICs.  Is that what you're trying to point out to me?
Please explain . . .

Thanks,

Steve

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.