On Mon, 12 Apr 1999, F. Brekeveld wrote:
> When using diald the connection is setup but after a few seconds
> terminated,
> here is a piece of the messages file:
>
> -----------------------------------------------------------------------
> Apr 12 14:11:46 dpp180 diald[1936]: Running connect (pid = 1946).
> Apr 12 14:12:10 dpp180 diald[1936]: Running pppd (pid = 1948).
> Apr 12 14:12:10 dpp180 kernel: PPP: version 2.2.0 (dynamic channel
> allocation)
> Apr 12 14:12:10 dpp180 kernel: PPP Dynamic channel allocation code
> copyright 199
> 5 Caldera, Inc.
> Apr 12 14:12:10 dpp180 kernel: PPP line discipline registered.
> Apr 12 14:12:10 dpp180 kernel: registered device ppp0
> Apr 12 14:12:10 dpp180 pppd[1948]: pppd 2.3.5 started by root, uid 0
> Apr 12 14:12:10 dpp180 pppd[1948]: Using interface ppp0
> Apr 12 14:12:10 dpp180 pppd[1948]: Connect: ppp0 <--> /dev/ttyS1
> Apr 12 14:12:18 dpp180 pppd[1948]: Hangup (SIGHUP)
> Apr 12 14:12:18 dpp180 pppd[1948]: Modem hangup
> Apr 12 14:12:18 dpp180 pppd[1948]: Connection terminated.
> Apr 12 14:12:19 dpp180 pppd[1948]: Exit.
> Apr 12 14:12:19 dpp180 modprobe: can't locate module net-pf-4
> Apr 12 14:12:19 dpp180 modprobe: can't locate module net-pf-5
> Apr 12 14:12:19 dpp180 modprobe: can't locate module net-pf-4
> Apr 12 14:12:20 dpp180 modprobe: can't locate module net-pf-5
> Apr 12 14:12:21 dpp180 diald[1936]: Delaying 30 seconds before clear to
> dial.
> Apr 12 14:14:19 dpp180 kernel: PPP: ppp line discipline successfully
> unregistere
> d
> Apr 12 14:14:33 dpp180 modprobe: can't locate module net-pf-4
> Apr 12 14:14:33 dpp180 modprobe: can't locate module net-pf-5
> -----------------------------------------------------------------------
> Here is the /etc/diald.conf
>
> mode ppp
> connect "/usr/sbin/chat -f /etc/sysconfig/network-scripts/chat-ppp0"
> device /dev/ttyS1
> speed 57600
> modem
> lock
> crtscts
> local 192.168.0.141
> remote 192.168.0.2
> dynamic
> defaultroute
> include /usr/lib/diald/standard.filter
>
Hi!
Some suggestions :
Did you compile PPP/SLIP (and related stuff) support into your current
kernel. I think those missing modules modprobe cries for may be
cause of your problem! If thye're really missing compile your new
kernel with those modules enabled (have fun :-)).
Afterwards:
Try to connect manually (that is using minicom, typing
atdt<ProviderNumber> and logging in. Exit minicom without terminating the
connection (don't know the actual command, look at the online help
which is available via Ctrl-A i suppose)
Afterwards try running your well configured pppd.
Well configured means that you should create a options file as
talked about in pppd's manpage.
Remember : Diald runs chat for authentication purposes and then
invokes pppd to establish the ppp-connection.
For the passing of options from diald to pppd you should
have a close look at the manpages (which i loved to read
setting up that stuff on my own; by the way i'm using
a config with 3 linux/win95/win311/dos(netware)- clients
dialing out via a linux gateway to my provider)
good luck
Michael Wirz
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
