Thanks for your quick reply. :) No, I didn't get the server side authorization problem, or I don't think I did... But, I have serveral other errors in the log that might be the cuplprit. Here is a portion of my /var/log/messages ---- Feb 25 00:19:04 linuxserver diald[2100]: keepup parsing error. Got token 'tcp.ssl'. Not a known tcp service port. Feb 25 00:19:04 linuxserver diald[2100]: parse string: 'tcp 120 tcp.dest=tcp.ssl' Feb 25 00:19:04 linuxserver diald[2100]: keepup parsing error. Got token 'tcp.ssl'. Not a known tcp service port. Feb 25 00:19:04 linuxserver diald[2100]: parse string: 'tcp 120 tcp.source=tcp.ssl' Feb 25 00:19:06 linuxserver modprobe: can't locate module tap0 Feb 25 00:19:06 linuxserver modprobe: can't locate module tap1 Feb 25 00:19:07 linuxserver modprobe: can't locate module tap2 Feb 25 00:19:07 linuxserver modprobe: can't locate module tap3 Feb 25 00:19:08 linuxserver modprobe: can't locate module tap4 Feb 25 00:19:08 linuxserver modprobe: can't locate module tap5 Feb 25 00:19:09 linuxserver modprobe: can't locate module tap6 Feb 25 00:19:09 linuxserver modprobe: can't locate module tap7 Feb 25 00:19:09 linuxserver modprobe: can't locate module tap8 Feb 25 00:19:10 linuxserver modprobe: can't locate module tap9 Feb 25 00:19:10 linuxserver modprobe: can't locate module tap10 Feb 25 00:19:11 linuxserver modprobe: can't locate module tap11 Feb 25 00:19:11 linuxserver modprobe: can't locate module tap12 Feb 25 00:19:12 linuxserver modprobe: can't locate module tap13 Feb 25 00:19:12 linuxserver modprobe: can't locate module tap14 Feb 25 00:19:13 linuxserver modprobe: can't locate module tap15 Feb 25 00:19:13 linuxserver diald[2101]: start sl1: SIOCSIFMETRIC: Operation not supported Feb 25 00:19:30 linuxserver diald[2101]: Trigger: tcp 192.168.0.12/1101 208.134.200.10/80 Feb 25 00:19:30 linuxserver diald[2101]: Calling site 192.168.0.13 Feb 25 00:19:30 linuxserver diald[2101]: Removed stale lock on ttyS0 (pid 1648) Feb 25 00:19:33 linuxserver connect: Initializing Modem Feb 25 00:19:33 linuxserver connect: Dialing system Feb 25 00:20:00 linuxserver connect: Connected Feb 25 00:20:00 linuxserver connect: Loggin in Feb 25 00:20:15 linuxserver diald[2101]: Trigger: tcp 192.168.0.12/1101 208.134.200.10/80 Feb 25 00:20:30 linuxserver diald[2101]: Connect script timed out. Killing script. Feb 25 00:20:30 linuxserver chat[2132]: SIGINT Feb 25 00:20:30 linuxserver connect: Failed to log in Feb 25 00:20:31 linuxserver diald[2101]: SIGHUP: modem got hung up on. Feb 25 00:20:31 linuxserver diald[2101]: Delaying 30 seconds before clear to dial. ---- I know my ISP uses only PAP authentication, so should a chat script be nessasary? Thanks again. >From: Tim Coleman <[EMAIL PROTECTED]> >To: David Bell <[EMAIL PROTECTED]> >Subject: Re: Diald monitors, ifup dials... Is this possible? >Date: Mon, 28 Feb 2000 07:12:19 -0500 > ><< msg.pgp >> ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
