Date: Sun, 11 Jan 1998 21:58:08 -0500 From: dmaddox@scsn.net (Donald J. Maddox) To: John Kelly <jak@cetlink.net> Cc: dmaddox@scsn.net, hackers@FreeBSD.ORG Subject: Re: PAP login Message-ID: <19980111215808.59067@scsn.net> In-Reply-To: <34c78c65.11922734@mail.cetlink.net>; from John Kelly on Mon, Jan 12, 1998 at 03:53:51AM %2B0000 References: <19980111150619.48677@scsn.net> <34b95e60.140553@mail.cetlink.net> <34B957B6.AEC4CDAF@scsn.net> <34bf6bef.3609890@mail.cetlink.net> <19980111194120.34679@scsn.net> <34c17b19.7493033@mail.cetlink.net> <19980111203118.15860@scsn.net> <34c48361.9613962@mail.cetlink.net> <19980111211328.42326@scsn.net> <34c78c65.11922734@mail.cetlink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 12, 1998 at 03:53:51AM +0000, John Kelly wrote: > On Sun, 11 Jan 1998 21:13:28 -0500, dmaddox@scsn.net (Donald J. > Maddox) wrote: > > >If I use PPP (which _does_ support channel bonding, and > >which works great under W95 dial-up networking), the modem connects fine, > >but instead of a login prompt, I just get garbage characters from the > >modem. I know the problem is something simple that I am just not quite > >grasping > > Yep! :) > > Those garbage characters you see are the PPP handshake from the ISP. > You simply need to do a PAP authentication directly without any login > script. > > In my /etc/ppp directory is a file called pap-secrets containing three > items of information: > > name remotename password > ---- ---------- -------- > > John BigTimeISP toomanybozos > > > My call to pppd looks like: > > pppd /dev/cuaa3 57600 defaultroute crtscts -bsdcomp \ > asyncmap 00000000 connect /root/pppk/cetchat \ > name John remotename BigTimeISP > > The last line tells pppd to use the password "toomanybozos" from the > pap-secrets file. The "name" must match your user name at your ISP, > likewise for the "password," but the "remotename" can be anything you > choose. > > The "connect /root/pppk/cetchat" is my chat script which contains some > AT commands to initialize the ISDN device, dial the number, and wait > for a CONNECT string, but nothing for logging in to a terminal prompt. > As soon as the chat script gets the CONNECT string, it passes control > back to pppd which starts the PAP authentication. Thanks, John... You are right on the money. I never used PAP before, so I didn't have a clue about this stuff. All is working perfectly now.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980111215808.59067>