... | ... | @@ -112,7 +112,7 @@ Handling of inbound LeaseQuery packets, would be provided by a new hook library, |
|
|
1. LeaseQuery::buffer<4/6>_receive() callout will unpack the query and pass it into a LeaseQuery handler which will:
|
|
|
1. Vet the LeaseQuery query against Access Control (discussed later on). Unauthorized requests will logged and dropped.
|
|
|
1. Search for matching leases
|
|
|
1. Construct the appropriate LeaseQueryResponse - When active leases are found this includes: extracting the needed information from the lease's user-context and based on the client's requested option list. Should we decide to additional options, we would need to calculate them now.
|
|
|
1. Construct the appropriate LeaseQueryResponse - When active leases are found this includes: extracting the needed information from the lease's user-context and based on the client's requested option list. Should we decide to support additional options, we would need to calculate them at this point, potentially using
|
|
|
1. Send the LeaseQuery response
|
|
|
1. LeaseQuery::buffer<4/6>_receive() callout will set status to DROP, causing the
|
|
|
server to go on to the next DHCPX client packet.
|
... | ... | |