Hi, I have recently installed diald-0.16.5-201.i386.rpm binaries package, and have a lot of trouble getting it to work. Attached are copies of my various configuration files that I have along with excerpts of messages that diald logs in my /var/log/messages file. Can anyone tell me what I'm doing wrong, or at least pointers on how to go about diagnosing and troubleshooting the problem? I have gone through the latest HowTO by Andres Seco Hernandez posted a few days ago and still can't get it to work. I have tried the following procedures to test my setup: 1) Bring diald connection up using /usr/sbin/chat -f /etc/chatscripts/provider as he suggests, the script times out on ATZ line in 'provider' chat script. 2) ping a valid internet address say 100.100.100.1 or fire up Netscape with a common URL like netscape's home and I get the message attached from /var/log/messages. One final question: I have a working ppp connect and disconnect scripts that works manually: /etc/sysconfig/network-scripts/ifup (and ifdown). Can I get diald to use these as its connection and disconnection scripts in its configuration file? Many thanks in advance for any helpful suggestions. Regards, Nader
ABORT BUSY ABORT "NO CARRIER" ABORT VOICE ABORT "NO DIALTONE" ABORT "NO ANSWER" "" ATZ OK ATDT0345002299 CONNECT \d\c
#!/bin/sh iface=$1 netmask=$2 localip=$3 remoteip=$4 metric=$5 echo `date` $1 $2 $3 $4 $5 | mail -s "diald - conecting" root@localhost
Apr 13 23:26:06 Caspian diald[2268]: accept parsing error. Got token 'tcp.443'. Not a known tcp service port. Apr 13 23:26:06 Caspian diald: diald[2268]: accept parsing error. Got token 'tcp.443'. Not a known tcp service port. Apr 13 23:26:06 Caspian diald[2268]: parse string: 'tcp 120 tcp.dest=tcp.443' Apr 13 23:26:06 Caspian diald[2268]: accept parsing error. Got token 'tcp.443'. Not a known tcp service port. Apr 13 23:26:06 Caspian diald[2268]: parse string: 'tcp 120 tcp.source=tcp.443' Apr 13 23:26:06 Caspian diald: diald[2268]: parse string: 'tcp 120 tcp.dest=tcp.443' Apr 13 23:26:06 Caspian diald: diald[2268]: accept parsing error. Got token 'tcp.443'. Not a known tcp service port. Apr 13 23:26:06 Caspian diald: diald[2268]: parse string: 'tcp 120 tcp.source=tcp.443' Apr 13 23:26:06 Caspian diald: diald startup succeeded Apr 13 23:26:20 Caspian diald[2269]: Running connect (pid = 2275). Apr 13 23:26:20 Caspian diald[2269]: Running pppd (pid = 2281). Apr 13 23:26:20 Caspian modprobe: can't locate module char-major-108 Apr 13 23:26:20 Caspian pppd[2281]: pppd 2.3.10 started by root, uid 0 Apr 13 23:28:20 Caspian diald[2269]: pppd startup timed out. Check your pppd options. Killing pppd. Apr 13 23:28:20 Caspian diald[2269]: Nonzero exit status (7) on command '/sbin/route add 127.0.0.4 metric 1 dev sl0' Apr 13 23:28:20 Caspian diald[2269]: Nonzero exit status (7) on command '/sbin/route add default metric 1 netmask 0.0.0.0 dev sl0' Apr 13 23:28:20 Caspian pppd[2281]: Terminating on signal 2. Apr 13 23:28:20 Caspian pppd[2281]: Exit. Apr 13 23:28:21 Caspian diald[2269]: Nonzero exit status (7) on command '/sbin/route add 127.0.0.4 metric 1 dev sl0' Apr 13 23:28:21 Caspian diald[2269]: Nonzero exit status (7) on command '/sbin/route add default metric 1 netmask 0.0.0.0 dev sl0' Apr 13 23:28:22 Caspian diald[2269]: Delaying 60 seconds before clear to dial.
# /etc/diald/personal.filter # Filter rules shown are the same as in the standard.filter with the # following changes: # # Change 10 to 4 minuttes in "any other tcp conection". # Added "ignore tcp tcp.fin" to ignore the FIN ACK packets. # Ignore icmp packets (ping and traceroute don't fire up the interface). # # This is a pretty complicated set of filter rules. # (These are the rules I use myself.) # # I've divided the rules up into four sections. # TCP packets, UDP packets, ICMP packets and a general catch all rule # at the end. ignore icmp any #------------------------------------------------------------------------------ # Rules for TCP packets. #------------------------------------------------------------------------------ # General comments on the rule set: # # In general we would like to treat only data on a TCP link as significant # for timeouts. Therefore, we try to ignore packets with no data. # Since the shortest possible set of headers in a TCP/IP packet is 40 bytes, # any packet with length 40 must have no data riding in it. # We may miss some empty packets this way (optional routing information # and other extras may be present in the IP header), but we should get # most of them. Note that we don't want to filter out packets with # tcp.live clear, since we use them later to speedup disconnects # on some TCP links. # # We also want to make sure WWW packets live even if the TCP socket # is shut down. We do this because WWW doesn't keep connections open # once the data has been transfered, and it would be annoying to have the link # keep bouncing up and down every time you get a document. # # Outside of WWW the most common use of TCP is for long lived connections, # that once they are gone mean we no longer need the network connection. # We don't neccessarily want to wait 10 minutes for the connection # to go down when we don't have any telnet's or rlogin's running, # so we want to speed up the timeout on TCP connections that have # shutdown. We do this by catching packets that do not have the live flag set. # --- start of rule set proper --- # When initiating a connection we only give the link 15 seconds initially. # The idea here is to deal with possibility that the network on the opposite # end of the connection is unreachable. In this case you don't really # want to give the link 10 minutes up time. With the rule below # we only give the link 15 seconds initially. If the network is reachable # then we will normally get a response that actually contains some # data within 15 seconds. If this causes problems because you have a slow # response time at some site you want to regularly access, you can either # increase the timeout or remove this rule. accept tcp 15 tcp.syn # Keep named xfers from holding the link up ignore tcp tcp.dest=tcp.domain ignore tcp tcp.source=tcp.domain # (Ack! SCO telnet starts by sending empty SYNs and only opens the # connection if it gets a response. Sheesh..) accept tcp 5 ip.tot_len=40,tcp.syn # keep empty packets from holding the link up (other than empty SYN packets) ignore tcp ip.tot_len=40,tcp.live # Modification by Andres Seco to ignore the FIN ACK packets. ignore tcp tcp.fin # make sure http transfers hold the link for 2 minutes, even after they end. # NOTE: Your /etc/services may not define the tcp service www, in which # case you should comment out the following two lines or get a more # up to date /etc/services file. See the FAQ for information on obtaining # a new /etc/services file. accept tcp 120 tcp.dest=tcp.www accept tcp 120 tcp.source=tcp.www # Same for https accept tcp 120 tcp.dest=tcp.443 accept tcp 120 tcp.source=tcp.443 # Once the link is no longer live, we try to shut down the connection # quickly. Note that if the link is already down, a state change # will not bring it back up. keepup tcp 5 !tcp.live ignore tcp !tcp.live # an ftp-data or ftp connection can be expected to show reasonably frequent # traffic. accept tcp 120 tcp.dest=tcp.ftp accept tcp 120 tcp.source=tcp.ftp #NOTE: ftp-data is not defined in the /etc/services file provided with # the latest versions of NETKIT, so I've got this commented out here. # If you want to define it add the following line to your /etc/services: # ftp-data 20/tcp # and uncomment the following two rules. #accept tcp 120 tcp.dest=tcp.ftp-data #accept tcp 120 tcp.source=tcp.ftp-data # If we don't catch it above, give the link 10 minutes up time. #accept tcp 600 any # Modificacion de Andres Seco. Solo dejar 4 minutos mas. accept tcp 240 any # Rules for UDP packets # # We time out domain requests right away, we just want them to bring # the link up, not keep it around for very long. # This is because the network will usually come up on a call # from the resolver library (unless you have all your commonly # used addresses in /etc/hosts, in which case you will discover # other problems.) # Note that you should not make the timeout shorter than the time you # might expect your DNS server to take to respond. Otherwise # when the initial link gets established there might be a delay # greater than this between the initial series of packets before # any packets that keep the link up longer pass over the link. # Don't bring the link up for rwho. ignore udp udp.dest=udp.who ignore udp udp.source=udp.who # Don't bring the link up for RIP. ignore udp udp.dest=udp.route ignore udp udp.source=udp.route # Don't bring the link up for NTP or timed. ignore udp udp.dest=udp.ntp ignore udp udp.source=udp.ntp ignore udp udp.dest=udp.timed ignore udp udp.source=udp.timed # Don't bring up on domain name requests between two running nameds. ignore udp udp.dest=udp.domain,udp.source=udp.domain # Bring up the network whenever we make a domain request from someplace # other than named. accept udp 30 udp.dest=udp.domain accept udp 30 udp.source=udp.domain # Do the same for netbios-ns broadcasts # NOTE: your /etc/services file may not define the netbios-ns service # in which case you should comment out the next three lines. ignore udp udp.source=udp.netbios-ns,udp.dest=udp.netbios-ns accept udp 30 udp.dest=udp.netbios-ns accept udp 30 udp.source=udp.netbios-ns # keep routed and gated transfers from holding the link up ignore udp tcp.dest=udp.route ignore udp tcp.source=udp.route # Anything else gest 2 minutes. accept udp 120 any # Catch any packets that we didn't catch above and give the connection # 30 seconds of live time. accept any 30 any
#General Options mode ppp fifo /etc/diald/diald.ctl #Device configuration #connect /etc/sysconfig/network-scripts/ifup ppp0 connect "/etc/diald/diald.connect" device /dev/ttyS1 speed 38400 modem lock crtscts local 192.168.0.1 remote 192.168.0.2 dynamic defaultroute include /usr/lib/diald/standard.filter
