From: "D. Stimits" <stimits@idcomm.com>
To: Ted Gervais <ve1drg@ve1drg.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ipchains
Date: Mon, 18 Jun 2001 11:09:22 -0600 [thread overview]
Message-ID: <3B2E35C2.69CEC5D9@idcomm.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0106181256120.2050-100000@ve1drg.com>
Ted Gervais wrote:
>
> I just ran into something odd. To me anyways, it was odd.
> I just installed and brought up kernel 2.4.5 and my ipchains failed.
> So I upgraded to the latest (that I could find) ipchains-1.3.10, and
> that also fails.
>
> Has anyone got any version of ipchains to work with the new(er) kernels?
>
> ---
> Doubt is not a pleasant condition, but certainty is absurd.
> -- Voltaire
>
> Ted Gervais <ve1drg@ve1drg.com>
> 44.135.34.201 linux.ve1drg.ampr.org
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
It works, but you can't load iptables modules at the same time as
ipchains. Be sure ipchains is the only module you are loading. rmmod any
iptables items before modprobe of ipchains. If you are running redhat,
also do not believe the script in /etc/rc.d/init.d/ipchains as to
whether or not ipchains is actually running, it is broken (does not
check return values), and lies and does not tell you when ipchains
startup fails (as root manually do something like ipchains -L -n).
D. Stimits, stimits@idcomm.com
next prev parent reply other threads:[~2001-06-18 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 15:57 ipchains Ted Gervais
2001-06-18 16:20 ` ipchains Fabian Arias
2001-06-18 17:09 ` D. Stimits [this message]
2001-06-18 19:09 ` [OT] ipchains J Sloan
2001-06-18 20:37 ` Ted Gervais
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B2E35C2.69CEC5D9@idcomm.com \
--to=stimits@idcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ve1drg@ve1drg.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox