John,
Apparently the problem is in 'chat': Feb 8 19:16:14 logan chat[623]: Can't
get terminal parameters: Invalid argument
Try running 'chat' manually (using the same parameters that the diald script
is using) and see what happens.
Good luck.
Paulo Abreu
> -----Original Message-----
> From: John LeMay [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, February 08, 1999 8:41 PM
> To: [EMAIL PROTECTED]
> Subject: diald stopped functioning!
>
> Help! I rebooted my box today and no diald won't connect. I can't figure
> out what might have changed that would have effected this since the last
> reboot, but it was working right up until the second I bounced it! My
> reason for bouncing was that I changed the hostname in
> /etc/sysconfig/network (new domain name). Here's what I get:
>
> It's giving me a chat error:
>
> Feb 8 19:15:52 logan diald[612]: Creating FIFO
> Feb 8 19:15:52 logan diald[612]: FIFO closed
> Feb 8 19:16:12 logan diald[612]: Trigger: udp
> 192.168.0.1/1024 205.164.220.1/53
> Feb 8 19:16:12 logan diald[612]: Calling site 192.168.0.2
> Feb 8 19:16:13 logan diald[612]: Running connector (pid = 621).
> Feb 8 19:16:14 logan connect: Initializing Modem
> Feb 8 19:16:14 logan chat[623]: Can't get terminal parameters: Invalid
> argument
> Feb 8 19:16:14 logan diald[612]: Connect script failed.
> Feb 8 19:16:14 logan connect: Failed to initialize modem
> Feb 8 19:16:15 logan diald[612]: Delaying 5 seconds before clear to
> dial.
> Feb 8 19:16:21 logan diald[612]: Calling site 192.168.0.2
> Feb 8 19:16:22 logan diald[612]: Running connector (pid = 626).
> Feb 8 19:16:22 logan connect: Initializing Modem
> Feb 8 19:16:22 logan chat[628]: Can't get terminal parameters: Invalid
> argument
> Feb 8 19:16:22 logan diald[612]: Connect script failed.
> Feb 8 19:16:22 logan connect: Failed to initialize modem
>
> My /etc/diald.conf looks like:
>
> [jlemay@logan jlemay]$ cat /etc/diald.conf
> # Bearcave standard diald configuration
> #
> device /dev/tty1
> lock
> speed 115200
> modem
> crtscts
>
> # Timeouts and retry limits
> connect-timeout 90
> retry-count 0
> died-retry-count 0
> dial-fail-limit 4
> redial-timeout 5
>
> # Diald 0.98+ settings
> scheduler fifo
> priority -2
>
> # Demon-specific coniguration.
> #
> local 192.168.0.1 # Your Demon IP
> remote 192.168.0.2
> mode ppp
> defaultroute
> dynamic
> connect /etc/demon-connect
> pppd-options debug user jlemay
>
> accounting-log /var/log/diald/calls
> pidfile diald.demon.pid
>
> # Line up and down scripts
> # ip-up /usr/local/lib/diald/ip-up
> # ip-down /usr/local/lib/diald/ip-down
>
> # The command fifo. There's a link to this
> # in /etc/diald so dctrl will find it.
> fifo /etc/diald/diald.ctl
>
> # Diald 0.98+ settings
> linkname Demon
> linkdesc Demon and the big wide world
>
> include /usr/lib/diald/standard.filter
>
>
> And my /etc/demon-connect:
>
> [jlemay@logan jlemay]$ cat /etc/demon-connect
> #!/bin/sh
> #
> # This script is hacked from an example provided with the most excellent
> # diald.
>
> # Configuration parameters
>
> # The initialization string for your modem
> MODEM_INIT="AT&f@b0=2%a2=95%a4=1"
>
> # The phone number to dial
> PHONE_NUMBER="4498579&8579" # Energis, good for k56 for me
>
> # The chat command. chat -v logs the chatting to the syslog.
> CHAT="/usr/sbin/chat -v"
> # CHAT="chat"
>
> # Pass a message on to diald and the system logs.
> function message () {
> [ $FIFO ] && echo "message $*" >$FIFO
> logger -p local2.info -t connect "$*"
> }
>
> # Initialize the modem. Usually this just resets it.
> message "Initializing Modem"
> $CHAT TIMEOUT 5 "" $MODEM_INIT TIMEOUT 45 OK "\c"
> if [ $? != 0 ]; then
> message "Failed to initialize modem"
> exit 1
> fi
>
> # Dial the remote system.
>
> message "Dialing system"
> $CHAT \
> TIMEOUT 45 \
> ABORT "NO CARRIER" \
> ABORT BUSY \
> ABORT "NO DIALTONE" \
> ABORT ERROR \
> "" ATDT$PHONE_NUMBER \
> CONNECT "\c"
> case $? in
> 0) message Connected;;
> 1) message "Chat Error"; exit 1;;
> 2) message "Chat Script Error"; exit 1;;
> 3) message "Chat Timeout"; exit 1;;
> 4) message "No Carrier"; exit 1;;
> 5) message "Busy"; exit 1;;
> 6) message "No DialTone"; exit 1;;
> 7) message "Modem Error"; exit 1;;
> *)
> esac
>
> # Success!
> # This already happens...
> # message "Connection made"
>
>
>
> Please help!!!
>
> ---
>
> John J. LeMay Jr.
> NJMC, LLC.
> http://www.njmc.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
application/ms-tnef
