I use diald 0.99.4 on my Debian 2.2 gateway, and found a few problems...
In the inclosed syslog, you'll see that the second trigger is wrong, and
shouldn't really happen at all.
Steve
Apr 22 10:14:07 slinky diald[839]: Trigger: udp 192.168.66.1/1024 20
3.56.8.1/53
Apr 22 10:14:07 slinky diald[839]: Calling site 203.56.8.153
Apr 22 10:14:35 slinky diald[839]: Connected to site 203.56.8.153
Apr 22 10:14:35 slinky diald[839]: Running pppd (pid = 1529).
Apr 22 10:14:37 slinky diald[839]: New addresses: local 216.132.22.196, remote 2
03.56.8.153, broadcast 0.0.0.0
Apr 22 10:14:37 slinky diald[839]: start ppp0: SIOCSIFMETRIC: Operation not supp
orted
Apr 22 10:18:13 slinky diald[839]: Closing down idle link.
Apr 22 10:18:13 slinky diald[839]: start sl0: SIOCSIFMETRIC: Operation not suppo
rted
Apr 22 10:18:16 slinky diald[839]: Delaying 30 seconds before clear to dial.
Apr 22 10:20:10 slinky diald[839]: Trigger: udp 198.41.0.10/53 192.
168.66.1/1024
Apr 22 10:20:10 slinky diald[839]: Calling site 203.56.8.153
Apr 22 10:20:38 slinky diald[839]: Connected to site 203.56.8.153
