On Mon, 7 Jan 2002 at 12:31, Michael Balcos wrote: > Welp, I guess I have to rely with my scripts for the while. But I have > that funny feeling that my login procedures will complicate a little, > especially when I've never used AutoPPP before. Hmmm... Does this > AutoPPP adjust to the kind of OS a dialup client is using? Also, does it > handle the modems like the "getty"s?
On the server you normally have mgetty listening to a port conventionally handled by inittab (but definitely handlable by anything else of similar nature) via an entry like: M0:2345:respawn:/sbin/mgetty -s 57600 -n 1 -D ttyS0 mgetty is configured to have AutoPPP support, defined via /etc/mgetty/login.config as an entry like so: /AutoPPP/ - a_ppp /usr/sbin/pppd auth -chap +pap login -detach Easily deducible from this, mgetty passes things on to pppd. I have an /etc/ppp/options.ttyS0 file that tells ppp how to handle that port. Normally I have stuff like the IP address, remote name, default DNS and WINS servers, that the defaultroute shouldn't be touched, and most significantly, that pap authentication should be used via an entry +pap With a setup like this, all the client has to do is define the phone number, login name, password, and that TCP/IP be used. No more DNS or IP address settings: pppd assigns them all (thanks to the options file). Neat eh? Not that hard at all. And AFAIK PAP authentication is standard. :) --> Jijo -- Federico Sevilla III :: [EMAIL PROTECTED] Network Administrator :: The Leather Collection, Inc. GnuPG Key: http://jijo.leathercollection.ph/jijo.gpg _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
