PPPoE Interface Configuration Guide

introduction introduction pppoe(point to point protocol over ethernet) is an ethernet based wan access protocol defined by rfc 2516 it combines the authentication, accounting, and link control functions of the ppp(point to point protocol) with the flexible networking features of the ethernet it is mainly used to establish point to point logical connections in a shared ethernet environment explanation of principles explanation of principles pppoe connection establishment is divided into two phases discovery phase discovery phase the discovery phase is completed by the following packets 1 padi(pppoe active discovery initiation)\ the client broadcasts a padi packet to find an available pppoe server 2 pado(pppoe active discovery offer)\ the server responds to the pado message, indicating that the service is available 3 padr(pppoe active discovery request)\ the client selects the server and sends a padr request 4 pads(pppoe active discovery session confirmation)\ the server assigns the session id to confirm the session establishment session phase session phase 1 based on the ppp protocol, lcp(link control protocol) negotiation is completed, authentication packet(chap) authentication, and ipcp(ip control protocol) completes ip address assignment pppoe session termination phase session termination phase session termination phase 1 padt(pppoe active discovery terminate)\ this parameter is generated by a client or server to notify the peer to release pppoe session resources pppoe client configuration pppoe client configuration dial interface configuration dial interface configuration create a logical interface for a pppoe client to centrally manage ppp parameters and bind physical interfaces true 296,175 0861678004535,189 9138321995465#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type ppp authentication user name and password configuration ppp authentication user name and password configuration configure authentication management the pppoe server can use this information to verify the client validity ensure that the user name and password are the same as those configured on the pppoe server true 288,228 8365220839661,144 1634779160339#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type mtu configuration mtu configuration pppoe encapsulation consumes 8 bytes (6 bytes pppoe header + 2 bytes ppp protocol number) to avoid fragmentation and increase the risk of packet loss, flexible adjustment is required in addition, ensure that the end to end mtu is consistent true 228,151 37267011614722,281 6273298838528#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type nat configuration nat configuration to enable intranet devices to access the internet through pppoe public ip addresses, the nat(network address translation) is required true 248,191 70051574783434,221 29948425216566#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type port binding configuration port binding configuration associate a physical interface with a dialer interface to enable pppoe traffic to be transmitted over a specified physical link true 220,194,247#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type pppoe server configuration pppoe server configuration pppoe server is used to provide layer 2 discovery (padi/pado) and layer 3 session capabilities for pppoe clients in the access network through username/password authentication, it dynamically assigns network parameters such as ip addresses and dns to clients, and supports large scale concurrent session control on the sonic device, pppoe server is usually deployed on the physical port or sub interface, which carries the terminal or access server downward, and accesses the internet through the three layer gateway or nat outlet upward pppoe server interface configuration create a logical interface for a pppoe client to centrally manage ppp parameters and bind physical interfaces true 220,227 54246575342464,213 45753424657536 left #4283c7 unhandled content type left #4283c7 unhandled content type left #4283c7 unhandled content type left unhandled content type left unhandled content type left unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type ac name configuration ac name configuration create the access concentrator name for the pppoe server, which will be carried in the pado message as an optional field true 240,217 22307955145527,203 77692044854473 left #4283c7 unhandled content type left #4283c7 unhandled content type left #4283c7 unhandled content type left unhandled content type left unhandled content type left unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type dns server configuration dns server configuration configure the dns ip sent by the pppoe server to the client as an optional field true 278,197 61624576771348,185 38375423228652 left #4283c7 unhandled content type left #4283c7 unhandled content type left #4283c7 unhandled content type left unhandled content type left unhandled content type left unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type service type configuration service type configuration configure the service name of the pppoe server and include this field in the pado message; simultaneously supports two switches, one for specifying the acceptance of any service type from the client, and a total of for specifying the allowed service types for the client to be empty this field is optional true 242,216 19114093125833,202 80885906874167 left #4283c7 unhandled content type left #4283c7 unhandled content type left #4283c7 unhandled content type left unhandled content type left unhandled content type left unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left #d8e5f5 1 1 unhandled content type left #d8e5f5 1 1 unhandled content type left #d8e5f5 1 1 unhandled content type keepalive configuration keepalive configuration configure the keep alive interval on the pppoe server side if the retry count is exceeded, the dead connection will be disconnected this field is optional true 236,219 28695679184915,205 71304320815085 left #4283c7 unhandled content type left #4283c7 unhandled content type left #4283c7 unhandled content type left unhandled content type left unhandled content type left unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type local ip configuration local ip configuration configure the local ip address of the pppoe server, which is the layer 3 address used to establish ppp connections, and be careful not to conflict with the remote ip pool true 237,218 77098748175067,205 22901251824933 left #4283c7 unhandled content type left #4283c7 unhandled content type left #4283c7 unhandled content type left unhandled content type left unhandled content type left unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type mru configuration mru configuration configure the maximum receiving unit on the pppoe server side, which defaults to 1492 the final receiving unit size will be negotiated with the mru value on the client side the final mtu value can be viewed on the ppp interface through the ifconfig command to determine the negotiation result note that the mtu value on the server side is determined entirely based on the mru negotiation results, otherwise the default value of 1492 will be used this field is optional true 236,219 28695679184915,205 71304320815085 left #4283c7 unhandled content type left #4283c7 unhandled content type left #4283c7 unhandled content type left unhandled content type left unhandled content type left unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type remote ip pool configuration remote ip pool configuration configure the pppoe server to provide users with an address pool for dial up authentication addresses, specifying pre configured ip ports that support both range and mask configuration methods true 234,220 3188954120461,206 6811045879539 left #4283c7 unhandled content type left #4283c7 unhandled content type left #4283c7 unhandled content type left unhandled content type left unhandled content type left unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left #d8e5f5 1 1 unhandled content type left #d8e5f5 1 1 unhandled content type left #d8e5f5 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type session max configuration session max configuration configure pppoe server side to support the maximum number of dial up authentication sessions established for clients this field is optional true 288,184 5947259688365,188 4052740311635 left #4283c7 unhandled content type left #4283c7 unhandled content type left #4283c7 unhandled content type left unhandled content type left unhandled content type left unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type left #d8e5f5 unhandled content type example of pppoe client configuration example of pppoe client configuration network requirements when a pppoe server connects to the device, set an authentication user name and password on the server the device has been configured with a pppoe client and correctly obtained an ip address from the server address pool, and can access the internet procedure 1 create dialer interface 1 sonic(config)# interface dialer 1 2 configure the same user name and password as the pppoe server sonic(config dialerif 1)# ppp chap username test1 123abc 3 configure mtu sonic(config dialerif 1)# mtu 1492 4 configure the port binds the dialer interface sonic(config dialerif 1)# exit sonic(config)# interface ethernet 1 sonic(config if 1)# pppoe client 1 verify configuration the device interface has been successfully assigned to the ip address in the pppoe server address pool, after the default route is configured, the device can access the internet example of pppoe server configuration example of pppoe server configuration network requirements the pppoe client accesses the sonic device through the two layer ethernet the device, as the pppoe server, provides user authentication, session establishment and address allocation capabilities the client successfully obtains the address pool ip and accesses the upstream network or internet through the device procedure 1 configure ip pool and configure pppoe server interface sonic(config)# ip pool pppoe pool1 sonic(config ippool pppoe pool1)# ip range 192 168 15 10 192 168 15 20 sonic(config)# interface pppoe server 1 2 configure ip pool and configure pppoe server interface sonic(config if pppoeserver 1)# ppp chap username test1 test1 3 configure the address pool for client ip allocation sonic(config if pppoeserver 1)# remote ip pool pppoe pool1 4 configure the local ip address of the server sonic(config if pppoeserver 1)# local ip 192 168 15 1 255 255 255 0 5 configure other server parameters sonic(config if pppoeserver 1)# dns server 8 8 8 8 sonic(config if pppoeserver 1)# ac name pppoe server 1 sonic(config if pppoeserver 1)# keepalive 15 sonic(config if pppoeserver 1)# mru 1400 sonic(config if pppoeserver 1)# service name test sonic(config if pppoeserver 1)# session max 300 6 port binding pppoe server interface sonic(config)# interface ethernet 2 sonic(config if 2)# pppoe server 1 verify configuration the pc can successfully obtain the ip address in the remote ip pool through dial up authentication of the pppoe server service provided by the device as the server, the device can view the relevant statistics and session establishment status corresponding to each server interface