I have a "sanity check" question. We are a power company that operates at
higher than normal capacity during times of disaster. The web guys want to
set up a cache server for temporary Emergencies. They want to be able to
"turn off" and "turn on" the cache server route during times of natural
disasters so that caching of web sites can be accomplished. I understand
how the cache server works in conjunction with the Firewall, however, I have
never implemented something like this.
Normal Traffic flow:
Internal Network ---------->Firewall --------->Internet site
| No
|
Cache server
Traffic flow requested during emergencies:
Internal Network ---------->Firewall --------->Internet site
* Yes *
* *
Cache server
What they are looking at is putting a leg off the firewall and running on a
172.16.x.* address. Possible solution would be having rules placed in the
firewall that are disabled and enabled during the times of emergency that
allow caching and/or disallow it. Again, I have never tried anything like
this and would like to know what any one else thinks.
There is not a problem with pipe size. This issue they have is with access
of a site. I have explained possible performance issues. If any one has
any suggestions or comments please let me have it. Thanks for all your
help.
Joseph L. Cosgriff
Carolina Power and Light
[EMAIL PROTECTED]
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
