|
|
@@ -92,7 +92,7 @@ packet processing. Hook points that are not specific to packet processing
|
|
|
field has been already parsed and stored in other fields. Therefore,
|
|
|
the modification in the data_ field has no effect.
|
|
|
|
|
|
- - <b>Nest step status</b>: If any callout sets the status to SKIP, the server will
|
|
|
+ - <b>Next step status</b>: If any callout sets the status to SKIP, the server will
|
|
|
drop the packet and start processing the next one. The reason for the drop
|
|
|
will be logged if logging is set to the appropriate debug level.
|
|
|
|
|
|
@@ -172,7 +172,7 @@ packet processing. Hook points that are not specific to packet processing
|
|
|
The "lease4" argument points to @c Lease4 object that contains the lease to
|
|
|
be released. It doesn't make sense to modify it at this time.
|
|
|
|
|
|
- - <b>Nest step status</b>: If any callout installed on the "lease4_release" hook
|
|
|
+ - <b>Next step status</b>: If any callout installed on the "lease4_release" hook
|
|
|
sets the next step action to SKIP, the server will not delete the lease.
|
|
|
It will be kept in the database and will go through the regular expiration/reuse
|
|
|
process.
|
|
|
@@ -193,7 +193,7 @@ packet processing. Hook points that are not specific to packet processing
|
|
|
modify it at this time. All the information will be removed from the lease
|
|
|
before it is updated in the database.
|
|
|
|
|
|
- - <b>Nest step status</b>: If any callout installed on the "lease4_release" hook
|
|
|
+ - <b>Next step status</b>: If any callout installed on the "lease4_release" hook
|
|
|
sets the next step action to DROP, the server will not decline the lease.
|
|
|
Care should be taken when setting this status. The lease will be kept in
|
|
|
the database as is and the client will incorrectly assume that the server
|
|
|
@@ -215,7 +215,7 @@ packet processing. Hook points that are not specific to packet processing
|
|
|
pkt4_send callouts are complete, so any changes to that field will
|
|
|
be overwritten.)
|
|
|
|
|
|
- - <b>Nest step action</b>: if any callout installed on the "pkt4_send" hook
|
|
|
+ - <b>Next step action</b>: if any callout installed on the "pkt4_send" hook
|
|
|
sets the next step action to SKIP, the server will not construct the raw
|
|
|
buffer. The expectation is that if the callout set skip flag, it is
|
|
|
responsible for constructing raw form on its own. Otherwise the output
|
Francis Dupont