I'm just pulling this one out of the air, but kernel 2.1.x and greater
use ipchains for firewalling where 2.0.x used ipfwadm. It could be that
your firewalling rules are no longer any good.
This is one reason why I haven't installed the new 2.2.x kernel. I
barely understand some of ipfwadm (enough to make it work at least) and
ipchains is just plain confusing for me (anyone care to write an
"Ipchains For Dummies," "Idiots Guide To Ipchains," or even just a better
tutorial than what's on the ipchains homepage?)
peace favor your sword
----------
From: Michael Barron
Sent: Thursday, February 04, 1999 9:57 PM
To: LKLawson; 'LINUX-DI@SMTP <[EMAIL PROTECTED]>'
Subject: Kernel 2.2.0 and diald
I recently installed a new hard drive in my RedHat 5.1 system, and did a
complete re-install in the process. I installed the 2.2.0 kernel,
compiling in the options as before--IP masquerading, PPP and SLIP
support, etc.
I reinstalled diald and restored my diald.conf, standard.filter, and
connect script files. Diald worked without a hitch before, but now it
will no longer dial on its own; I must do a 'diald up' to initiate the
connection. I thought it may be a problem with my masq configuration,
but it refuses to "auto-connect" as it should on the Linux box, as well.
Any ideas?
Thanks,
Michael Barron
-
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]
