PPPoE
PPPoE Functional Overview
iMG/RG Software Reference Manual (ADSL Port)
8-66
8.7.2.4 Populating automatically routing table and DNS server table
During the PPP connection establishment, the Network Control Protocol IPCP is called to negotiate the IP
address of the local end of the link and to retrieve, eventually, a list of DNS server ip addresses.
The negotiated local IP address is used to assign the ip address value to the un-numbered IP interface attached
to the PPPoE transport. In this case when the PPP session is established, the un-numbered IP interface changes
from having a null IP address to the new negotiated IP address and every time the PPP session is closed, the IP
interface will revert back to having a null IP address.
Note:
Note that, even if the IP interface is attached to a PPP transport, the IP subnet mask is
assumed to be the class-based subnet mask of the IP address that has been allocated.
It’s possible force the PPPoE transport to assign always a 32bit subnet mask (all ones) to the IP interface via the
configuration command:
pppoe set transport <pppoe_name> subnetmask 255.255.255.255
In this way, independently of the IP address value assigned by the Remote Access Server, the IP interface will be
configured as a single host address.
Note:
Note that if more than one PPP connection is active at the same time on the CPE, adjacent IP
addresses can fall into the same subnet causing the IP addresses assignment to fail. In this
case, it’s strongly suggested to force each PPPoE transport to assign a 32bit subnet mask (all
ones) to the IP interface.
The PPPoE transport object is also able to set automatically the CPE default route to use the IP interface to
which the PPPoE object is attached. By default this functionality is turned ON and can be deactivated or re-acti-
vated via the command:
pppoe set transport <pppoe_name> createroute disabled|enabled
Note:
If more than one PPP connection is active at the same time on the CPE, all those, by default,
will try to configure the default route causing possible problems on the proper packets routing.
To avoid this, it’s strongly suggested to have only one PPP session that drives the default
route configuration.
Instead to create the default route when a PPP connection is established successfully, it’s possible inform the
PPPoE transport object to create a specific route based on the IP address of the Remote Access Server and a
subnet mask configured manually. In this case the default route cannot be created automatically because the
PPPoE transport object is able to create only one route (default or specific) at the same time. To inform the
PPPoE module to create a specific rule instead of the default route, the following commands are used:
pppoe set transport <pppoe_name> specifyroute enabled
pppoe set transport <pppoe_name> routemask <specific_route_mask>
The capability of the PPPoE transport object to configure automatically the properties of other modules is also
extended to the DNS Client and DNS Relay modules. It’s possible force, during IPCP phase, the PPP module to