 |
|
| |
| PPPoE |
 |
| |
| Many Service Providers have an existing infra-structure, in which they provision subscribers using the PPP protocol and authenticate them using a RADIUS database. This architecture can be re-used within the context of the Aperto® PacketWave® system, as shown in figure. In order to do this, the system has to be provisioned in one of the following ways: |
| |
| PPPoE Pass Through Mode in the SU |
- The BSU is provisioned in the Bridging mode, so that it transparently passes all Ethernet traffic from its wireless interfaces, onto its wired interface
- Subscriber hosts have PPPoE protocol stack on them, using which they are able to set up a PPPoE session with the Broadband Aggregation Router (BRAS), located in the Service Provider’s metropolitan point of presence.
- All SUs with PPPoE subscribers are provisioned in the bridge mode. SUs may also be provisioned in the NAT or Router modes, but in these cases the hosts behind them will be provisioned using the DHCP server in the SU, rather than the BRAS.
|
|
| PPPoE Termination at the SU |
| In this case the PPPoE session is terminated at the SU, which is provisioned in the NAT mode. The SU obtains a public IP address using the PPPoE protocol and assigns private IP addresses to the hosts in the customer LAN using its own DHCP server. Note that in this case there is no need to install the PPPoE stack on the local hosts. |
| |
| Note that these architectures requires that the Service Provider’s Metropolitan Backbone be based on Layer 2, so that Ethernet packets from the subscriber’s host go all the way to the Broadband Aggregation Router. This can be done using either a Metropolitan Ethernet based backbone, or an ATM based backbone. |
| |
| |
