Re: [FW1] fw putkey - is a restart necessary?

[Bill Husler <BHusler@FW1-NOSPAMPacBell.net>]

Graham,
  Contrary to whatever other may say, I have found that in most cases, fwstop and
fwstart are not necessary. Timing is everything, however,  since you have to get
both putkeys completed before the next authentication request. I have had great
success with both skey and fwn1 (your mileage may very) with simply using multiple
telnet windows to set up each box and timing the last enter keypress (ie. hit enter
/ jump to other window / hit enter again). Others may have different experiences
with this, but I suggest giving it a try before resorting to fwstop / fwstart (what
have you got to lose at that point).
Bill

Graham Leggett wrote:

> Hi all,
>
> According to what I have read so far, to get a remote module and a
> management module to talk to each other requires the following steps:
>
> [management.wherever.com]# ./fw putkey remote.wherever.com
> Enter secret key:
> Again secret key:
>
> [remote.wherever.com]# ./fw putkey management.wherever.com
> Enter secret key:
> Again secret key:
>
> At this point do I need to restart the management module and remote
> module before this change will take effect?
>
> If so, how? (Other than ./fwstop ; ./fwstart)
>
> Regards,
> Graham
> --
>
> ================================================================================
>      To unsubscribe from this mailing list, please see the instructions at
>               http://www.checkpoint.com/services/mailing.html
> ================================================================================





================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================