To guarantee the security of a DHCPv4 server, you need to enable DHCPv4 proxy when the DHCPv4 packet sent from the NetEngine 8000 F to a user does not contain the DHCPv4 server IP address.
The system view is displayed.
The interface view is displayed.
A BAS interface is created, and the BAS interface view is displayed.
The access type is set to Layer 2 subscriber access and the attributes of this access type are configured.
DHCP proxy is enabled.
Currently, DHCPv4 proxy is used only for the remote address pool of the BAS. The configuration modification does not take effect on online users.
DHCPv4 proxy can also be used for Layer 2 users or Layer 2 leased line users.
DHCP lease proxy is enabled on the BAS interface, and a proxy lease is specified.
Using shorter proxy leases can accelerate the identification of client or link faults. However, users renew their leases more frequently, increasing the processing load of the device. To balance the conflict between fault detection and processing load, run the dhcp lease-proxy first-step first-step second-step second-step command to enable DHCP lease proxy with step-based proxy leases.
The maximum number of times that a lease proxy user's client sends lease renewal packets to the DHCP server before T1 (1/2 of the lease) or T2 (7/8 of the lease) arrives is configured.
The configuration is committed.