Hi Jean-Louis,
I put my DNS setting in /etc/resolv.conf
and also found the same file in /etc/ppp/resolv.conf , maybe put by
linuxconf (I am using RedHat 6.2, and used the netconf)
it says:
nameserver 203.117.33.19
nameserver 203.117.33.18
which are my ISP's primary and secondary DNS
for my /etc/diald.conf,
I use the usual
local 127.0.0.2
remote 127.0.0.3
I heard it doesn't matter.
I guess the most important setting that eludes me earlier when I first try
diald is the pap-secrets.
If your ISP use PAP (it won't send you those login: or password: text
prompt, but instead it sends you some garbage strings).
Make sure yo have "*" instead of "ppp0" in your pap-secret file
(get your ISP login and password ready)
# # Added by linuxconf
yourloginname * yourpassword
# Secrets for authentication using PAP
# client server secret IP addresses
then, also have this yourloginname in the ppp-option line in /etc/diald.conf
device /dev/modem
speed 115200
lock
mode ppp
dynamic
local 127.0.0.2
remote 127.0.0.3
pppd-options noauth name yourloginname
up-delay 5
defaultroute
modem
crtscts
connect /etc/diald/connect
redial-timeout 10
fifo /etc/diald/diald.ctl
finally, you need your /etc/diald/connect to simply dial and return:
#!/bin/sh
# Copyright (c) 1996, Eric Schenk.
#
# This script is intended to give an example of a connection script that
# uses the "message" facility of diald to communicate progress through
# the dialing process to a diald monitoring program such as dctrl or diald-top.
# It also reports progress to the system logs. This can be useful if you
# are seeing failed attempts to connect and you want to know when and why
# they are failing.
#
# This script requires the use of chat-1.9 or greater for full
# functionality. It should work with older versions of chat,
# but it will not be able to report the reason for a connection failure.
# Configuration parameters
# The initialization string for your modem
#MODEM_INIT="ATZ&C1&D2%C0"
MODEM_INIT="ATZ"
# The phone number to dial FILL THIS UP
PHONE_NUMBER="XXXXXXXXXX"
# The chat sequence to recognize that the remote system
# Pass a message on to diald and the system logs.
function message () {
[ $FIFO ] && echo "message $*" >$FIFO
logger -p local2.info -t connect "$*"
}
# Initialize the modem. Usually this just resets it.
message "Initializing Modem"
chat TIMEOUT 5 "" $MODEM_INIT TIMEOUT 45 OK ""
if [ $? != 0 ]; then
message "Failed to initialize modem"
exit 1
fi
# Dial the remote system.
>/var/log/diald.connect
message "Dialing $PHONE_NUMBER"
/usr/sbin/chat -r /var/log/diald.connect \
REPORT CONNECT \
TIMEOUT 45 \
ABORT "NO CARRIER" \
ABORT BUSY \
ABORT "NO DIALTONE" \
ABORT ERROR \
"" ATDT$PHONE_NUMBER \
CONNECT ""
case $? in
0) message "$(cat /var/log/diald.connect)";;
1) message "Chat Error"; exit 1;;
2) message "Chat Script Error"; exit 1;;
3) message "Chat Timeout"; exit 1;;
4) message "No Carrier"; exit 1;;
5) message "Busy"; exit 1;;
6) message "No DialTone"; exit 1;;
7) message "Modem Error"; exit 1;;
*)
esac
# Success!
message "Protocol started"
I was very frustrated last week when mine doesn't work at all.
So I hope this helps.
Rusman
At 01:53 PM 22/05/2000 -0400, Jean-Louis LeTortorec wrote:
>Hi:
>
>I've just installed diald on my computer and it works "a bit".
>It finds the modem, take the line and dial but can't get a connection.
>
>Actually, I don't know where to put the two DNS addresses I have for
>my provider. I suspect that the source of the problem.
>
>What I did is:
> local 192.168.0.0.1
> remote 123.456.789.123 (the DNS address from my ISP)
> dynamic
>
>I'm sure that the remote configuration is incorrect. Moreover, I
>have 2 DNS to enter.
>
>If someone could help, I'd appreciate.
>
>Thanks
>
>JL
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
