beautypg.com

Configuring acfc negotiation – H3C Technologies H3C SecPath F5020 User Manual

Page 22

background image

14

Step

Command

Remarks

3.

Specify the primary and

secondary DNS server IP
addresses to be allocated to

the peer in PPP negotiation.

ppp ipcp dns
primary-dns-address

[ secondary-dns-address ]

By default, a device does not
allocate DNS server IP addresses

to its peer if the peer does not
request them.

Configuring ACFC negotiation

PPP can compress the address and control fields of PPP packets to increase the payload size.
ACFC negotiation notifies the peer that the local end can receive packets carrying compressed address

and control fields.
ACFC negotiation is implemented at the LCP negotiation stage. After the ACFC negotiation succeeds,

PPP does not include the address and control fields in non-LCP packets. To ensure successful LCP

negotiation, PPP does not apply the compression to LCP packets.
H3C recommends that you use the ACFC configuration option on low-speed links.
To configure the local end to send ACFC requests:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter interface view.

interface interface-type
interface-number

N/A

3.

Configure the local end to
send ACFC requests by

including the ACFC option in

outbound LCP negotiation
requests.

ppp acfc local request

By default, the local end does not
include the ACFC option in

outbound LCP negotiation
requests.

To configure the local end to reject ACFC requests received from the peer:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter interface view.

interface interface-type
interface-number

N/A

3.

Configure the local end to
reject ACFC requests received

from the peer.

ppp acfc remote-reject

By default, the local end accepts
the ACFC requests from the remote

peer, and performs ACFC on

frames sent to the peer.

This manual is related to the following products: