Hello diald gurus,

At work, we are currently having a big big problem with diald.
kernel 2.0.36
diald 0.16.5a
redhat 5.1
RNIS connection (Courrier I-Modem)

Everything has been working fine for several months and with different
ISPs.
Same thing with our latest ISP during at least 2 or 3 months.

But... since late february, we can't get rid of this problem:

"dialdc up" works fine, every time I call it manually.
but if a host (even our gateway which is running diald) makes a request
to an internet site, see what's happening:

Mar 26 10:50:11 hermes syslogd 1.3-3: restart.
Mar 26 10:50:20 hermes diald[368]: FIFO. Changing debug flags to 93.
Mar 26 10:50:24 hermes diald[368]: filter accepted rule 1 proto 6 len 60
seq b0eec30a ack 0 flags  SYN packet 192.168.33.66,1026 =>
195.83.118.1,21
Mar 26 10:50:24 hermes diald[368]: Adding connection 134618448 @
922441824 - timeout 60
Mar 26 10:50:24 hermes diald[368]: new state CONNECT action 134540880
timeout 60
Mar 26 10:50:25 hermes diald[368]: Running connect (pid = 379).
Mar 26 10:50:27 hermes diald[368]: filter accepted rule 1 proto 6 len 60
seq b0eec30a ack 0 flags  SYN packet 192.168.33.66,1026 =>
195.83.118.1,21
Mar 26 10:50:27 hermes diald[368]: Adding connection 134618448 @
922441827 - timeout 60
Mar 26 10:50:29 hermes diald[368]: SIGCHLD[4]: pid 379 dial, status 0
Mar 26 10:50:29 hermes diald[368]: new state START_LINK action 134541632
timeout 60
Mar 26 10:50:29 hermes diald[368]: Running pppd (pid = 380).
Mar 26 10:50:29 hermes pppd[380]: pppd 2.3.5 started by root, uid 0
Mar 26 10:50:29 hermes pppd[380]: Using interface ppp0
Mar 26 10:50:29 hermes pppd[380]: Connect: ppp0 <--> /dev/ttyS0
Mar 26 10:50:30 hermes pppd[380]: sent [LCP ConfReq id=0x1 <asyncmap
0x0> <magic 0x5020e421> <pcomp> <accomp>]
Mar 26 10:50:30 hermes pppd[380]: rcvd [LCP ConfReq id=0x1 < 00 04 00
00> <mru 1524> <asyncmap 0xa0000> <auth pap> <pcomp> <accomp> < 11 04 05
f4> < 13 09 03 00 c0 7b 7e 0a e5>]
Mar 26 10:50:30 hermes pppd[380]: sent [LCP ConfRej id=0x1 < 00 04 00
00> < 11 04 05 f4> < 13 09 03 00 c0 7b 7e 0a e5>]
Mar 26 10:50:30 hermes pppd[380]: rcvd [LCP ConfReq id=0x2 <mru 1524>
<asyncmap 0xa0000> <auth pap> <pcomp> <accomp>]
Mar 26 10:50:30 hermes pppd[380]: sent [LCP ConfAck id=0x2 <mru 1524>
<asyncmap 0xa0000> <auth pap> <pcomp> <accomp>]
Mar 26 10:50:33 hermes pppd[380]: sent [LCP ConfReq id=0x1 <asyncmap
0x0> <magic 0x5020e421> <pcomp> <accomp>]
Mar 26 10:50:33 hermes pppd[380]: rcvd [LCP ConfAck id=0x1 <asyncmap
0x0> <magic 0x5020e421> <pcomp> <accomp>]
Mar 26 10:50:33 hermes pppd[380]: sent [PAP AuthReq id=0x1 user="i'm
not" password="that dumb :)"]
Mar 26 10:50:33 hermes diald[368]: filter accepted rule 1 proto 6 len 60
seq b0eec30a ack 0 flags  SYN packet 192.168.33.66,1026 =>
195.83.118.1,21
Mar 26 10:50:33 hermes diald[368]: Adding connection 134618448 @
922441833 - timeout 60
Mar 26 10:50:33 hermes pppd[380]: rcvd [PAP AuthAck id=0x1 ""]
Mar 26 10:50:33 hermes pppd[380]: Remote message: 
Mar 26 10:50:33 hermes pppd[380]: sent [IPCP ConfReq id=0x1 <addr
0.0.0.0>]
Mar 26 10:50:33 hermes pppd[380]: rcvd [IPCP ConfReq id=0x1 <compress VJ
0f 01> <addr 195.154.11.129>]
Mar 26 10:50:33 hermes pppd[380]: sent [IPCP ConfRej id=0x1 <compress VJ
0f 01>]
Mar 26 10:50:33 hermes pppd[380]: rcvd [IPCP ConfNak id=0x1 <addr
212.43.203.47>]
Mar 26 10:50:33 hermes pppd[380]: sent [IPCP ConfReq id=0x2 <addr
212.43.203.47>]
Mar 26 10:50:33 hermes pppd[380]: rcvd [IPCP ConfReq id=0x2 <addr
195.154.11.129>]
Mar 26 10:50:33 hermes pppd[380]: sent [IPCP ConfAck id=0x2 <addr
195.154.11.129>]
Mar 26 10:50:33 hermes pppd[380]: rcvd [IPCP ConfAck id=0x2 <addr
212.43.203.47>]
Mar 26 10:50:33 hermes pppd[380]: local  IP address 212.43.203.47
Mar 26 10:50:33 hermes pppd[380]: remote IP address 195.154.11.129
Mar 26 10:50:34 hermes diald[368]: New addresses: local 212.43.203.47,
remote 195.154.11.129.
Mar 26 10:50:34 hermes diald[368]: Setting pointopoint route for ppp0
Mar 26 10:50:34 hermes diald[368]: running '/sbin/route add
195.154.11.129 metric 0  dev ppp0'
Mar 26 10:50:34 hermes diald[368]: SIGCHLD[5]: pid 383 system, status 0
Mar 26 10:50:34 hermes diald[368]: Establishing routes for ppp0
Mar 26 10:50:34 hermes diald[368]: running '/sbin/route add default
metric 0  dev ppp0'
Mar 26 10:50:34 hermes diald[368]: SIGCHLD[6]: pid 384 system, status 0
Mar 26 10:50:34 hermes diald[368]: new state UP action 134542064 timeout
120
Mar 26 10:50:34 hermes diald[368]: Changed snoop device to ppp0
Mar 26 10:50:37 hermes pppd[380]: Hangup (SIGHUP)
Mar 26 10:50:37 hermes pppd[380]: Modem hangup
Mar 26 10:50:37 hermes pppd[380]: Connection terminated.
Mar 26 10:50:37 hermes pppd[380]: Exit.
Mar 26 10:50:37 hermes diald[368]: SIGCHLD[7]: pid 380 link, status 256
Mar 26 10:50:37 hermes diald[368]: running '/sbin/ifconfig sl0 127.0.0.3
pointopoint 127.0.0.2 mtu 1500 up'
Mar 26 10:50:38 hermes diald[368]: SIGCHLD[8]: pid 387 system, status 0
Mar 26 10:50:38 hermes diald[368]: Setting pointopoint route for sl0
Mar 26 10:50:38 hermes diald[368]: running '/sbin/route add 127.0.0.2
metric 1  dev sl0'
Mar 26 10:50:38 hermes diald[368]: SIGCHLD[9]: pid 391 system, status 0
Mar 26 10:50:38 hermes diald[368]: Establishing routes for sl0
Mar 26 10:50:38 hermes diald[368]: running '/sbin/route add default
metric 1  dev sl0'
Mar 26 10:50:38 hermes diald[368]: SIGCHLD[10]: pid 392 system, status 0
Mar 26 10:50:38 hermes diald[368]: Removing routes for ppp0
Mar 26 10:50:38 hermes diald[368]: running '/sbin/route del default
metric 0 dev ppp0'
Mar 26 10:50:38 hermes diald[368]: SIGCHLD[11]: pid 393 system, status
1792
Mar 26 10:50:38 hermes diald[368]: Deleting pointopoint route for ppp0
Mar 26 10:50:38 hermes diald[368]: running '/sbin/route del
195.154.11.129 metric 0 dev ppp0'
Mar 26 10:50:38 hermes diald[368]: SIGCHLD[12]: pid 394 system, status
1792
Mar 26 10:50:38 hermes diald[368]: Link died on remote end.
Mar 26 10:50:38 hermes diald[368]: running '/sbin/ifconfig sl0 127.0.0.3
pointopoint 127.0.0.2 mtu 1500 up'
Mar 26 10:50:39 hermes diald[368]: SIGCHLD[13]: pid 395 system, status 0
Mar 26 10:50:39 hermes diald[368]: Setting pointopoint route for sl0
Mar 26 10:50:39 hermes diald[368]: running '/sbin/route add 127.0.0.2
metric 1  dev sl0'
Mar 26 10:50:39 hermes diald[368]: SIGCHLD[14]: pid 399 system, status 0
Mar 26 10:50:39 hermes diald[368]: Establishing routes for sl0
Mar 26 10:50:39 hermes diald[368]: running '/sbin/route add default
metric 1  dev sl0'
Mar 26 10:50:39 hermes diald[368]: SIGCHLD[15]: pid 400 system, status 0
Mar 26 10:50:39 hermes diald[368]: Closed fwdfd
Mar 26 10:50:39 hermes diald[368]: Changed snoop device to sl0
Mar 26 10:50:39 hermes diald[368]: new state DISCONNECT action 134542768
timeout 120
Mar 26 10:50:39 hermes diald[368]: new state CLOSE action 134542912
timeout -1
Mar 26 10:50:39 hermes diald[368]: Closing modem line.
Mar 26 10:50:41 hermes diald[368]: new state RETRY action 134543216
timeout -1
Mar 26 10:50:42 hermes diald[368]: new state CONNECT action 134540880
timeout 60
...

And it restarts again and again 3 or 4 times until the link no more
falls down and remains up.

I don't understant what's happening. I didn't changed anything in the
diald's conf files.

I've tried with another ISP: it works !
I've tried with a simple "pppd and chat" script, it works, as "dialdc
up" does.
I've re-installed another Linux distributions, such as Suse 6.0 kernel
2.0.36 or RedHat 5.1 kernel 2.2.5, and configured diald from scratch:
same problem !

It is really a problem because the call doesn't completely fail. And
before the link die, it costs us money !

Any idea ?

Regards,
Eric

-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to