![]() |
![]() |
| |||||||||||||||||||||||||||||||||||||||||
Chapter 29Setting Up PPP Authentication (Tasks)This chapter contains tasks for setting up PPP authentication. Subjects that are covered include the following: The procedures show how to implement authentication over a dial-up link because dial-up links are more likely to be configured for authentication than leased-line links. You can configure authentication over leased lines if authentication is required by your corporate security policy. For leased-line authentication, use the tasks in this chapter as guidelines. If you want to use PPP authentication but are not sure which protocol to use, review the section Why Use PPP Authentication?. More detailed information about PPP authentication is in the pppd(1M) man page and in Authenticating Callers on a Link. Configuring PPP Authentication (Task Map)This section contains task maps to help you quickly access procedures for PPP authentication. Table 29-1 Task Map for General PPP Authentication
Configuring PAP AuthenticationThe tasks in this section explain how to implement authentication on a PPP link by using the Password Authentication Protocol (PAP). The tasks use the example that is shown in Example--PPP Authentication Configurations to illustrate a working PAP scenario for a dial-up link. Use the instructions as the basis for implementing PAP authentication at your site. Before you perform the next procedures, you must have done the following:
Setting Up PAP Authentication (Task Maps)Use the next task maps to quickly access PAP-related tasks for the dial-in server and trusted callers on dial-out machines. Table 29-2 Task Map for PAP Authentication (Dial-in Server)
Table 29-3 Task Map for PAP Authentication (Dial-out Machine)
Configuring PAP Authentication on the Dial-in ServerTo set up PAP authentication, you must do the following:
|
# user1 myserver "" * user2 myserver "" * myserver user2 serverpass * |
To use the login option of /etc/ppp/pap-secrets, you must type the UNIX user name of each trusted caller. Wherever a set of double quotes ("") appears in the third field, the password for the caller is looked up in the server's password database.
The entry myserver * serverpass * contains the PAP user name and password for the dial-in server. In Figure 26-3, the trusted caller user2 requires authentication from remote peers. Therefore, myserver's /etc/ppp/pap-secrets file contains PAP credentials for use when a link is established with user2.
Task | For Instructions |
|---|---|
Modify the PPP configuration files to support PAP authentication | Modifying the PPP Configuration Files for PAP (Dial-in Server) |
Set up PAP authentication on the dial-out machines of trusted callers | Configuring PAP Authentication for Trusted Callers (Dial-out Machines) |
The tasks in this section explain how to update any existing PPP configuration files to support PAP authentication on the dial-in server.
How to Add PAP Support to the PPP Configuration Files (Dial-in Server)The procedure uses the PPP configuration files that were introduced in How to Define Communications Over the Serial Line (Dial-in Server) as examples.
Log in to the dial-in server as superuser.
Add authentication options to the /etc/ppp/options file.
For example, you would add the options in bold to an existing /etc/ppp/options file to implement PAP authentication:
lock idle 120 nodefaultroute name myserver auth require-pap user myserver remotename user2 login |
Create an /etc/ppp/options.ttyname file, as described in How to Define Communications Over the Serial Line.
Set up the $HOME/.ppprc file for each remote caller, as explained in How to Configure Users of the Dial-in Server.
Previous Contents Index Next ![]() |