Jim Adams wrote:

>     I have recently installed the latest version of diald and am a mite
> perplexed. Having tried and failed using earlier versions it was
> reccomended that I try the latest release.
>     With the earlier version I used an RPM for installation and it
> apparently put everything in its plaxce. With the new release I had no
> problem compiling and installing, but where the heck is the
> /etc/diald.conf file? Is thuis something that is not necessary in the
> latest version? Or do I need to start from scratch and create my own
> conf file. If this is the case would someone please be kind enough to
> let me know.
>     Up until now everyone responding has gone above and beyond anything
> I would expect from  a mailing list. So here is a big THANKS to all of
> those that have assisted in the past.
>
> Cheers
> Jim Adams
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]

Jim,

I started from scratch (referencing the documentation often).  I am planning
on running diald for two different ISP and therefore put diald.conf in
/etc/diald/diald.conf and started diald in rc.local as follows:

/usr/sbin/diald -f /etc/diald/diald.conf.

Both of my ISPs use PAP and I have set up the pap-secrets files
appropriately, here is my diald.conf file for my main ISP:

#
# diald.conf for anathoth
#
# Select the demand dial rules you want
# Bring the link up for anything, timeout in seconds. Use this for
# when the dompute has its own phone line
accept any 420 any
# Use the filter file that comes with diald.  This can be a bit drastic,
# so use the filter below
# include /usr/lib/diald/standard.filter
# or use the filter that brings the link up for use on a line shared with
# a phone
# include /etc/diald/phone.filter

# stuff to set up the diald connection
device /dev/ttyS1
speed 115200
lock
mode ppp
# We may get another terminal server, thus use
# 'dynamic' and do not tell PPP the IP number of the other end
# For use with gated, comment out the 'dynamic' option, and
# set remote to be the same as local
dynamic
local 10.0.0.1
remote 10.0.0.2
# your userID and remote name in the next line
pppd-options asyncmap 0 user userid remotename rem-name ipcp-accept-remote
# impulse may conflict with the time out at the beginning of the file
# impulse 300,0,0
defaultroute
modem
crtscts
connect "/usr/sbin/chat -f /etc/ppp/pppchat"
redial-timeout 10
fifo /etc/diald/diald.ctl
# restrict 9:00:00 17:45:00 1 * *
# or-restrict 9:00:00 17:45:00 2 * *
# or-restrict 9:00:00 17:45:00 3 * *
# or-restrict 9:00:00 17:45:00 4 * *
# or-restrict 9:00:00 17:45:00 5 * *
# up

I used the following options for chat (/etc/ppp/pppchat):

ABORT "NO DIALTONE"
ABORT BUSY
ABORT "NO CARRIER"
REPORT "CONNECT"
"" ATZ
OK AT&F&C1E0s11=55L0M0S95=1X4W2&Q5&D3
OK ATDT6381198
CONNECT ""

I hope this helps.

Bob Chiodini



-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to