Need Help with 'diald' - dial on demand

Need Help with 'diald' - dial on demand

Post by Clifford Kit » Wed, 16 May 2001 02:00:27




> I installed diald 0.91.1RPM package accompanied with a book
> on networking..I have modified the diald.conf and diald-dialer
> (attached for your ref) to suit (I believer !) my enviroment..When
> I run /usr/sbin/diald and ping somedomain.com or ip.ad.re.ss, my
> modem makes noise and connecting, but it then time out ...I have
> increased time out in diald-dialer, but still no

Increasing the timeout for chat is rarely successful.

Quote:> luck. I also attached below the log file for your info..

[...]

Quote:> ===============/ect/ppp/diald-dialer=============
> #!/bin/sh
> exec /usr/sbin/chat -v                                            \
>         TIMEOUT         3                                           \
>         ABORT           '\nBUSY\r'                               \
>         ABORT           '\nNO ANSWER\r'                    \
>         ABORT           '\nRINGING\r\n\r\nRINGING\r'    \
>         ' '                      'AT'
> \
>         'OK'                'ATZ'                                         \
>         TIMEOUT         120                                          \
>         'OK'                ATDT770393                              \
>         CONNECT

I'd suggest using  CONNECT '\c'  as the last chat expect-send instead
of just CONNECT.  If you are lucky then that change alone will be enough.

Quote:> ===================/var/log/nessages =======================

[...]

Quote:> May 13 17:47:12 myserver diald[907]: Running pppd (pid = 931).
> May 13 17:47:12 myserver kernel: PPP: version 2.3.7 (demand dialling)
> May 13 17:47:12 myserver kernel: PPP line discipline registered.
> May 13 17:47:12 myserver kernel: registered device ppp0
> May 13 17:48:12 myserver diald[907]: pppd startup timed out. Check your pppd
> options. Killing pppd.

Since I haven't used it I can't comment much on diald, but this says
that there is likely something wrong with the pppd configuration
options, at least in diald's opinion.

Do as it says, check the pppd options.  Although the diald options you
posted clearly contained some pppd options and I saw nothing unusual,
the diald configuration options may not be correctly specified.  You can
also add debug to the pppd options and post exact copies of the PPP
negotiation log messages, including timestamps, which should be in one
of the log files in the /var/log directory.  Just which file varies
according to how /etc/syslog.conf is configured.

The Lucent "modem" driver might also be a factor since as the kernel
version changes these must usually change too.

--

/* Better is the enemy of good enough. */

 
 
 

Need Help with 'diald' - dial on demand

Post by Bill Meek » Wed, 16 May 2001 07:03:43


Be sure your OPTIONS file in "/etc/ppp" contains the line "noauth" without
the quote marks.

I also found I could dispense with entirely with the CHAT script if I just
set the parameters in the "chap-secrets" or "pap-secrets" file, as
appropriate.

Bill

 
 
 

Need Help with 'diald' - dial on demand

Post by Dean Thompso » Wed, 16 May 2001 07:06:30


Hi Suwat,

Quote:> I installed diald 0.91.1RPM package accompanied with a book on
> networking..I have modified the diald.conf and diald-dialer (attached for
> your ref) to suit (I believer !) my enviroment..When I run /usr/sbin/diald
> and ping somedomain.com or ip.ad.re.ss, my modem makes noise and
> connecting, but it then time out ...I have increased time out in
> diald-dialer, but still no luck. I also attached below the log file for
> your info..

> I am a newbie..don't know much about what those log messages mean and how
> to fix the problem.

Sounds like you are almost there, but do you know whether or not you pass your
modem a "chat sequence" which is responsible for negotiating the client
connection with your ISP.  Additionally, based on your logs it looks like
there might be a problem with your "slip" interface.  I am not sure whether
you are trying to form a slip connection or a PPP connection.  You might like
to increase the "verbose" level of PPP so that it can give you some more
information but it almost looks like PPP is trying to establish a PPP session
with the SLIP interface.

You might like to take a look at your PPP options file to ensure that
everything does look right for a dialout to the remote site.  If you get stuck
take a look at the PPP-HOWTO located at http://www.linuxdoc.org and check to
make sure that you can form a PPP connection with your ISP without diald and
then introduce that once you know PPP works.

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

1. linux 2.018/kerneld/PPP dial on demand: 'network unreachable' then starts dialling

I recently upgradet to the 2.0.18 kernel from 1.2.13, and decided to
switch from using diald to the kerneld-based dial-on-demand solution
documented in the kerneld READMEs.

Most of the time, my connections come up OK (except for some
irrelevant rumbles that I suspect are due to a misconfiguration
on my ISP's side), but when I try starting ncftp from the command
line, I get this:

--------[snip]---------

NcFTP: nic.funet.fi (101): Network is unreachable

NcFTP 1.9.4 (April 15, 1995) by Mike Gleason, NCEMRSoft.

Tip: If you don't want a .ncrecent file in your home directory, put
the
     command '#unset recent-list' in your .ncftprc file.

ncftp>
--------[snip]---------

then, after some seconds, my modem starts dialling and a PPP
connection gets established. To me, it looks like ncftp times
out immediately, but kerneld processes the package anyway.

Is it possible to devise a workaround for this?

- Peter

2. rp-pppoe2.6 on-demand function problem

3. Is there a port for diald (or does OpenBSD's pppd support dial on demand)?

4. Help! Can SCO ODT run on AMD CPU?

5. Pls help: 'efax' and 'diald' don't quite get along

6. Linux Sys. Admin's Survival Guide

7. ISDN Dial-On-Demand: Can't Stop dial with arp packets...

8. Telnet and screen capture

9. PPP problems - "Dial on Demand" won't dial

10. How do I get 'dial-out' on demand?

11. How to 'dumb-up' on-demand dialing?

12. DialD Dial on Demand HELP w/RH 5.2

13. demand dialing vs. the other demand dialing