Bug 88308 - CONFIG_IP_NF_NAT_LOCAL is not set
Summary: CONFIG_IP_NF_NAT_LOCAL is not set
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel
Version: 2.1
Hardware: ia64
OS: Linux
Target Milestone: ---
Assignee: Larry Woodman
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-08 19:56 UTC by Ryan Bradetich
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-10-19 19:25:11 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Ryan Bradetich 2003-04-08 19:56:09 UTC
Description of problem:

The kernel-smp-2.4.18-e.25 does not have the following kernel configuration item
set: CONFIG_IP_NF_NAT_LOCAL.  In the latest update kernel for Red Hat 7.3 (this 
is the only one I have looked at) this option is set to =m, on RedHat 2.1AS for 
ia64 this option is not set.  This affects the usage of iptables for NAT to the 
OUTPUT chain.

Version-Release number of selected component (if applicable):

How reproducible: Always

Steps to Reproduce:

1. On a kernel with # CONFIG_IP_NF_NAT_LOCAL is not set do this command:

2. /sbin/iptables -t nat -A OUTPUT --dst -p tcp --dport 993 -j DNAT --

The result is: iptables: Invalid argument.

3. On a kernel with CONFIG_IP_NF_NAT_LOCAL=m do the same command.

4. this works.

Additional info:

I have a support contract for RHAS 2.1 on ia64 with Hewlett-Packard also.  The 
Hewlett-Pakcard Response center, my customers, and I figured out the solution to
the problem.  I would like to see this integrated into the official Red Hat 
kernel so I can still utalize this support contract if necessary.

Comment 1 RHEL Program Management 2007-10-19 19:25:11 UTC
This bug is filed against RHEL2.1, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products.  Since
this bug does not meet that criteria, it is now being closed.

For more information of the RHEL errata support policy, please visit:

If you feel this bug is indeed mission critical, please contact your
support representative.  You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.