Hi Dick,
sorry for my more-than-one-month-delay in replying. The reason was my yearly
holidays, but it's over now, :-(
I think we don't need some conventional setup help any longer due to the
"spurious_routing_failures" (from CHANGES file of 0.16) of version 0.14, that
have been (over-)corrected already by 0.15 and now erased by 0.16 which works on
my system now.
(Does it really work? See my two other postings on the list:
"Connection hold up / renewed continously" and "diald sometimes doesn't bring a
link up")
When I read your diald.conf, that reminds me of an aspect in the diald manpage
which I wanted to ask something about already for a few times: it is the section
the pppd_options.
It tells us - a bit simplified - that we should not pass on a certain set of
options to pppd, not even to put them into a /etc/ppp/options file, but to write
them directly into the diald.conf file.
This set explicitely includes the lock option, and I could follow this directive
except for lock.
That is because diald locks the serial device /dev/modem (links to /dev/ttyS0)
before it calls pppd which then can't connect to my ISP of course. Therefore I
left this option in the options file which is passed on to pppd.
How do you (or anyone reading this) think about this? Did anybody observe this
strange behaviour?
> My route resolution problem was casued mainly by a redundant 'defaultroute'
> option. This should not appear in /etc/ppp/options but in /etc/diald.conf
> (when diald is to be used).
I find it very interesting that two different things like "spurious_routing" in
V. 0.14 and a redundant 'defaultroute' can cause (nearly) the same effects to
observe.
> Under Linux it is necessary to set a flag in the ip_dynaddr file (see the lines
> from my rc.local below).
This has a respect to the thread "Connection hold up / renewed continously".
There I received an answer which recommends an 'echo 5 >
/proc/sys/net/ipv4/ip_dynaddr' for clearing a remaining IP socket to me.
But what causes the socket to still remain after diald has disconnected?
And why do I have to manually clear the socket? I want diald to do this or
anyway to be done automatically!
How can I solve this problem in an elegant way?
> Files:
> >From my rc.local file:
shortened to a few parts by me.
> [...]
> #Following for use with diald
> /sbin/ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0
>
> echo "1" > /proc/sys/net/ipv4/ip_forwarding #start IP forwarding
> echo "1" > /proc/sys/net/ipv4/ip_dynaddr #dynamic address flag (1 for
> #normal, 5 to clear socket)
These commands are given only at the startup of diald, right?
When should I execute 'echo "5" > /proc/sys/net/ipv4/ip_dynaddr' to kill the
socket whenever it remains existing without a connection?
>
> #start diald
> echo "starting diald"
>
> my /etc/diald.conf file
> mode ppp
> connect "/usr/sbin/chat -f /etc/sysconfig/network-scripts/chat-ppp0"
> device /dev/cua0
> speed 115200
> modem
> lock
No problem with 'lock' there? I observed pppd looking at first for a lock file
and if it finds one it refuses to continue, and I find that's normal.
> crtscts
> local 192.168.1.20
> remote 192.168.1.21
> dynamic
> defaultroute
> include /usr/lib/diald/standard.filter
> [...]
>
> my /etc/sysconfig/network-scripts/ifcfg-ppp0:
> PERSIST="no"
> DEFROUTE="no"
> ONBOOT="no"
> INITSTRING="AT&F&D2&C1X4V1Q0S6=3S7=70&M4&B1&H1&R2M0"
> MODEMPORT="/dev/cua0"
> LINESPEED="115200"
> ESCAPECHARS="no"
> DEFABORT="yes"
> HARDFLOWCTL="yes"
> DEVICE="ppp0"
> PPPOPTIONS=""
> DEBUG="yes"
> PAPNAME="rlpcon"
> REMIP=""
> IPADDR=""
> BOOTPROTO="none"
> MTU=""
> MRU=""
> DISCONNECTTIMEOUT="5"
> RETRYTIMEOUT="0"
> USERCTL="yes"
> NETMASK="255.255.255.0"
What program uses this file?
> Note that the use of a correct modem string is important.
Do you mean the modem initialization string beginning with AT...?
If so, OK, I think that's basically necessary for making the connection via
phone lines.
Now my configuration files:
---------------------------------------------------------------------------------------
/etc/suseppp/diald/generic.diald - passed on to diald by a startup script after
booting
device /dev/modem
mode ppp
#lock
modem
crtscts
speed 115200
local 192.168.1.1
remote 192.168.1.2
defaultroute
dynamic
disconnect-timeout 300
redial-timeout 5
#first-packet-timeout 80
retry-count 0
died-retry-count 0
#redial-backoff-start 10
dial-fail-limit 1
fifo /etc/diald.fifo
accounting-log /var/log/diald.acc
# Define DEBUG flags (from diald.h) HEX BIN DEC
# DEBUG_FILTER_MATCH 0x0001 0000001 1
# NOT IN USE !!! 0x0002 0000010 2
# DEBUG_PROXYARP 0x0004 0000100 4
# DEBUG_VERBOSE 0x0008 0001000 8
# DEBUG_STATE_CONTROL 0x0010 0010000 16
# DEBUG_TICK 0x0020 0100000 32
# DEBUG_CONNECTION_QUEUE 0x0040 1000000 64
# DEBUG level = bitwise logical OR of flags
debug 0010001
# +++++ Zeittakte im City-Tarif der Deutschen Telekom AG +++++
# An Werktagen (Mo - Fr)
restrict 00:00:00 05:00:00 1-5 * *
impulse 230,10
restrict 05:00:00 09:00:00 1-5 * *
impulse 140,10
restrict 09:00:00 18:00:00 1-5 * *
impulse 80,10
restrict 18:00:00 21:00:00 1-5 * *
impulse 140,10
restrict 21:00:00 23:59:59 1-5 * *
impulse 230,10
# An Wochenenden (Sa, So)
restrict 00:00:00 05:00:00 6,0 * *
impulse 230,10
restrict 05:00:00 21:00:00 6,0 * *
impulse 140,10
restrict 21:00:00 23:59:59 6,0 * *
impulse 230,10
-------------------------------------------------------------------------------------
/etc/suseppp/generic.options - the file which diald passes on to pppd
#/dev/modem
#115200
#crtscts
#modem
lock
user <my loginname>
192.168.1.1:192.168.1.2
ipcp-accept-local
ipcp-accept-remote
#0.0.0.0:
noipdefault
#defaultroute
-ipx-protocol
#debug
--------------------------------------------------------------------------------------
/etc/diald.conf contains the filter rules.
May be you can find a misfit in my files, but I don't believe this ;-)
Thanks to all for dealing with my problems.
Best regards, Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
