I'm trying to tighten up the security on the lone dialup port on our office server now that there are 3 remote users wanting to connect to our local LAN (isolated from the internet). These 3 each run a different OS: 1 runs NT4sp4, 1 runs a patched Win95, and I run Linux (of course). I had been using Linux to connect to Linux with no problems for a couple years now. We're running RH5.2 (ppp-2.3.5). The NT box is giving me fits. Perusing the debug/kdebug output, the NT box (host name NANTUCKET) is giving its host name to the Linux ppp server as 'MSRAS-1-NANTUCKET' as far as I can tell. In the hex data dump, there's a couple of nulls, then the characters 'Mc' before the host name is sent. I see the user's password but not the user's name. LCP handshaking indicates the NT box is agreeing to authenticate with PAP, but I've configured the pap (and chap) secrets files in every convoluted way possible but authentication fails every time. If I remove the 'auth' keyword from the options file it connects fine. But, I don't want unauthenticated connections for obvious reasons. Could this be a side effect from Mgetty? I'm using the Mgetty+sendfax package to monitor the port using Mgetty's 'AutoPPP' option. The debug file also shows pppd being started by LOGIN (uid 0) so I'm assuming this is by way of Mgetty. Adding the 'login' keyword to ppp/options has no effect; without 'auth' anything still connects. Virtually all of the documentation I can find on ppp deals with setting up ppp as a client on a remote host dialing into a server. Would some kind soul point me to a decent FAQ or other info about setting up ppp as a SECURE dialin server? Regards, //Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to [EMAIL PROTECTED]
