Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

allow-bulk-leasequery (DHCP Local Server)

 

Syntax

Hierarchy Level

Release Information

Statement introduced in Junos OS Release 16.1.

Description

Enable a DHCPv4 or DHCPv6 local server to listen for, process, and respond to bulk leasequery requests received on TCP connections on TCP port 67 for DHCPv4 and on TCP port 547 for DHCPv6.

Options

max-connections number-of-connectionsSpecify the maximum number of concurrent TCP connections allowed in the logical system/routing instance. This setting helps you manage the resources that the jdhcpd daemon uses for bulk leasequery operations in the logical system/routing instance. The number of connections you specify for a logical system/routing instances must be less than the number of connections you specify for the global accept-max-tcp-connections statement.

Range: 1 through 10

Default: 3

max-empty-replies number-of-repliesSpecify the maximum number of empty replies that the DHCP local server sends to a specific requestor. When the maximum number is reached, the DHCP server closes the connection.

An empty reply is a response sent from the DHCP local server that contains no bindings or has an option status code error. Empty replies are often the response to an unauthorized requestor that has sent an invalid or incorrect query that produces no binding information. By limiting the number of empty replies that the DHCP local server can send, you prevent the connection from being consumed by an unauthorized or malicious requester, and free up the DHCP local server to support legitimate requestors.

Range: 1 through 100

Default: 5

restricted-requestorSpecify that the DHCP local server responds to a bulk leasequery request by sending the binding information to restricted requestors only. This ensures that the requestor is the originator of the binding.

Restricted requestors are determined as follows:

  • For DHCPv4 bulk leasequery requests, the giaddr of the requestor must match the giaddr of the client.

  • For DHCPv6 bulk leasequery requests, the requestor’s client ID in the bulk leasequery message must match the relay ID sent during binding creation.

timeout secondsSpecify the number of seconds that a connection on the TCP socket can be idle before the DHCP local server closes the connection. Closing inactive connections enables the DHCP local server to more efficiently apply resources in support of active TCP connections.

Range: 1 through 1000

Default: 120

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.