As well the firewall should be (e.g. clever enough to forbid)...
If the firewall offers a third interface, then it's probably for the purpose
of a creating a DMZ. A place where you can place "publicly-accessible"
servers (e.g. web, email, etc.). One of the major security benefits of
having a DMZ, is that you prohibit all connections being initiated from it
to the "internal" side of the firewall.
What you're looking to do, contradicts the purpose of the DMZ.
..
Best Regards, Don Kelloway
http://www.kelloway.org
-----Original Message-----
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, December 14, 1999 7:02 AM
Subject: Question
>
>
>We have a firewall with three interfaces, internal, external and the third
one
>is defined as external, but now we need some internal addresses to come
from
>this third interface to the internal network. The problem is that the
firewall
>is clever enough to forbid connections from an external interface which
have the
>source IP within the range defined for an internal interface.
>
>Any idea, solution, suggestion...?
>Thanks in advance.
>
>
>-
>[To unsubscribe, send mail to [EMAIL PROTECTED] with
>"unsubscribe firewalls" in the body of the message.]
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
