Jorge Sousa hat gesagt: // Jorge Sousa wrote:
> I'm trying to use Debian Linux as a ppp dial in server for Win95 clients.
> I'm able to login into the linux box only if I have the - Bring terminal
> window after dialing - check box checked. If this checkbox is off the line
> goes down after a while.
>
> If I login using the terminal window I'm stucked inside a very small window
> and cannot interact with my win95 system.
>
> How can I assign a IP address to the caller's interface?
> How can I be validated using AutoPPP?
> How to avoid the terminal window?
> Which log files can I send to the list to get some help?
> I've read a lot of files, followed some examples but still missing something
> on the authentication side.
Hi Jorge,
I did set up a ppp server just yesterday after A LOT of problems. But now it
is working, yeah.
-= THE GOAL =-
The dialin server has the IP-number 192.168.0.1 in my LAN. Incoming
connections shall get the IP-Number 192.168.0.50. All normal users on
192.168.0.1 should be allowed to dial in using their passwords.
-= THE RUN =-
First I installed the usual packages, i.e. pppd and mgetty.
They have to be configured. Don't change /etc/ppp/options! Put inbound
options in the options file for your modem port.
My [EMAIL PROTECTED] sits at ttyS0 so I edited /etc/ppp/options.ttyS0
(copied from options.ttyXX) to give the incoming calls the right IP-Number:
<--------------------------------------------------->
# /etc/ppp/options.ttyS0:
# Edit the following line so that the first IP address
# mentioned is the is the IP address of your host while the second
# is the ip address of the serial port
192.168.0.1:192.168.0.50
# DEBUG is good at first
debug
# END options
<--------------------------------------------------->
Now comes the critical part:
Win95 prefers PAP so I had to setup the file /etc/ppp/pap-secrets
The secrets file in my pppd-package has a bug, I think, which caused
authentification to fail. The right way is this:
<--------------------------------------------------->
# /etc/ppp/pap-secrets:
# INBOUND connections
# Every regular user can use PPP and has to use passwords from /etc/passwd
# From debian mailing list:
* * "" 192.168.0.50
# ^ this number HAS to be the SAME as in
# the file "options.ttyS0" (IMPORTANT)
# UserIDs that cannot use PPP at all. Check your /etc/passwd and add any
# other accounts that should not be able to use pppd!
guest fliwatut "*" -
master fliwatut "*" -
root fliwatut "*" -
support fliwatut "*" -
stats fliwatut "*" -
# OUTBOUND connections
# your stuff here [...]
<--------------------------------------------------->
The last file to check is /etc/mgetty/login.config
The line starting with /AutoPPP/ should be uncommented and read something
like:
/AutoPPP/ - - /usr/sbin/pppd auth +pap -chap login -detach
^ this can also be 'a_ppp' or just an '@'
and you maybe don't need the -detach option.
-= THE SMOKE TESTS =-
On the client side there should be no further configuration necessary.
Just make a new dialup connection to your debian machine as described
in /usr/doc/ppp/win95.ppp
Now watch incoming calls in the following two places:
/var/log/mgetty/mg_ttyS0.log
* should show mgetty starting the pppd
Example:
[...]
02/08 15:58:40 yS0 tio_set_flow_control( HARD )
02/08 15:58:40 yS0 print welcome banner (/etc/issue)
02/08 15:58:40 yS0 getlogname (FIDO AUTO_PPP), read:~[ff]}#[c0]!
02/08 15:58:42 yS0 input finished with '\r', setting ICRNL ONLCR
02/08 15:58:42 yS0 tio_get_rs232_lines: status: RTS CTS DSR DTR DCD
02/08 15:58:42 yS0 login: use login config file /etc/mgetty/login.config
02/08 15:58:42 yS0 match: user='/AutoPPP/', key=''
02/08 15:58:42 yS0 match: user='/AutoPPP/', key=''
02/08 15:58:42 yS0 match: user='/AutoPPP/', key='/AutoPPP/'*** hit!
02/08 15:58:42 yS0 calling login: cmd='/usr/sbin/pppd', argv[]='pppd auth
+pap -chap login -detach'
02/08 15:58:42 ##### data dev=ttyS0, pid=1063, caller='none',
conn='33600/LAPM/V42BIS', name='', cmd='/
usr/sbin/pppd', user='/AutoPPP/'
[...]
/var/log/ppp.log
* shows the gory details of two pppds talking to each other, checking
passwords and negotiating IP adresses.
One last tip:
If you can do, then try dialing into the debian machine from another debian
or linux system. You will get a lot more debuging info this way.
Hope this helps. Happy dialing,
--
__ __
Frank Barknecht ____ ______ ____ __ trip\ \ / /wire ______
/ __// __ /__/ __// // __ \ \/ / __ \\ ___\
/ / / ____/ / / / // ____// /\ \\ ___\\____ \
/_/ /_____/ /_/ /_//_____// / \ \\_____\\_____\
/_/ \_\
