First off, which version of Linux are you using?And, where did you get
diald
(the filename should tell us which version)?
Second, the test script is dialdc (note the 'c'). Run diald once and
it will
set itself up as a daemon. Then you can play with dialdc up etc. I
recommend
you play with dctrl instead if you are running X windows.
Third, installing diald should have made /etc/diald. It may or may not
have put some
files in there. Also /usr/lib/diald will have some example files in
its contrib directory.
And man diald.examples has several examples, at least one of which
covers
your setup.
/etc/diald should have connect, diald.conf, diald.defs, diald.ctl, and
perhaps
phone.filter. diald.ctl is the management pipe and is automatically
created by
running diald. leave diald.defs and phone.filter alone also. connect
is the
script diald runs to establish your ISP connection. diald.conf is read
by diald
when it starts up. connect and diald.conf are fairly well commented
and have
only a few places that need customization.
If you are using linuxconf to manage your system, go to its Control
Panel, then to
Control Service Activity, and enable diald. Otherwise invoke it as
/usr/bin/diald
in your /etc/rc.d/rc.local script. Do a ps ax | grep diald to see if
it got started by
linuxconf (sometimes it doesn't when you first configure it). If not
running, you
can either start it by hand or restart your system. The latter is maybe
a good thing
to do anyway once you think you have your configuration set up, as
confirmation
that it really does lnow what to do for you now.
Hope this helps.
Brian Witowski wrote:
Greetings,Im still hacking away trying to get this garbage to work. How many different versions are
floating around? I read one text that said to use 'diald start' and when I tried it, it didnt work.
Just exactly how do I get this thing to work? I tried starting it with 'diald up' and it didnt work.
It did however succeed in taking down the rest of my network. I read the man page until
I couldn't see straight. With every document I read I see more references to other config files.
Are there any 'real-world' documents floating around that document
exactly which files need to be in place and where they should be and what they should
contain? An example file isnt worth anything if the lines arent documented so I can apply
it to my system. My system is about as basic as it gets. (1) Linux box and (1) Win98 box.
And (1) dynamic dial-up internet account. Samba works great. I can ping till the cows come
home. I've installed and tested ipfwadm and it works great if I go start my dialer (Xisp) every time.
Oh yes, how do I check the version of something?
I would really appreciate some input here. Not a link to more confusing documentation that
presents another 8 conf files that the others didnt mention.Brian
--
Dave Warman
====================================================
Warman's First Law:
Everything that can be configured, must be
Corollary:
Defaults aren't
