> What would such a patch entail? Using the remote peername instead of the
> local peername for the utmp entry?
pppd should create utmp entry on username basis.
Let's say user korekhov logged in via ppp0 (assuming PAP auth thru
/etc/passwd), so pppd should put `korekhov` into utmp. So I can do command
`who` and see that korekhov logged in on ttyXX.
Actually, this's what option login must do. It takes username and
password from remote peer, verifies them against /etc/passwd and places
`korekhov` utmp record.
As I said, that *was* working on our old machine with ppp 2.3.3.
And I have no idea why it's not working in later versions.
> > mgetty. If you have the patched pppd, this is how it works. You have to
> > add the option "login" to pppd in login.config and change the third column
> > to "-" (in the example it's a_ppp or ppp).
>
> can't the current pppd maybe already do this the right way? have you tried
> the above?
Oh, yes! I've tried a lot of combinations.
--
Kins Orekhov
Outlook Technologies, Inc.
E-mail: [EMAIL PROTECTED]
Phone: 773-775-2099, ext. 226
http://swoop.outlook.net
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
