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


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


ME60 V800R010C10SPC500 Configuration Guide - Security Hardening 01

This is ME60 V800R010C10SPC500 Configuration Guide - Security Hardening

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).


  • TTL/hop limit:

    A source device can transmit RIP/RIPng packets to a device that is only a hop far from the source. When RIP/RIPng packets are sent on broadcast or multicast networks (except for unicast peers), RIP/RIPng sets the TTL/hop limit value to 1.

  • Whitelist

    RIP/RIPng supports a whitelist in a CP-CAR policy. Packets sent by a neighbor listed in a whitelist are accepted, but not discarded.

  • GTSM

    RIP uses GTSM to protect devices from potential attacks by checking whether the TTL value in each IP packet header is within a pre-defined range. TTL specifies the maximum number of devices through which a packet can pass. If the TTL value in an IP packet header is not within the pre-defined range, the forwarding plane discards the packet, protecting the control plane from being attacked.

  • Authentication

    RIP-2 supports authentication to prevent receiving bad routing data, error packets, and replay attacks.

    RIPng does not define any authentication mechanism to prevent receiving bad routing data, error packets, or replay attacks. RIPng supports IPsec authentication for RIPng packets.

  • Route limit

    RIP/RIPng supports the limit on the number of routes that can be added to the RIP/RIPng database for each RIP/RIPng process.

Updated: 2019-01-04

Document ID: EDOC1100059445

Views: 9025

Downloads: 11

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next