"Adams, James" wrote:
> Thanks Once Again,
> I believe my single brain-cell is beginning to flicker. When I
> installed the diald .99 tarball no configuration files were included. So if
> Mr. Brain-Cell is correct, I could reinstall .99 then install the 0-16
> config rpm and continue on from there? Or am I totally confused?
I mean no disrespect, but it sounds like Mr Brain-Cell is, er, unaccustomed to
dealing with these matters. Here is a step-by-step checklist that should see you
through.
Why am I doing this? am I nuts? It's much more fun to watch you struggle. Not!
I'm posting it to the list in the vain hope that others will see it and avoid
difficulty. ALL READERS PLEASE NOTE: I'd be grateful if you could quickly check
this through for errors. If you find any mistakes or have any other suggestions
please email them to me. I'll repost any updated versions.
The advantage of following this procedure is that it will preserve your
existing diald configuration in /etc/diald.conf and any boot scripts which
might be in the rpm. You should really have a script which starts up diald with
the required parameters upon booting.
Here goes, then:
==========================================================================
The "How To Upgrade From Diald-0.16 RPM Via Diald-0.99 Tarball" MINI-HOWTO
==========================================================================
1) First make copies of any diald configuration files you have customised
previously, just in case of diasaster.
2) Then kill the diald daemon and remove all traces of diald installation.
Do 'rpm -e diald' if you have the rpm installed. If you used the tarball,
you have to do it by hand. If you can't figure out where the files live,
see below for clues.
3) Then do a clean installation of the diald-0.16 rpm, and use whatever
procedure you have to get diald up and running and try some pings, http
and ftp connections to check that diald is working correctly bringing
the link up and down as needed.
4) Know your diald installation. This means finding out where key diald
files live. These are:
diald
- the executable
dctrl
- the Tcl-based diald control application
diald.defs
- the file that defines how the headers of certain packets look
standard.filter
- the default set of filter rules
connect
- a template script for diald to use for dialling out
diald.8, dctrl.1, diald-examples.5, dial-control.5, diald-monitor.5
- all the diald man pages
The best way to do this is just to enter one of the following commands:
'rpm -ql diald'
or
'rpm -qpl diald-0.16-whatever.rpm'
It will tell you where these files are located when you are using that
rpm version.
5) make sure you have the tarball for diald-0.99 and not diald-0.99.1, the
latter is not up to scratch.
6) Then unpack the diald-0.99 tarball into a clean directory tree and cd into
it. If you *must* use one you already unpacked then cd into the directory
with the Makefile and enter the command "make clean".
7) Edit the file called Makefile:
7.1) find the bit at the top where it says:
# Once you have read, understood, and made any necessary changes
# you may comment out the next two lines.
unconfig:
@echo 'EDIT THE CONFIG SETTINGS IN THE MAKEFILE!'; exit 1
7.2) and put hash marks at the beginning of those 'unconfig' and '@echo'
lines.
7.3) Save and quit.
You don't need to change the directory paths in the makefile as these are the
same in the current tarballs as they are in the old rpm.
8) Then enter the command "make". This will compile the binary.
9) Now, you have two options for installation. First cd into the directory
tree where you did the 'make' command, and then EITHER:
9.1.a) manually: get the files to be installed and copy them to the
locations you got from the rpm commands, and which should be correct
in at the top of the Makefile.
Get them from where? if you are in the right directory, the
executables are in that same directory, the defs and filter are
in ./config and the man pages are in ./doc. There is no diald.conf
supplied with this tarball, you are going to use your old one.
*OR*
9.1.b) just run 'make install' instead (should work OK).
10) Check configuration files.
If you backed up any specially customised configuration files then restore them
now. Otherwise, realise that you now have the configuration files from
diald-0.99 except the diald.conf which comes from the diald-0.16 rpm.
Your old installation probably used /usr/lib/diald/standard.filter directly
as a filter rules file, and put all the diald options into /etc/diald.conf. You
should have something like the following in the diald.conf:
device /dev/modem
-m ppp
speed 115200
two-way
local your.computers.ppp.ipaddress
remote your.isps.ppp.ipaddress
connect /usr/lib/diald/connect
file /usr/lib/diald/standard.filter
defaultroute
disconnect-timeout 30
redial-timeout 0
dial-fail-limit 5
fifo /var/adm/diald/diald.ctl
debug 31
There will need to be either a 'file' reference to standard.filter or another
file of filter rules or else the filter rules must be present in this file
itself. Please note:
***
***If diald finds no filter rules it will match no packets***
***and will never dial out.***
***
your.computers.ppp.ipaddress and your.isps.ppp.ipaddress will be whatever your
ISP has told you. If the ISP uses dynamic IP allocation at either end of the
link then you need to add the 'dynamic' option to this file and set these
addresses to arbitrary private IP address values which you are not currently
using. Thus you might set them to 192.168.0.1 and 192.168.0.2. But not if you
are already using those on your internal network! The numbers picked must be
currently unused, and fall between one of the following inclusive ranges:
10.0.0.1 - 10.25.255.254 Class A - humungous networks
172.16.0.0 - 172.31.255.254 Class B - big networks
192.168.0.1 - 192.168.255.254 Class C - normal (little) networks
Assuming you use a fifo named as in the above example, then as root, do the
following:
mkfifo /var/adm/diald/diald.ctl # make control fifo for dctrl
chmod ugo=rw /var/adm/diald/diald.ctl # so everyone can control link
11) If you have all your diald options in /etc/diald.conf and your ppp options
in /etc/ppp/options then diald can be started without any command-line
parameters as everything is in the default location.
Sensible ppp options might be:
noipdefault
debug
noauth
crtscts
lock
modem
asyncmap 0
nodetach
noproxyarp
noipx
local.IP.address:remote.IP.address
Only supply values for that last line if they are static, i.e. permanent
assignments and not dynamically allocated. Otherwise, leave them out.
If you've got a set in your /etc/ppp/options that is known to work then leave
them alone.
12) Restart diald in the way you normally do (again, I mean restarting the
diald daemon, not just dialling out).
--
[EMAIL PROTECTED] Ralph Clark, Virgo Solutions Ltd (UK)
__ _
/ / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable *
/ /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day*
/____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
