-----Original Message-----
From: Sleep Zz [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, September 23, 1999 11:08 AM
To: [EMAIL PROTECTED]
Subject: ipppd and diald problems
I found the reason of my last problem.
Actually, diald make a pppd start timeout (60s by
default) because there is a conflict between my
connect script and pppd that diald uses.
Does someone know how diald deals with ipppd and ISDN?
ippp0 must be configure before dial up. (see my script
below)
To dialup, I have to use "isdnctrl dial ippp0"
A strange thing I noticed is that dev mode must ignore
connect and disconnect command in diald conf file, but
actually it doesnt !!!
Addroute adn delroute are runs but i don't understand
when and why.
Ip-up and Ip-down are never run.
How does diald route dynamically ? (how works dynamic
option)
It's not diald that does the routing. Pppd handles that.
Diald uses the diald.conf file to determine what parameters to pass to pppd.
I used dctrl. I see states Down, Close and Start_link.
is there another one "connected" i haven't seen ?
There is no dialing log or load (the physical link is
not done!)
Yeah, there's a connected state. I don't recall if that's
the term used, though. The START_LINK state says that diald is trying to
establish a connection.
As you can see, I'm completely lost :) and diald is a
very important thing on our server...
for informations: I use diald 0.16 from red hat6.0 rpm
file.
You might try using a newer version. The most recent
version is 0.99.1. You can get it in RPM format (along with thousands of
other programs) at rufus.w3.org; the page w/diald is
http://rufus.w3.org/linux/RPM/DByName.html
<http://rufus.w3.org/linux/RPM/DByName.html> . You want to get the
diald-0.99.1-10 and diald-config-0.1-1 packages.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
