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)
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!)
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.
*******************
*here it comes the script I use for manual connection.
ifconfig ippp0 down
ifconfig ippp0
ipppd /dev/ippp0
ifconfig ippp0 up
isdnctrl dial ippp0
#route
PASS=1.1.1.1
while [ $PASS = 1.1.1.1 ]
do
PASS=`ifconfig ippp0 | grep "P-t-P" | awk '......
...... (etc...)
done
route .....
*************************
___________________________________________________________
Do You Yahoo!?
Votre e-mail @yahoo.fr gratuit sur http://courrier.yahoo.fr
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
