From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: Invalid argument Error : DNAT rule at OUTPUT chain in arm-linux box
Date: Fri, 12 Oct 2007 17:33:50 +0200 [thread overview]
Message-ID: <470F93DE.5060307@plouf.fr.eu.org> (raw)
In-Reply-To: <470f9225.1997600a.2d3f.3a27@mx.google.com>
Hello,
Sathish Kumar.R a écrit :
>
> I have a problem while executing the followng DNAT rule at arm-linux box,
>
> Box = "Linux 2.4.27-uc1 #6 Mon Oct 8 22:12:01 IST 2007 armv5b unknown"
> iptables version: "iptables v1.2.7a"
>
> Executed Rule
> -------------
> iptables -t nat -A OUTPUT -p tcp --dport 80 -j DNAT --to-destination
> 10.0.1.1
> iptables: Invalid argument
> ..
>
> the above rule executed on intel box without any errors,
> even the same rule at PREROUTING chain working successfully on arm-linux box
> but in OUTPUT chain, i am getting this trouble, as "iptables: Invalid
> argument"
NAT in the OUTPUT chain is optional until version 2.4.29. Check that
your kernel has CONFIG_IP_NF_NAT_LOCAL=y.
prev parent reply other threads:[~2007-10-12 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 15:26 Invalid argument Error : DNAT rule at OUTPUT chain in arm-linux box Sathish Kumar.R
2007-10-12 15:33 ` Pascal Hambourg [this message]
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=470F93DE.5060307@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter@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