Probelms with diald!

Probelms with diald!

Post by Michael Zwac » Fri, 19 Nov 1999 04:00:00



Hello All,

I have the following problem with diald (or pppd?):

When diald recognizes traffic to the internet, diald
starts the connect-script, but after ~30 seconds
the dialin-script is killed - so the connection is
shut down although the connection has been ok!!!
When I start ppp-up manually it is working fine!

the followin lines have been written to /var/log/messages

pppd[1313]: sent [LCP EchoReg id=0x1 magic=0x5ac4b04e]
pppd[1313]: rcvd [LCP EchoReg id=0x1 magic=0x4a708715]
diald[1290]: Sending SIGINT to (dis)connect process 1312
pppd[1313]: Terminating on signal 2.
.
.
.
ip-down

Please, could anyone help me!!

Maybe my dial-in-script:

/etc/ppp/ppp-up

#!/bin/sh
localip=0.0.0.0
remoteip=
device=/dev/ttyS0
pppflags="38400 modem debug defaultroute"
/usr/sbin/pppd lock connect \
   '/usr/sbin/chat -v -f /etc/ppp/ppp.chat' \
   $device $pppflags $localip:$remoteip

/etc/ppp/ppp.chat

TIMEOUT 30
ABORT "NO CARRIER"
ABORT BUSY
ABORT ERROR
"" +++ATZ
OK #ATDT0,0718912751
CONNECT ""
ogin:--ogin: <username>
word: <password>

/etc/diald.conf

mode ppp
connect "/etc/ppp/ppp-up"
device /dev/ttyS0
speed 115200
modem
lock
crtscts
local 192.168.122.254
remote 192.168.122.253
dynamic
defaultroute
include /usr/lib/diald/standard.filter

I have also tried to use instead of connect "/etc/ppp/ppp-up"
the following line
connect "/usr/sbin/chat -f /etc/ppp/ppp.chat"
but in this case, the modem tries to reset but does not dial?!!

Thanks
Michael

 
 
 

1. 2.2.1, diald, diald-control, pipe, wish

I planned to post this in a greman news group, but then I found some
postings about this subject in this news group. I made some remarks at
the end.

Hallo

Ich konnte dem reissen nicht wiederstehen, kernel 2.2.1 musste her.

Ich habe jetzt ein problem mit dctrl. Oder auch nicht.

Dctrl shickt diald ein request seine monitoring daten durch eine pipe zu
schicken.

Mit kernel 2.2.x erhalte ich folgende fehler in /var/log/messages:

Feb 12 18:04:35 localhost diald[307]: FIFO: full monitor connection to
monitor /tmp/dctrl requested
Feb 12 18:04:35 localhost diald[307]: FIFO: could not open pipe
/tmp/dctrl: Device not configured.

Diald control startet zwar, l?sst sich aber nicht bedienen.
Wenn ich nach einiger zeit den monitor request von hand an diald
schicke,
gehts wieder.

Mein workaround:

-----------------------------------------
#!/bin/bash
#diald-control starten

# -fifo option benutzt?
FIFO=/etc/diald/diald.ctl
while  [ -n "$1" ] ;do
   if [ $1 = "-fifo" ];then
      FIFO=$2
   fi
   shift
done

sleep 5s
# $! ist der zuletzt gestartete hintergrundprozess (PID)
echo monitor /tmp/dctrl.$! > "$FIFO"
-----------------------------------------

Entsprechnde Zeilen aus /usr/bin/dctrl (wish script):

-----------------------------------------
#!/bin/sh
# the next line restarts using wish \

............

proc openFifo {} {
    global fifofd monfifo monfd default_FIFO

    # Turn off any previous monitoring
    if {$monfd!=""} {close $monfd}
    if {$monfifo!=""} {catch {exec rm -f $monfifo}}

    # get new monitoring fifo
    set fifofd [open $default_FIFO w]

    set monfifo /tmp/dctrl.[pid]
    catch {exec mkfifo -m 0600 $monfifo}
    fifoCmd "monitor $monfifo"
    set monfd [open $monfifo r]
    fileevent $monfd readable {stateChange}
----------------------------------

???
catch {exec mkfifo -m 0600 $monfifo}
???
was ist da los?

Versionen:
suse 6.0

diald-0.16.5

tk-4.2p2-35

und wo ist nun dieses 'feature' versteckt?
kernel, wish ,diald oder diald-control?

I had troubles using diald-control (dctrl).
I found a way to overcome this problem. (see my work around).
I think I found the line in the dctrl script that causes the hanging.
    catch {exec mkfifo -m 0600 $monfifo}
    of the  "proc openFifo {}" fragment above.
I don't know howto track it down further.

Kolja

2. Kernel mismatch with Mandrake 8.0 on 7500/100

3. diald problem - pppd won't start from diald

4. Longhorn...does sound so good to me.

5. ip_masq and diald - diald won't bring up link for masq-ed packets

6. Installing NIC on Solaris 8 -- Causing me grief!

7. probelm login on cde

8. Changing groups automaticly

9. W E I R D ftape2.02 probelms...

10. Probelm with custom slot

11. Exabyte Exb4200S 4mm DAT probelms

12. NFS probelms

13. RED HAT 5.0 CDROM MOUNT PROBELMS WITH SONY CDU31A / CDU33A