Thread View: comp.os.linux.networking
1 messages
1 total messages
Started by Mat Ballard
Thu, 02 Apr 1998 00:00
DIALD Problems
Author: Mat Ballard
Date: Thu, 02 Apr 1998 00:00
Date: Thu, 02 Apr 1998 00:00
247 lines
6948 bytes
6948 bytes
i've set up (slackware) linux 2.0.33 on a 386 at home to act as a dial-up server to my isp. i've got pppd working fine, but am having problems with diald: it connects to the isp OK, then immediately runs a second "chat" script that resets the modem. if anyone could point me in the right direction to solve this i'd greatly appreciate it, thanks in advance, Mat here's the key system log entries: ____________________________________ Apr 1 22:06:04 stablefd diald[173]: Running connect (pid = 184). Apr 1 22:06:04 stablefd chat[184]: abort on (BUSY) Apr 1 22:06:04 stablefd chat[184]: abort on (NO CARRIER) Apr 1 22:06:04 stablefd chat[184]: send (AT&F^M) Apr 1 22:06:05 stablefd chat[184]: expect (OK) Apr 1 22:06:05 stablefd chat[184]: AT&F^M^M Apr 1 22:06:05 stablefd chat[184]: OK -- got it Apr 1 22:06:05 stablefd chat[184]: send (AT&D2&C1^M) Apr 1 22:06:05 stablefd chat[184]: expect (OK) Apr 1 22:06:05 stablefd chat[184]: ^M Apr 1 22:06:05 stablefd chat[184]: AT&D2&C1^M^M Apr 1 22:06:05 stablefd chat[184]: OK -- got it Apr 1 22:06:05 stablefd chat[184]: send (ATD(the isp phone number)^M) Apr 1 22:06:05 stablefd chat[184]: expect (rname:) Apr 1 22:06:05 stablefd chat[184]: ^M Apr 1 22:06:25 stablefd chat[184]: ATD(the isp phone number)^M^M Apr 1 22:06:25 stablefd chat[184]: CONNECT 26400/V42BIS^M Apr 1 22:06:25 stablefd chat[184]: ^M Apr 1 22:06:25 stablefd chat[184]: ^M Apr 1 22:06:25 stablefd chat[184]: User Access Verification^M Apr 1 22:06:25 stablefd chat[184]: ^M Apr 1 22:06:25 stablefd chat[184]: Username: -- got it Apr 1 22:06:25 stablefd chat[184]: send (matballard^M) Apr 1 22:06:25 stablefd chat[184]: expect (sword:) Apr 1 22:06:26 stablefd chat[184]: matballard^M Apr 1 22:06:26 stablefd chat[184]: Password: -- got it Apr 1 22:06:26 stablefd chat[184]: send (password^M) Apr 1 22:06:26 stablefd diald[173]: Running pppd (pid = 185). Apr 1 22:06:27 stablefd kernel: registered device ppp0 Apr 1 22:06:27 stablefd pppd[185]: pppd 2.2.0 started by root, uid 0 Apr 1 22:06:27 stablefd chat[190]: abort on (BUSY) Apr 1 22:06:27 stablefd chat[190]: abort on (NO CARRIER) Apr 1 22:06:27 stablefd chat[190]: send (AT&F^M) Apr 1 22:06:27 stablefd chat[190]: expect (OK) # this is what kills the modem: Apr 1 22:06:27 stablefd chat[190]: AT&F^M Apr 1 22:06:27 stablefd chat[190]: % Unknown command or computer name, or unable to find computer address^M Apr 1 22:07:26 stablefd diald[173]: pppd startup timed out. Check your pppd options. Killing pppd. Apr 1 22:07:27 stablefd pppd[185]: Terminating on signal 2. Apr 1 22:08:28 stablefd pppd[185]: Terminating on signal 2. Apr 1 22:09:33 stablefd diald[173]: Delaying 300 seconds before clear to dial. Apr 1 22:11:27 stablefd chat[190]: cs2511> Apr 1 22:11:27 stablefd chat[190]: alarm Apr 1 22:11:27 stablefd chat[190]: Failed Apr 1 22:11:27 stablefd pppd[185]: Exit. ____________________________________ here are the other key files: DIALD.CONF:____________________________________ # set the accounting log file: accounting-log /var/log/diald.accounting.log # tell us everything debug VERBOSE # ping the nameserver once link is up: # ip-up /etc/diald/pingit # we use ppp: mode ppp # DONT use the options file for pppd; use this one instead: pppd-options file /etc/ppp/options4diald # use the existing chat script for the pppd: connect "/usr/sbin/chat -v -t 300 -f /etc/ppp/net-chat" # use the modem: modem lock crtscts device /dev/ttyS1 speed 38400 # network setup: netmask 255.255.255.0 local 138.194.50.201 remote 138.194.50.200 dynamic proxyarp mtu 576 mru 576 window 2048 defaultroute # first the timeouts; mostly default: connect-timeout 60 disconnect-timeout 60 stop-dial-timeout 60 kill-timeout 60 start-pppd-timeout 60 stop-pppd-timeout 60 first-packet-timeout 60 # try again 300 seconds later after failed call: redial-timeout 300 # retry rules: retry-count 0 died-retry-count 1 # give only three attempts: dial-fail-limit 3 # third, keep the link up for 900 seconds at least, # then check for a further 1800 seconds (hangup if no activity) # ie: 15 minutes then 30 minutes. impulse 900,1500 # use the standard filter rules: include /usr/lib/diald/standard.filter ____________________________________ OPTIONS4DIALD: i've removed most comments, and commented out all the variables that DIALD uses (eg: crtscts): ____________________________________ # /etc/ppp/options4diald asyncmap 0 # add the "10 minute Guide" parameters: # /dev/ttyS1 # defaultroute # connect /etc/ppp/net-connect # 115200 # 38400 # auth # crtscts #xonxoff #escape 11,13,ff #local # lock # modem #mru 542 # notation (e.g. 255.255.255.0). # netmask 255.255.255.0 #noipdefault #passive #silent #-all #-ac #-am #-detach #-ip #-mn #-mru #-pc #+pap #-pap #+chap #-chap #-vj debug domain chem.csiro.au #kdebug n #mtu <n> #usehostname #remotename <n> # proxyarp # login lcp-echo-interval 20 lcp-echo-failure 20 #lcp-restart <n> #lcp-max-terminate <n> #lcp-max-configure <n> #lcp-max-failure <n> #ipcp-restart <n> #ipcp-max-terminate <n> #ipcp-max-configure <n> #ipcp-max-failure <n> #pap-restart <n> #pap-max-authreq <n> #chap-restart <n> #chap-max-challenge #chap-interval <n> ipcp-accept-local ipcp-accept-remote ____________________________________ NET_CHAT:____________________________________ ABORT 'BUSY' ABORT 'NO CARRIER' '' AT&F OK AT&D2&C1 OK ATD rname: matballard sword: password 2511> ppp ____________________________________ NET-CONNECT (should only be called by PPPD, not DIALD):____________________________________ #!/bin/sh /usr/sbin/chat -v -t 300 -f /etc/ppp/net-chat ____________________________________ To reply, just remove the .NoSpam at the end of my address ! ____________________________________ Dr Mat Ballard, CSIRO Molecular Science, Private Bag 10, Clayton South MDC, Clayton, Vic 3169. AUSTRALIA. tel: 61-3-9545-2425 fax: 61-3-9545-2415 m.ballard@molsci.csiro.au URL: http://www.wark.csiro.au/ballard/
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads