public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <jjs@toyota.com>
To: "Sim, CT (Chee Tong)" <CheeTong.Sim@sin.rabobank.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: [OT] Re: Linux NAT questions- (kernel upgrade??)
Date: Wed, 02 May 2001 10:24:18 -0700	[thread overview]
Message-ID: <3AF042C2.2BF4716B@lexus.com> (raw)
In-Reply-To: <1E8992B3CD28D4119D5B00508B08EC5627E8A4@sinxsn02.ap.rabobank.com>

"Sim, CT (Chee Tong)" schrieb:

> 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

uname -a

> and
> how to upgrade it??

Either upgrade to a distro that includes the new kernel
(e.g. latest SuSE or Red Hat) or download kernel source
and compile. It might be helpful to provide the distribution
and version you are using (Red Hat 6.2, Slackware 7,
Debian Potato, etc)

> [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

Yes, of course iptables won't work with the old kernel.
If you want to stay with the old kernel, you must use
ipchains instead.

cu

Jup


  parent reply	other threads:[~2001-05-02 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 10:14 Linux NAT questions- (kernel upgrade??) Sim, CT (Chee Tong)
2001-05-02 11:09 ` Michel Wilson
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 ` J Sloan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-03  1:20 [OT] " Sim, CT (Chee Tong)
2001-05-03  2:41 ` 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=3AF042C2.2BF4716B@lexus.com \
    --to=jjs@toyota.com \
    --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