*Q: The Session ID field in the PPPoE protocol is only 16 bits. Only the Session ID can only indicate 65,000 users. If there are 200,000 users, is there any other field to help mark a subscriber, such as service name? If a BRAS supports multiple service names, what is the maximum number?

A:The session ID cannot be extended. If the maximum number of accesses is exceeded, the newly accessed user is discarded. OpenBRAS can be flexibly scaled, and 200,000 users can be divided into multiple VMs.

*Q:If a Subscriber's traffic reaches the upper limit, how do the new BRAS receive the new packet, and discard it or cache it to the next calculation cycle?

A:The traffic will be discarded directly once reaches the upper limit.

*Q:Does OpenBRAS uplink to the Internet directly forward through the gateway or need to query the route? If the route is queried, does the aging of the routing table need to be done on the card?

A:OpenBRAS handles the user access control process and needs to query routes.

Q:According to the PPPoE protocol, PADI and PADO have the same Host-Uniq. The PADR and PADS packets have the same situation. Is it necessary to save the authentication status on the card and filter the unreasonable packets?

A:PADI, PADO, PADR, and PADS are all in the protocol discovery phase and have not yet reached the certification process. The PPPoE user uses the Session ID+MAC to do the key value search for the user. User information such as authentication status is in the user table.

*Q:Does the card need to be protected against authentication attacks, such as repeated requests for authentication by arrears users, and is this request still sent?

A:The general practice is to use speed limit for protection against authentication attacks.