From: "Michel Wilson" <michel@procyon14.yi.org>
To: "Sim, CT \(Chee Tong\)" <CheeTong.Sim@sin.rabobank.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Linux NAT questions- (kernel upgrade??)
Date: Wed, 2 May 2001 13:09:33 +0200 [thread overview]
Message-ID: <NEBBLEJBILPLHPBNEEHIIEGHCEAA.michel@procyon14.yi.org> (raw)
In-Reply-To: <1E8992B3CD28D4119D5B00508B08EC5627E8A4@sinxsn02.ap.rabobank.com>
> Hi.. I follow your instruction, but I encounter this issue, my kernel need
> to be upgrade? MAy I know how to determine the current kernel version and
> how to upgrade it??
You can see the current kernel version by doing uname -a. It is also shown
at boot time.
>
>
> [root@guava /root]# iptables -t nat -A PREROUTING -p tcp --dst
> 1.1.1.160 -i
> eth1 -j D
> NAT --to-destination 192.168.200.2
> iptables v1.1.1: can't initialize iptables table `nat': iptables who? (do
> you need to insm
> od?)
> Perhaps iptables or your kernel needs to be upgraded.
>
>
> [root@guava simc]# rpm -ivh iptables-1_2_0-6_i386.rpm
> error: failed dependencies:
> kernel >= 2.4.0 is needed by iptables-1.2.0-6
For iptables you'll need kernel >= 2.4.0, as stated. I don't know if RedHat
has a precompiled rpm somewhere (i don't use RedHat) but i would think so.
You might ask your local RedHat guru ;-).
Other options are:
- build your own 2.4.x (see Kernel-HOWTO, if it's not too outdated)
- use ipchains.
I don't know ipchains enough to tell you how to do it, i don't even know if
it's possible.... But
http://www.linuxdoc.org/HOWTO/IP-Masquerade-HOWTO-6.html#ss6.8 may be of
interest to you.
Greetings,
Michel Wilson.
next prev parent reply other threads:[~2001-05-02 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 10:14 Sim, CT (Chee Tong)
2001-05-02 11:09 ` Michel Wilson [this message]
2001-05-02 12:22 ` Feng Xian
2001-05-02 12:38 ` Russell King
2001-05-02 12:44 ` Vivek Dasmohapatra
2001-05-02 17:24 ` [OT] " J Sloan
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=NEBBLEJBILPLHPBNEEHIIEGHCEAA.michel@procyon14.yi.org \
--to=michel@procyon14.yi.org \
--cc=CheeTong.Sim@sin.rabobank.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®