> If a IF that is configged in the firewall goes down the Firewall
> (Firewall-1, CheckPoint) freaks out totally.
OK makes sense. Although I would still bug CheckPoint about this, since
that is a bit of a limitation. Since they are binding the fw operation to
the interface, they should be able to easily determine its up/down status
and only operate if/when whatever interface(s) the fw is binded to are up,
otherwise the fw code (be it filtering or otherwise) stays out of the data
path entirely.
> So i have to set it up with a private network between theire LAN and our
> PM3 so the isdn IF us up all the time.
>
> Ive set it up like this and it works but i just wanted to check if its
> the correct way.
[..snip..]
What you describe in the remainder of your message is fine
network/routing-wise so, yes, it is correct in that sense and if it works
fine for you, that is great. Beyond that, I won't comment any further on
it. ;-)
-jr
----
Josh Richards - <jrichard@livingston.com> - <josh@lucent.com>
[Beta Engineer] - LUCENT Technologies - Remote Access Business Unit
<URL:http://www.livingston.com/> * <URL:http://www.lucent.com/dns/>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>