dialup pppd server setup
Byron Young
The configuration of a Linux 2.2.16 server 2.2.16 "correctly" accepts
dialup ppp(2.3.5) access from other linux 2.X machines. Once these
client machines are connected, they have full access to the servers
internet connection and other workstations on the 10BASET LAN. Recently,
I installed windows 95 onto one of the client machines and attempted to
dial into the server using the windows 95 dialup networking dialer. The
current windows 95 dialer configuration allows the windows95 client to
dial into the network and start pppd on the server machine. A physical
connection is established, some information is exchanged, then the
server sends some information to the windows95 client for a few seconds,
then all traffic stops.
On the windows95 machine the ppplog.txt:
08-13-2000 12:22:05.60 - Microsoft Dial Up Adapter log opened.
08-13-2000 12:22:05.60 - Server type is SLIP (Serial Line Protocol).
08-13-2000 12:23:36.18 - Remote access driver is shutting down.
08-13-2000 12:23:36.18 - CRC Errors 0
08-13-2000 12:23:36.18 - Timeout Errors 0
08-13-2000 12:23:36.18 - Alignment Errors 0
08-13-2000 12:23:36.18 - Overrun Errors 0
08-13-2000 12:23:36.18 - Framing Errors 0
08-13-2000 12:23:36.18 - Buffer Overrun Errors 0
08-13-2000 12:23:36.18 - Incomplete Packets 0
08-13-2000 12:23:36.18 - Bytes Received 360
08-13-2000 12:23:36.18 - Bytes Transmittted 93
08-13-2000 12:23:36.18 - Frames Received 18
08-13-2000 12:23:36.18 - Frames Transmitted 3
08-13-2000 12:23:36.18 - Microsoft Dial Up Adapter log closed.
the debug messages from the server are:
Aug 13 12:21:39 waiter pppd[2877]: pppd 2.3.5 started by www, uid 505
Aug 13 12:21:39 waiter pppd[2877]: Using interface ppp0
Aug 13 12:21:39 waiter pppd[2877]: Connect: ppp0 <--> /dev/ttyS1
Aug 13 12:22:09 waiter pppd[2877]: LCP: timeout sending Config-Requests
Aug 13 12:23:12 waiter pppd[2877]: Hangup (SIGHUP)
Aug 13 12:23:12 waiter pppd[2877]: Modem hangup
Aug 13 12:23:12 waiter pppd[2877]: Connection terminated.
Aug 13 12:23:14 waiter pppd[2877]: Exit.
What exactly is going on here, and what must I do on the server side and
the windows95 client side to establish a connection that will allow
network traffic thru the line?
Thanks,
Byron Young
bky...@jps.net
David Efflandt
>The configuration of a Linux 2.2.16 server 2.2.16 "correctly" accepts
>dialup ppp(2.3.5) access from other linux 2.X machines. Once these
>client machines are connected, they have full access to the servers
>internet connection and other workstations on the 10BASET LAN. Recently,
>I installed windows 95 onto one of the client machines and attempted to
>dial into the server using the windows 95 dialup networking dialer. The
>current windows 95 dialer configuration allows the windows95 client to
>dial into the network and start pppd on the server machine. A physical
>connection is established, some information is exchanged, then the
>server sends some information to the windows95 client for a few seconds,
>
>What exactly is going on here, and what must I do on the server side and
>the windows95 client side to establish a connection that will allow
>network traffic thru the line?
You need to enable more extensive debugging temporarily in Linux, at least
kdbug 7, or debug and set up syslog.conf to save that somewhere (and
'killall -HUP syslogd' to have it reread its conf).
If you are doing AutoPPP, I suspect you are using the +pap option which
asks the other 'machine' to authenticate itself, and Windows does not do
that. The confusion is because man pppd is unclear what a peer is (user
or hostname). The auth and login options take care of the user login.
--
David Efflandt effl...@xnet.com http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://hammer.prohosting.com/~cgi-wiz/ http://cgi-help.virtualave.net/