List fellow members:

This is a slightly edited post I'm resending since this problem seems 
arising over and over so here it goes again (Edward, I'm taking your 
suggestion in consideration, but I think it needs more work to become a 
Web page).

First I think that the problem arises with RedHat 6.0 and based 
distributions, which lack a good stock /etc/conf.modules. I myself only 
noted the situation by accident since I normally use Debian based 
distributions and the earlier versions of RedHat didn't seem to have 
this problem.

Here goes the stuff:

First I'll assume you have pppd configured RedHat style and that it is 
built as modules and that the ethertap device and af_packet are also 
built as modules.

Now, start by issuing the following as root "tail -f /var/log/messages 
>/dev/tty12&" to get a easy way to see what is going on with pppd and 
diald (you must replace /var/log/messages with your syslog file - look 
at /etc/syslog.conf - if your distributioin isn't RedHat style). This 
step is not essential but eases error trapping and can be stopped with 
"killall tail".

Start pppd the usual way, maybe "ifup ppp0", and take a look at console 
12 with [ALT]-[F12].

If you find any reference to "ppp-compress-21", "ppp-compress-24" or 
"ppp-compress-26" not being found just edit /etc/conf.modules and add 
the following lines:

...
# PPP compress modules
alias ppp-compress-21 bsd_comp
alias ppp-compress-24 ppp_deflate
alias ppp-compress-26 ppp_deflate
...

It is time to get diald.

Join http://rufus.w3.org/linux/RPM/DByName.html and get 
diald-0.99.1-2.i386.rpm and diald-config-0.16.5a-1.i386.rpm (don't get 
fooled by version numbers, diald-config-1.2.1-1.noarch.rpm is older). 
By the way if you get 
ftp://rufus.w3.org/pub/rpmfind/rpmfind-rh6-1.2-1.i386.rpm you can use 
it to fetch, check for and upgrade rpm packages.

Now here we have to take some care. The above is true for RedHat 6.0 
and based distributions. If yours is older you _must_ use a diald 
version compiled against the libraries used on your system.
If in doubt issue "ls /lib/libc.so*" and compare the result with the 
needed libraries found on the corresponding diald version Web page. You 
can always get the source code and compile it yourself on your system, 
but this is a quick receipt not a lengthy explanation.

Install diald with "rpm -Uhv diald-0.99.1-2.i386.rpm" and diald-config 
with "rpm -Uhv diald-config-0.16.5a-1.i386.rpm".

OK, here we can go two ways, either edit /etc/rc.d/init.d/diald and add 
"-f /etc/diald/diald.conf" to the line that starts diald, or create a 
/etc/diald.conf that points to the /etc/diald/ directory (I prefer the 
second method so I run "echo include /etc/diald/diald.conf 
>/etc/diald.conf" and then do a "chmod 700 /etc/diald.conf").

Now it is time to customise the /etc/diald/diald.conf file, since it 
was built with version 0.16.5a in mind.

Edit /etc/diald/diald.conf and comment out "pppd-options name pppanex 
:" since it won't be likely to be the name you use to access your ISP 
(if you use PAP or CHAP don't comment it, replace it with the name you 
use to access your ISP), and "up-delay 5" since it seems deprecated. 
Also uncomment the "include /etc/diald/phone.filter" line and comment 
the "accept any 480 any" since it would give a very long wait time for 
the line to go down. Now it is a good time to take a look at "man 
diald" and find if you would like to add any new options.

Check out /etc/ppp/options and remove any references to the commands 
indicated in diald man page, for instance "lock" (if you still want to 
connect directly with "if-up ppp0" add any commands you removed from 
/etc/ppp/options to the corresponding 
/etc/sysconfig/network-scripts/ifcfg-ppp0 file).

Next we must edit our connect script /etc/diald/connect to meet our 
needs. Almost all possible options are well commented so just take a 
look at /etc/sysconfig/network-scripts/chat-ppp0 for the correct 
answers to put in the file. Here goes an extra for PAP or CHAP, add to 
either /etc/ppp/pap-secrets or /etc/ppp/chap-secrets "username * 
password" with username and password replaced with the correct values, 
set "pppd-options user username" in /etc/diald/diald.conf also with 
username replaced with the correct value and leave USER_NAME empty in 
the /etc/diald/connect script.

All done. Let's cross our fingers and start the diald daemon with 
"/etc/rc.d/init.d/diald restart". Now switch to the console 12 with 
[ALT]-[F12].

Trap errors, like for instance chat errors and, if any, try to find out 
what did you mistype in the connect script.

If your system is configured as I assumed on the first line you will 
have two fatal errors both module related, so any reference to 
tap0-tap15 devices and module net-pf-17 not found are, I believe, due 
to a poor RedHat 6.0 stock /etc/conf.modules file. Let's fix it:

Add to /etc/conf.modules the following

...
# tap device configuration
alias tap0 ethertap
        options tap0 -o tap0 unit=0
alias tap1 ethertap
        options tap1 -o tap1 unit=1
alias tap2 ethertap
        options tap2 -o tap2 unit=2
alias tap3 ethertap
        options tap3 -o tap3 unit=3
alias tap4 ethertap
        options tap4 -o tap4 unit=4
alias tap5 ethertap
        options tap5 -o tap5 unit=5
alias tap6 ethertap
        options tap6 -o tap6 unit=6
alias tap7 ethertap
        options tap7 -o tap7 unit=7
alias tap8 ethertap
        options tap8 -o tap8 unit=8
alias tap9 ethertap
        options tap9 -o tap9 unit=9
alias tap10 ethertap
        options tap10 -o tap10 unit=10
alias tap11 ethertap
        options tap11 -o tap11 unit=11
alias tap12 ethertap
        options tap12 -o tap12 unit=12
alias tap13 ethertap
        options tap13 -o tap13 unit=13
alias tap14 ethertap
        options tap14 -o tap14 unit=14
alias tap15 ethertap
        options tap15 -o tap15 unit=15

alias net-pf-17 af_packet # Needed for diald
...

And create the tap devices with the corresponding "mknod /dev/tap* c 36 
NN" command (NN starts at 16 for tap0 and goes incremented by 1 until 
31 for tap15). You don't need to create all tap devices but I recommend 
at least one more than those you know you'll need just to stay on the 
safe side.

Now start again the diald daemon and check console 12 for errors. If 
any that you can't fix just drop a copy of the relevant part of your 
syslog file on the list, and we'll try to help.

Hope this helps.

---
Lazarus Long
<[EMAIL PROTECTED]>
PGP: 
<http://wwwkeys.pgp.net:11371/pks/lookup?op=index&search=0x5C1DC205>
ICQ#: 30062012

-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to