No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE40E V800R010C10SPC500 Configuration Guide - User Access 01

This is NE40E V800R010C10SPC500 Configuration Guide - User Access
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring DHCPv4 Proxy

Configuring DHCPv4 Proxy

Usage Scenario

To guarantee the security of the DHCPv4 server, you need to enable DHCPv4 proxy when the DHCPv4 packet sent from the NE40E to a user does not contain the DHCPv4 server IP address.

DHCPv4 proxy can be used in the scenario shown in Figure 4-3.

  • The DHCPv4 server can receive DHCPv4 Discovery and Request packets that are forwarded by the NE40E and carry the IP address of the NE40E as the source address.

  • The user can receive the DHCPv4 Offer packet with the source address of the IP address of the NE40E and obtain an IP address allocated by the DHCPv4 server to access the network.

Figure 4-3 Networking diagram of DHCPv4 proxy

Pre-configuration Tasks

Configuring a DHCPv4 Server Group

Enabling DHCPv4 Proxy

To guarantee the security of the DHCPv4 server, you need to enable DHCPv4 proxy when the DHCPv4 packet sent from the NE40E to a user does not contain the DHCPv4 server IP address.

Context

Perform the following steps on the NE40E:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number [ .subinterface-number ]

    The interface view is displayed.

  3. Run bas

    A BAS interface is created and the BAS interface view is displayed.

  4. Run access-type layer2-subscriber [ default-domain { [ authentication [ force | replace ] dname ] [ pre-authentication predname ] } ]

    The access type is set to Layer 2 subscriber access and the attributes of this access type are configured.

  5. Run dhcp-proxy enable

    DHCP proxy is enabled.

    NOTE:
    • Currently, DHCPv4 proxy is used only for the BAS 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.

  6. (Optional) Run dhcp lease-proxy [ lease-time ]

    DHCP lease proxy is enabled on the BAS interface, and a proxy lease is specified.

    NOTE:

    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 second-step command to enable DHCP lease proxy with step-based proxy leases.

  7. (Optional) Run dhcp lease-proxy renew-packet through-time time-value

    The maximum number of times that a lease proxy user's client sends lease renewal packets to the DHCP server before the original T1 (1/2 of the lease)/T2 (7/8 of the lease) lease arrives is configured.

  8. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055031

Views: 17756

Downloads: 72

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next