Warning, this is a long post
I really hope a diald guru reads this.

I have RH 7.3 and diald 1.0 (or so the man page says)
I have for months now struggled with this system to get samba, squid, named, firestarter and now diald working. I have everything working except diald which works but cannot actually dial.

I have the system working well and had used gnome utilities to create my ppp connection and start and stop it. I can also start my dial up connection with this command
/etc/sysconfig/network-scripts/ifup ifcfg-ppp0
so I know everything is working properly (or so it seems)

I have installed diald (v1.0)
then when I realised that it came with no configuration scripts and that my understanding was way too little, I looked and found these rpms
diald-config-1.2.1-1.noarch.rpm
diald-config-unmetered-0.2-2.noarch.rpm
I installed both of them (didn't find the second one until after I had installed the first). So now I have the latest version of diald and config files for much older versions. I have fumbled on and almost got diald working.
When diald starts these messages appear in /var/log/messages

May 4 21:59:15 leeper diald[3545]: ignore parsing error. Got token 'udp.route'. Not a known udp service port.
May 4 21:59:15 leeper diald[3545]: parse string: 'udp tcp.dest=udp.route'
May 4 21:59:15 leeper diald[3545]: ignore parsing error. Got token 'udp.route'. Not a known udp service port.
May 4 21:59:15 leeper diald[3545]: parse string: 'udp tcp.source=udp.route'
May 4 21:59:15 leeper diald[3545]: ignore parsing error. Got token 'udp.route'. Not a known udp service port.
May 4 21:59:15 leeper diald[3545]: parse string: 'udp udp.dest=udp.route'
May 4 21:59:15 leeper diald[3545]: ignore parsing error. Got token 'udp.route'. Not a known udp service port.
May 4 21:59:15 leeper diald[3545]: parse string: 'udp udp.source=udp.route'
May 4 21:59:15 leeper diald[3545]: ignore parsing error. Got token 'udp.route'. Not a known udp service port.
May 4 21:59:15 leeper diald[3545]: parse string: 'udp tcp.dest=udp.route'
May 4 21:59:15 leeper diald[3545]: ignore parsing error. Got token 'udp.route'. Not a known udp service port.
May 4 21:59:15 leeper diald[3545]: parse string: 'udp tcp.source=udp.route'
May 4 21:59:15 leeper diald[3545]: accept parsing error. Got token 'any'. Expecting a number.
May 4 21:59:15 leeper diald[3545]: parse string: 'any any ny'
May 4 21:59:16 leeper modprobe: modprobe: Can't locate module tap0
May 4 21:59:16 leeper modprobe: modprobe: Can't locate module tap1
May 4 21:59:16 leeper modprobe: modprobe: Can't locate module tap2
May 4 21:59:16 leeper modprobe: modprobe: Can't locate module tap3
May 4 21:59:16 leeper modprobe: modprobe: Can't locate module tap4
May 4 21:59:16 leeper modprobe: modprobe: Can't locate module tap5
May 4 21:59:16 leeper modprobe: modprobe: Can't locate module tap6
May 4 21:59:16 leeper modprobe: modprobe: Can't locate module tap7
May 4 21:59:16 leeper modprobe: modprobe: Can't locate module tap8
May 4 21:59:17 leeper modprobe: modprobe: Can't locate module tap9
May 4 21:59:17 leeper modprobe: modprobe: Can't locate module tap10
May 4 21:59:17 leeper modprobe: modprobe: Can't locate module tap11
May 4 21:59:17 leeper modprobe: modprobe: Can't locate module tap12
May 4 21:59:17 leeper modprobe: modprobe: Can't locate module tap13
May 4 21:59:17 leeper modprobe: modprobe: Can't locate module tap14
May 4 21:59:17 leeper modprobe: modprobe: Can't locate module tap15
May 4 21:59:17 leeper diald[3550]: start sl0: SIOCSIFMETRIC: Operation not supported

I have reduced the ignore parase errors. I'm not worried about them
I don't know about the line parse string: 'any any ny'
The modprobe messages I've seen mentioned in many posts, but am no wiser about them
Diald triggers OK but fails to dial. It is looking for a file to pass to chat. By experimenting I've found that the file is called
/etc/sysconfig/network-scripts/chat-
but I don't know what should be in this file. I also believe it should be looking for a file called chat-ppp0 instead of chat-
diald also seems to ignore the connect statement in diald.conf
If I create the file chat- then these lines appear in /var/log/messages

May 4 21:59:18 leeper diald[3550]: Trigger: udp 192.168.0.1/1025 192.58.128.30/53
May 4 21:59:18 leeper diald[3550]: Calling site 192.168.0.254
May 4 21:59:20 leeper chat[3692]: expect (USERCTL='yes')
May 4 22:00:05 leeper chat[3692]: alarm
May 4 22:00:05 leeper chat[3692]: Failed
May 4 22:00:05 leeper diald[3550]: Connect script failed.
May 4 22:00:06 leeper diald[3550]: Delaying 1 seconds before clear to dial.

ttyS1 is locked but the line is not picked up.
BTW (USERCTL='yes') is the first line in the chat- file I created (I had put a diald connect file there)

Any ideas?