Subject: Re: pppd as login shell
To: Tom T. Thai <firstname.lastname@example.org>
From: John Nemeth <email@example.com>
Date: 11/10/1996 16:10:32
On Nov 10, 2:42pm, "Tom T. Thai" wrote:
} On Sat, 9 Nov 1996, John Nemeth wrote:
} > On Nov 9, 11:13pm, Jon Buller wrote:
} > }
} > } It seems better to me if I could just make pppd the login shell,
} > } but I need client1 to change based on the login, eliminating (as
} > Put 'server:client1' in ~/.ppprc. If you're doing dynamic
} > addressing, then put it in /etc/ppp/tty.<whatever>.
} > } far as I know) /etc/ppp/options. And putting x:y as a shell argument
} > Use options for common options.
} is there a way to do this by assign each serial line an ip address and
} not have to use the user's home dir at all?
See above. Use /etc/ppp/tty.<whatever>. See man pppd for full
details. If you want to take it one step further, you can use the
latest mgetty beta. It has the option to recognise incoming PPP
packets and automatically start pppd. This will let callers use
PAP/CHAP authentication, and not have to write scripts. If you start
pppd with the 'login' option, it will use the system password file to
do PAP authentication and make utmp entries. I hacked pppd to also
make wtmp entries.
}-- End of excerpt from "Tom T. Thai"