Configuring zero field check on ripng packets, Applying ipsec policies for ripng – H3C Technologies H3C SR8800 User Manual

Page 301

Advertising
background image

285

To configure poison reverse:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter interface view.

interface interface-type
interface-number

N/A

3.

Enable the poison reverse
function.

ripng poison-reverse

Disabled by default

Configuring zero field check on RIPng packets

Some fields in the RIPng packet must be zero, which are called “zero fields”. With zero field check on

RIPng packets enabled, if such a field contains a non-zero value, the entire RIPng packet will be

discarded. If you are sure that all packets are reliable, disable the zero field check to reduce the CPU

processing time.
To configure RIPng zero field check:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter RIPng view.

ripng [ process-id ]

N/A

3.

Enable the zero field check.

checkzero

Optional
Enabled by default

Configuring the maximum number of equal cost routes for load
balancing

To configure the maximum number of equal cost RIPng routes for load balancing:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter RIPng view.

ripng [ process-id ]

N/A

3.

Configure the maximum
number of equal cost RIPng

routes for load balancing.

maximum load-balancing number

Optional

Applying IPsec policies for RIPng

To protect routing information and defend attacks, RIPng supports using an IPsec policy to authenticate
protocol packets.
Outbound RIPng packets carry the Security Parameter Index (SPI) defined in the relevant IPsec policy. A

router uses the SPI carried in a received packet to match against the configured IPsec policy. If they match,

the router accepts the packet; otherwise, it discards the packet and will not establish a neighbor
relationship with the sending router.

Advertising