OS: Red Hat 7.2 Kernel 2.4.7-10
Diald version: 0.99.1-1
Symptoms: Modem dials; got authenticated and received both remote and local
IP addresses from the ISP (SINGNET). I can successfully ping the remote IP
address BUT I wasn't able to ping www.singnet.com.sg or the primary and
secondary DNS servers of the ISP I subscribe to. I cannot surf the internet
using Netscape navigator as it cannot resolve the proxy address entered in
Netscape.
I must stress the fact that I am able to surf by running my own ppp scripts
(ppp-on and ppp-on-dialer). You can safely assume that my /etc/resolv.conf
is
set up properly; if not, I wouldn't have been able to surf.
Please help by telling me what is wrong with my configuration here. I'm at a
loss.
Here are my diald.conf and diald-dialer files:
diald.conf
mode ppp
connect /etc/ppp/diald-dialer
device /dev/ttyS0
speed 115200
modem
lock
crtscts
pppd-options name cheokkin
local 192.168.0.100
remote 192.168.0.200
dynamic
defaultroute
include /usr/lib/diald/standard.filter
diald-dialer
#!/bin/sh
#
# This is part 2 of the ppp-on script. It will perform the connection
# protocol for the desired connection.
#
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 40 \
'OK' ATDT17131 \
CONNECT
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-06-25
I'd guess you forced remote address is the issue. Your ISP may not be allowing you to set the address for local and remote. Your diald.conf file has forced settings; the log output has different remote and local IPs.
Apr 16 11:30:45 network pppd[1683]: local IP address
165.21.55.81
Apr 16 11:30:45 network pppd[1683]: remote IP address 165.21.55.6
Don't force local and remote in diald.conf.
Steven Howe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OS: Red Hat 7.2 Kernel 2.4.7-10
Diald version: 0.99.1-1
Symptoms: Modem dials; got authenticated and received both remote and local
IP addresses from the ISP (SINGNET). I can successfully ping the remote IP
address BUT I wasn't able to ping www.singnet.com.sg or the primary and
secondary DNS servers of the ISP I subscribe to. I cannot surf the internet
using Netscape navigator as it cannot resolve the proxy address entered in
Netscape.
I must stress the fact that I am able to surf by running my own ppp scripts
(ppp-on and ppp-on-dialer). You can safely assume that my /etc/resolv.conf
is
set up properly; if not, I wouldn't have been able to surf.
Please help by telling me what is wrong with my configuration here. I'm at a
loss.
Here are my diald.conf and diald-dialer files:
diald.conf
mode ppp
connect /etc/ppp/diald-dialer
device /dev/ttyS0
speed 115200
modem
lock
crtscts
pppd-options name cheokkin
local 192.168.0.100
remote 192.168.0.200
dynamic
defaultroute
include /usr/lib/diald/standard.filter
diald-dialer
#!/bin/sh
#
# This is part 2 of the ppp-on script. It will perform the connection
# protocol for the desired connection.
#
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 40 \ 'OK' ATDT17131 \ CONNECT
Here's the output of tail -f /var/log/messages
Apr 16 11:30:03 network diald[1631]: accept parsing error. Got token
'tcp.www'. Not a known tcp service port.
Apr 16 11:30:03 network diald[1631]: parse string: 'tcp 120
tcp.dest=tcp.www'
Apr 16 11:30:03 network diald[1631]: accept parsing error. Got token
'tcp.www'. Not a known tcp service port.
Apr 16 11:30:03 network diald[1631]: parse string: 'tcp 120
tcp.source=tcp.www'
Apr 16 11:30:03 network diald[1631]: ignore parsing error. Got token
'udp.route'. Not a known udp service port.
Apr 16 11:30:03 network diald[1631]: parse string: 'udp udp.dest=udp.route'
Apr 16 11:30:03 network diald[1631]: ignore parsing error. Got token
'udp.route'. Not a known udp service port.
Apr 16 11:30:03 network diald[1631]: parse string: 'udp
udp.source=udp.route'
Apr 16 11:30:03 network diald[1631]: ignore parsing error. Got token
'udp.route'. Not a known udp service port.
Apr 16 11:30:03 network diald[1631]: parse string: 'udp tcp.dest=udp.route'
Apr 16 11:30:03 network diald[1631]: ignore parsing error. Got token
'udp.route'. Not a known udp service port.
Apr 16 11:30:03 network diald[1631]: parse string: 'udp
tcp.source=udp.route'
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap0
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap1
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap2
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap3
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap4
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap5
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap6
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap7
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap8
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap9
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap10
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap11
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap12
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap13
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap14
Apr 16 11:30:03 network modprobe: modprobe: Can't locate module tap15
Apr 16 11:30:03 network kernel: CSLIP: code copyright 1989 Regents of the
University of California
Apr 16 11:30:03 network kernel: SLIP: version 0.8.4-NET3.019-NEWTTY-MODULAR
(dynamic channels, max=256) (6 bit encapsulation enabled).
Apr 16 11:30:03 network kernel: SLIP linefill/keepalive option.
Apr 16 11:30:03 network diald[1632]: start sl0: SIOCSIFMETRIC: Operation not
supported
Apr 16 11:30:03 network diald[1632]: start sl0: RTNETLINK answers: File
exists
Apr 16 11:30:14 network diald[1632]: Trigger: udp 192.168.0.100/32769
165.21.83.88/53
Apr 16 11:30:14 network diald[1632]: Calling site 192.168.0.200
Apr 16 11:30:15 network chat[1682]: timeout set to 3 seconds
Apr 16 11:30:15 network chat[1682]: abort on (\nBUSY\r)
Apr 16 11:30:15 network chat[1682]: abort on (\nNO ANSWER\r)
Apr 16 11:30:15 network chat[1682]: abort on (\nRINGING\r\n\r\nRINGING\r)
Apr 16 11:30:15 network chat[1682]: send (AT^M)
Apr 16 11:30:15 network chat[1682]: expect (OK)
Apr 16 11:30:15 network chat[1682]: ^M
Apr 16 11:30:15 network chat[1682]: OK
Apr 16 11:30:15 network chat[1682]: -- got it
Apr 16 11:30:15 network chat[1682]: send (ATZ^M)
Apr 16 11:30:15 network chat[1682]: timeout set to 40 seconds
Apr 16 11:30:15 network chat[1682]: expect (OK)
Apr 16 11:30:15 network chat[1682]: ^M
Apr 16 11:30:16 network chat[1682]: ^M
Apr 16 11:30:16 network chat[1682]: OK
Apr 16 11:30:16 network chat[1682]: -- got it
Apr 16 11:30:16 network chat[1682]: send (ATDT17131^M)
Apr 16 11:30:16 network chat[1682]: expect (CONNECT)
Apr 16 11:30:16 network chat[1682]: ^M
Apr 16 11:30:41 network chat[1682]: ATDT17131^M^M
Apr 16 11:30:41 network chat[1682]: CONNECT
Apr 16 11:30:41 network chat[1682]: -- got it
Apr 16 11:30:41 network diald[1632]: Connected to site 192.168.0.200
Apr 16 11:30:41 network diald[1632]: Running pppd (pid = 1683).
Apr 16 11:30:41 network pppd[1683]: pppd 2.4.1 started by root, uid 0
Apr 16 11:30:41 network kernel: PPP generic driver version 2.4.1
Apr 16 11:30:41 network pppd[1683]: Using interface ppp0
Apr 16 11:30:41 network pppd[1683]: Connect: ppp0 <--> /dev/ttyS0
Apr 16 11:30:41 network pppd[1683]: Warning - secret file
/etc/ppp/pap-secrets has world and/or group access
Apr 16 11:30:44 network pppd[1683]: Warning - secret file
/etc/ppp/pap-secrets has world and/or group access
Apr 16 11:30:45 network kernel: PPP BSD Compression module registered
Apr 16 11:30:45 network kernel: PPP Deflate Compression module registered
Apr 16 11:30:45 network pppd[1683]: local IP address 165.21.55.81
Apr 16 11:30:45 network pppd[1683]: remote IP address 165.21.55.6
Apr 16 11:30:45 network diald[1632]: New addresses: local 165.21.55.81,
remote 165.21.55.6, broadcast 0.0.0.0
Apr 16 11:30:45 network diald[1632]: start ppp0: SIOCSIFMETRIC: Operation
not supported
Apr 16 11:30:45 network diald[1632]: start ppp0: RTNETLINK answers: File
exists
Apr 16 11:30:45 network diald[1632]: start ppp0: RTNETLINK answers: File
exists
Apr 16 11:31:59 network diald[1632]: Closing down idle link.
Apr 16 11:31:59 network diald[1632]: start sl0: SIOCSIFMETRIC: Operation not
supported
Apr 16 11:31:59 network diald[1632]: start sl0: RTNETLINK answers: File
exists
Apr 16 11:31:59 network diald[1632]: stop ppp0: RTNETLINK answers: No such
process
Apr 16 11:31:59 network pppd[1683]: Terminating on signal 2.
Apr 16 11:31:59 network pppd[1683]: Connection terminated.
Apr 16 11:31:59 network pppd[1683]: Connect time 1.3 minutes.
Apr 16 11:31:59 network pppd[1683]: Sent 497 bytes, received 491 bytes.
Apr 16 11:31:59 network pppd[1683]: Exit.
Apr 16 11:31:59 network diald[1632]: start sl0: SIOCSIFMETRIC: Operation not
supported
Apr 16 11:31:59 network diald[1632]: start sl0: RTNETLINK answers: File
exists
Apr 16 11:31:59 network diald[1632]: start sl0: RTNETLINK answers: File
exists
Apr 16 11:32:00 network diald[1632]: Delaying 30 seconds before clear to
dial.
Apr 16 11:33:28 network syslogd 1.4.1: restart.
Apr 16 11:35:45 network su(pam_unix)[2079]: session opened for user news by
(uid=0)
Apr 16 11:35:45 network su(pam_unix)[2079]: session closed for user news
I'd guess you forced remote address is the issue. Your ISP may not be allowing you to set the address for local and remote. Your diald.conf file has forced settings; the log output has different remote and local IPs.
Apr 16 11:30:45 network pppd[1683]: local IP address
165.21.55.81
Apr 16 11:30:45 network pppd[1683]: remote IP address 165.21.55.6
Don't force local and remote in diald.conf.
Steven Howe
i think ip remote and local are to set for the diald interface... in diald.conf he added the dynamic option as well....
if he is able to connect and ping probably it's a dns isue.. check your /etc/resolv.conf to have a valid nameserver address in it