Scott Ullrich wrote:
On 11/20/07, Paul M <[EMAIL PROTECTED]> wrote:
two firewalls, fwa, fwb, fwa is the master and replicated to fwb
I made the mistake of modifying something on
fwb, and then of course had to go back and reproduce the changes on fwa.
Could there be added in the UI (advanced options maybe) a flag to
indicate that this FW is a slave, and then grey out anything which is
overwritten by the master.
Could it, when the pages are greyed out, put a timestamp at the top to
indicate when the changes were last propagated?
Just a thought. OK, it's pandering to people who do stupid things, but
I'm sure I'm not the only one.
This is a great idea but it needs to be further thought out. What if
you loose the master firewall and in an emergency you need to change a
firewall rule but it is greyed out?
It could allow editing if it has master status. It would have to go
further than that as well. If you allow any editing on the secondary,
when the primary came back online it would get overwritten with the old
config.
A number of issues to address with this, though it's something we'd like
to see done eventually.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
