Oops. Forgot to say that I have a PAP secrets file:
Add following line in /etc/ppp/pap-secrets, verify file has 600 root only
read/write permission:
nameXXX * "password"
- - -CL
: This are my notes on setting up diald (rpm -i diald-0.16-1.i386.rpm) for
my
: Caldera OpenLinux1.3. Note that:
: the /etc/ppp/c-s chat-script file contains entries such as (no comment
: lines appear allowed):
: ABORT BUSY
: ABORT "NO DIAL TONE"
: "" ATZ
: OK ATDTnnnnnnnn
: CONNECT ""
:
: you may only get a dynamic IP address for your dialup ppp connection,
not
: a static IP address as in the example below, in which case you will need
: dummy IP addresses for "local" and "remote" and you must uncomment the
: "dynamic" parameter as well as the command "echo 7
: /proc/sys/net/ipv4/ip_dynaddr". Read the diald man pages and the text in
: /usr/src/linux/Documentation/networking/ip_dynaddr.txt.
:
: Hope this is useful. - - -CL
:
: 1. Copied /usr/lib/diald/diald.conf.sample file to /etc/diald.conf, and
: configured the diald.conf file:
: modem
: connect /bin/true
: #disconnect /bin/true # use hardware to disconnect
: pppd-options connect "/usr/sbin/chat -f /etc/ppp/c-s" name XXX asyncmap
0
: device /dev/ttyS1 # ttyS1 so that lock file is same as used by
:mgetty
for
: dial-in
: speed 115200
: local n.n.n.n # static IP address from ISP
: remote m.m.m.m # default router at ISP
: netmask 255.255.255.0
:
: #dynamic # static IP address
: mode ppp
: crtscts
: defaultroute
: reroute
: #proxyarp
: lock # lock file is /var/lock/LCK..ttyS1
:
: debug 31 # to see the filtered datagrams in
:/var/log/messages
:
: #(following paths are OpenLinux specific)
: fifo /etc/diald/diald.ctl
: accounting-log /var/log/diald
: path-route /sbin/route
: path-ifconfig /sbin/ifconfig
: path-pppd /usr/sbin/pppd
: path-bootpc /sbin/bootpc
: ip-up /etc/ppp/ip-up
: ip-down /etc/ppp/ip-down
: include /usr/lib/diald/standard.filter
: 2. Edited /usr/lib/diald/standard.filter file used to specify type of
: datagrams to be filtered to trigger the specified action:
: increase http hold up time after a transfer ends from 2 min to 5 min
: accept tcp 300 tcp.dest=tcp.www
: accept tcp 300 tcp.source=tcp.www
: uncomment rules for ftp-data, since it is defined in /etc/services
: accept tcp 120 tcp.dest=tcp.ftp-data
: accept tcp 120 tcp.source=tcp.ftp-data
: decreased hold up time for any other tcp datagram from 10 min to 2 min
: accept tcp 120 any
: 3. (Note: If diald were running, need to kill then re-run it to use new
: diald.conf or standard.filter files.)
: 4. Edited /etc/rc.d/rc.local file to:
: run diald daemon at boot up:
: /usr/sbin/diald
: echo "Starting diald daemon"
: if local ip address were not static, to have kernel use the dynamic IP
: address assigned to pppd instead of the initial dummy SLIP interface IP
: address defined as 'local' in /etc/diald.conf file:
: #echo 7 >/proc/sys/net/ipv4/ip_dynaddr
:
:
: ----------
: : From: [EMAIL PROTECTED]
: : To: [EMAIL PROTECTED]
: : Cc: [EMAIL PROTECTED]
: : Subject: PAP support in diald
: : Date: Sunday, May 30, 1999 5:36 PM
: :
: : I'm trying to setup diald and have run into a major question. Does
diald
: : support PAP or CHAP authentication? All examples I have seen refer to
: : script based logins, in which diald is searching for --name: and word:
: fields
: : (or derivations thereof). Since PAP is used on Cornell's dialup pool, I
: can
: : login using pppd from the command line (and included files like
: : /etc/ppp/pap-secrets) but this does not seem to cut it for the diald
: : configurations. Any advice, tips or tricks would be appreciated!
: :
: : Peter Krebs
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
