Re: Tutorial changes

On Thu, 5 Jun 2003 10:06:48 -0400 (EDT) Roger Hartmuller <[email protected]>
wrote:
> 1. Under Navigating the GUI, the last paragraph, the middle sentence
> should read "You can see what policy conflicts have been created."

Fixed.
 
> 2. Under Defining some network policies, under 2. Create the policy.
> 
> The 1st step should be to select Manage Policies, and then Create New.

Fixed.

> The next screen shows boxes to check or uncheck - this needs to be added.
> I assume this would be Notification generator to check.

Fixed.

> In Step 3.1., the button is called "Add a new notification log destination"

Fixed.
 
> The next screen is "Select policies to apply data to" and needs to be
> included here. (This section needs re-working.)

Fixed.
 
> In Step 4. 2., It is a pull-down list, not a box check.

Not sure I understand this one. Can you see if it is still a problem. (Note that item numbers may have changed)

> The next screen is Modify clients or policies in role 'notification 
> generator'. You need to check either 'modifiy clients' or 'modify policies'.
> 
> Explain how to finish here.

Fixed.

> 3. Filters and Actions: A more complex example
> 
> Step 1. 4. This screen is Modify clients or policies in role 'telnet 
> server'. You have to check 'Modify clients'. The next screen then gives
> the list of clients.

Fixed.

> (Aside: Should we create 2 clients here, as we did
> in our testing previously?)

No, I updated the section at the end for adding additional clients.

> -----------------------------------------
> At this point, I reset the database, to go thru as if we had NOT done the 
> notification example.
> 
> Under Step 2. 6. - SA Direction is listed twice - Do you want 
> SA DF handling:?

Fixed.
 
> Step 3. 1. has you creating hosts again. That was already done
> in Step 1.

Fixed.
 
> Pick it up with 3. 2.
> 
> 4. IKE and IPSEC: A more complex example
> 
> This states "This example assumes that the preconfigured action example 
> has already been completed."
> 
> I think I remember that committing the preconfigured action prior to 
> doing the IKE example caused a problem with the clients, so I always 
> did the IKE example stand-alone.

It shouldn't. Can you try again, so we can identify and fix the problem?

> In Step 5., the responder negotiation parameters should read
> In Step 8., the responder negotiation parameters should read
> 
> min 1m; refresh 90%; can idle

Fixed.
 
> At the end, you have to create the ip filter.

You should be able to use the existing Telnet filter. If not, let me know so we can figure out what's wrong and fix it.


-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.