# (c) 1997, The Meme Factory, Inc.  http://www.meme.com
# Distributed under the GNU copyright.

# Global configuration for diald

# These values are good for a machine on a U.S. business or other,
# metered by time, phone line.  YMMV

# The diald-config README in /usr/doc may provide additional help.

# Check that the xxx_MAIL_TIMEOUTs are set properly! (Or just don't set it.)

# The rest are optional.

#
# Compatibilty.
#

# The configuration program used to generate some of these config files.
# Unless configured otherwise, make diald work like the ppp system
# we're replacing.
#
# Legal values are:
# REDHAT  For the RedHat ppp network configuration utility.
# the empty string (or undefined)  For no particular GUI config utility.
CONFPROG="REDHAT"

# Version of the configuration program.
# With Redhat this is the redhat distribution release number.
CONFPROGVER="4.2"

#
# Diald monitoring
#
# Note that dctrl (use start-dctrl) must be started independently of
# diald with links in /etc/rc.d/rc*.d/, if you always want it up.
# dctrl should be started after diald, and stopped before diald.
# (Seems that way with diald v 0.16 anyhow.)  
#

# Animate the dctrl icon (when the window is iconified.)
ANIMATE_DCTRL=

# Start dctrl as an icon.
ICONIFY_DCTRL=

# Start dctrl with dialing log displayed.
DLOG_DCTRL=yes

# Start dctrl with packet queue displayed.
PQUEUE_DCTRL=

# Start dctrl with alarm timeouts and numeric load detail displayed.
TLOAD_DCTRL=

# Start dctrl with graphical load monitor displayed.
GLOAD_DCTRL=

# Send log messages regarding the connect script to the FIFO.
# (Usually dctrl, which displays them in it's dialing log.)
MON_CONNECT=yes

# Log exchange used to connect.
# Note that if this is on, the password will be logged unless it is
# prefixed in the chat script with "\q", which is _not_ done automatically
# by the Redhat (4.0) network control panel.
VERBOSE_LOGGING="yes"

#
# link control settings
#

# Kill ppp link if no lcp response from the other end (ppp startup fails.)
# How many checks can fail before we give up?
LCP_ECHO_FAILURE=3
# How often should we check?
LCP_ECHO_INTERVAL=7

# Force diald retry on failed ppp establishment.  (When lcp is not used to
# detect dead link bring the line down.)
# Should be set longer on slow networks.
#STARTUP_TIMEOUT=15

#
# Network settings.
#

# The local ppp daemon will not supply any ip numbers for the link.
# NOIPDEFAULT=yes

# See LINK_DOWN_IPADDR and LINK_DOWN_REMIP above for more network settings.

#
# Authentication
#

# Username to use when checking to see that remote end is who they say
# they are.  (See pppd remotename option.)  When Redhat compatible, empty
# picks up the value Redhat uses.
# REMOTENAME=

#
# Dialing section.
#

# How many times should I try to dial the phone?
DIAL_FAIL_LIMIT=6

# How long should I wait between dialing tries?
REDIAL_TIMEOUT=10

# Delay between dialing attempts when no free modem is available, in 
# seconds.
# NODEV_RETRY_TIMEOUT=1

# Maximum dial attempts on initial connection.
# RETRY_COUNT=0

# Connection failures allowed before doubling delay between dial attempts.
# REDIAL_BACKOFF_START=

# Maximum delay between failed calls, in seconds.
# REDIAL_BACKOFF_LIMIT=600

#
# Other stuff.
#

# Throw away packets older that this that are sitting waiting to be sent.
BUFFER_TIMEOUT=600

#
# Traffic control timeouts
#

# Keep "typical network maintenance traffic" from controlling the link.
STANDARD_IGNORES="yes"

# Default for http, nntp, and ftp traffic
WEB_BROWSING_TIMEOUT=120  ;# 2 minutes 

# ftp traffic, if not defined, WEB_BROWSING_TIMEOUT will be used
# FTP_TIMEOUT=120         ;# 2 minutes 

# http (web) traffic, if not defined, WEB_BROWSING_TIMEOUT will be used
# HTTP_TIMEOUT=120        ;# 2 minutes

# nntp (news) traffic, if not defined, WEB_BROWSING_TIMEOUT will be used
# NNTP_TIMEOUT=120        ;# 2 minutes

# Mail timeouts should correspond to the timeouts in the applications
# that get/send mail, plus a little slack as experience dictates.
#
# imap and pop-2 and pop-3 traffic
# FETCH_MAIL_TIMEOUT=240          ;#  4 minutes 
#
# smtp traffic
# SEND_MAIL_TIMEOUT=240          ;#  4 minutes 

# domain name services.
# As this is what usually brings the link up, it must be longer than the
# time taken to start the link and get the first dns reply!  (At least with
# those resolvers/configurations where no more packets will be sent until the
# dns reply comes back.)  I believe that the standard resolver timeout is
# 30 seconds, so, in absence of other traffic, 
# when nameservices requests the net, just when diald
# is about to give up and hang up the phone, the resolver sends out another
# packet if it wants to try again.  What a co-inky-dink!
DOMAIN_TIMEOUT=30  ;# in seconds, standard value from diald distribution

# Ugly microsoft netbios name services.
NETBIOS_NS_TIMEOUT=

# Drop the connection quickly when tcp sessions finish.
# Overrides timeouts for all tcp connections but http.
QUICK_DROP=yes


# Do not bring link up or keep link up for dns requests.  
# The only time I can imagine you want this option is a) to emulate
# the configuration distributed with diald, or b) when you are
# supplying a dialup site with internet access and that site is acting
# as a primary nameserver for which you are a secondary.
# IGNORE_NAMESERVER=yes

# Generic defaults
OTHER_TCP_TIMEOUT=600     ;# 10 minutes 
OTHER_UDP_TIMEOUT=120     ;#  2 minutes 

# How long should the link remain idle before we hang up the phone?
# Catches any packets for which there are no other timeouts defined.
DEFAULT_TIMEOUT=30	;# In seconds.
