I have a similar RH setup. Prior to last week I was using RH6.0
and DIALD 16.5, and experienced no problems. Last week
I upgraded to RH6.1 and DIALD 99.x. At that point I started
experiencing problems. However, I have since then corrected
them. These problems were not like yours - PPPD changes
caused me to change my PPP Secrets and Options Files.
I do see the error with TAP Devices missing, as well as, the
weird routing addition by LinuxConf, but none of the erroroneous
operation you are seeing. Additionally, I must say that I have
experienced some weirdness with RH LinuxConf
(both with RH6.0 and RH6.1), with it not maintaining settings,
as well as, erroneously overwriting settings when you don't
expect it (if you look on the RH FTP Sight there is a new version
of LinuxConf for RH6.0 -- I did not upgrade to this, but you may
want to give it a try -- I don't remember the bugs it fixes -- you
will have to look on the RH 6.0 Errata Area on the RH Site).
The link you are trying to setup is a Serial/Modem Link ? From
the Errors it appears DIALD does not understand the Device Type.
If Modem, are you correctly specifying the Serial Device (if I
remember correctly you have to create the symbolic link between
/dev/modem and your serial port on RH6.0 -- I run several different
distributions, so I can't always keep track of the quirks of each).
Are you specifying the same Device to DIALD and PPPD (if
I remember under LinuxConf PPP uses the /dev/ttySx while the
DIALD Example Configs use /dev/modem) ?
Please provide a copy of your diald.conf, your forwarding
and masquerading rules from rc.local.
Have you changed any of the Protocol Timings in your filters file ?
Also, you may want to use the ANOTHER LEVEL OF MENUS - ADMIN - NETWORK
CONFIGURATION to look at your Network Settings. Under Routing, do you have
IPV4
Forwarding Enabled ? Under Routing what do you have as your Default Gateway
and Default Routing Device ?
Below are my Forwarding and MasQ Rules from rc.local
/sbin/depmod -a
/sbin/modprobe ip_masq_ftp
/sbin/modprobe ip_masq_raudio
/sbin/modprobe ip_masq_irc
ipchains -P forward DENY
ipchains -A forward -s 192.168.2.0/24 -j MASQ
All of the above are merely suggestions of some things to
take a look at. You probably have been through these several
times -- As I have done in the past -- "Needle in the Haystack"...
You may want to think about upgrading to RH6.1. It has the 2.2.12
Kernel, and the Installation is setup and built for Pentium Class
Machines (not the 386 level as with RH6.0) -- Noticable Performance
Improvements.
Jeff
----- Original Message -----
From: Morris Maynard <[EMAIL PROTECTED]>
To: Linux-Diald <[EMAIL PROTECTED]>
Sent: Friday, November 12, 1999 12:00 AM
Subject: diald 0.99 warnings and won't hangup
> I looked through the text in the source distrib and found a note about
using
> diald with masquerading. It seems likely that diald is not getting the
> packets it is supposed to be monitoring at all - apparently with this
> version, I have to build scripts to change around the ipchains rules when
> the link goes up and down. I guess whatever hack was used before (which
got
> in trouble when the default route changed) is gone. Well, if this seems
like
> a reasonable guess (or not) please chime in. I'm gonna go try to make an
> addroute script. One problem is that linuxconf, for an unknown reason,
adds
> a rule to the chain during bootup. Oh, well...
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
