Nicolas Blanc wrote:
> On 2 Oct, Tim MacDonald wrote:
> > Hi,
> > I am not able to connect using diald.
> > The following messages are found in /var/log/messages:
> >
> > Sep 20 18:02:09 timmip pppd[4833]: Using interface ppp0
> > Sep 20 18:02:09 timmip pppd[4833]: Connect: ppp0 <--> /dev/ttyS0
> > Sep 20 18:02:39 timmip pppd[4833]: LCP: timeout sending Config-Requests
> > Sep 20 18:03:09 timmip diald[4658]: pppd startup timed out. Check your
> > pppd options. Killing pppd.
> > Sep 20 18:03:09 timmip diald[4658]: stop ppp0: SIOCDELRT: No such
> > process
> >
> > If you have any clues as to how I can go about debugging these
> > messages, I would appreciate it.
> >
> > Thanks,
> > -timm
> >
>
> Can you send your /etc/ppp/options file and your config....
>
> Niko
Thanks for the response ... here's my ppp options file, which is referenced
from
the diald.conf file, followed by the diald.conf file.
******************************
/etc/ppp/options.diald
******************************
remotename ppp0
ipparam ppp0
******************************
/etc/diald.conf
******************************
#------------------------------------------------------------------------------
# Rules for TCP packets.
#------------------------------------------------------------------------------
# General comments on the rule set:
#
# In general we would like to treat only data on a TCP link as signficant
# 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
# 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 240 tcp.dest=tcp.www
accept tcp 240 tcp.source=tcp.www
# 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 240 tcp.dest=tcp.ftp
accept tcp 240 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 240 tcp.dest=tcp.ftp-data
accept tcp 240 tcp.source=tcp.ftp-data
# If we don't catch it above, give the link 10 minutes up time.
accept tcp 600 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 240 udp.dest=udp.domain
accept udp 240 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 240 any
# Catch any packets that we didn't catch above and give the connection
# 30 seconds of live time.
accept any 240 any
#### Diald configuration options
debug 0x7f
mode ppp
pppd-options file /etc/ppp/options.diald
device /dev/ttyS0
speed 38400
crtscts
defaultroute
lock
modem
lcp-max-configure 20
lcp-restart 5
dynamic
local 127.0.0.2
remote 127.0.0.3
connect "/usr/sbin/chat -v -r /etc/ppp/report-chat -f
/etc/ppp/ppp.chatscript
# This is needed because we want a single data stream through which data
# flows. We don't want the interfaces changing.
-reroute
# This is needed so we run the firewall script at every start. We get a
# different IP address from the ISP each time.
ip-up /usr/lib/diald/firewallon
# When we shut down the link, reset the firewall rules.
ip-down /usr/lib/diald/firewalloff
buffer-timeout 180
first-packet-timeout 120
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
