TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
Actually, this is an ideal IDS architecture. We use this configuration to
monitor our external ethernet segments (external being outside the
firewall). We have 2 nics in the RealSecure box. One nic is connected to
the external network strictly listening (stealth mode), the other nic is
connected to our internal network and is used to communicate with the
console. We find this to be ideal.
Scott Lunsford
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 17, 2000 7:34 AM
> To: Benjamin Mah
> Cc: [EMAIL PROTECTED]
> Subject: Re: Real Secure Engine with 3 NICs -reply
>
>
>
> TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of
> your message to
> [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help
> with any problems!
> --------------------------------------------------------------
> --------------
>
> It works, but it is not an ideal IDS architecture. Is there
> a reason why
> you are setting up your IDS system this way??
>
> /m
>
>
>
>
> "Benjamin Mah" <[EMAIL PROTECTED]>
> Sent by: [EMAIL PROTECTED]
> 02/14/00 04:57 PM
>
>
> To: <[EMAIL PROTECTED]>
> cc:
> Subject: Real Secure Engine with 3 NICs
>
>
>
> I am trying to do an engine with 3 NICs which means there
> will be 2 NICs
> without any IPs and IP forwarding ... the last NIC would
> have an internal
> IP address which reports back to the internal Console... Has
> anyone tried
> this ? Does this work ? Are there any security complication
> if i really
> implement this ?
>
> Thanks
> BenJiZs
>
>
>
>
