The procedure uses as examples the PPP configuration files that were introduced in How to Define Communications Over the Serial Line on a Dial-In Server.
For more information, see Using Your Assigned Administrative Rights in Securing Users and Processes in Oracle Solaris 11.4.
For example, you would add the options in bold to an existing /etc/ppp/options file to implement PAP authentication:
lock auth login nodefaultroute proxyarp ms-dns 198.51.100.1 idle 120
Where:
auth specifies that the server must authenticate callers before establishing the link.
login specifies that the remote caller be authenticated by using the standard UNIX user authentication services.
nodefaultroute indicates that no pppd session on the local system can establish a default route without root privileges.
proxyarp adds an entry to the system's Address Resolution Protocol (ARP) table that specifies the IP address of the peer and the Ethernet address of the system. With this option the peer appears to be on the local Ethernet to other systems.
ms-dns 198.51.100.1 enables pppd to supply a Domain Name Server (DNS) address, 198.51.100.1, for the client.
idle 120 specifies that idle users are disconnected after two minutes.
:198.51.100.2
:198.51.100.3
* * "" *
See Also
To configure PAP authentication credentials for trusted callers of the dial-in server, refer to Configuring PAP Authentication on Dial-Out Systems for Trusted Callers.