From: Herman <Herman@AerospaceSoftware.com>
To: netfilter@lists.netfilter.org
Subject: Re: Invalid friggen argument
Date: Tue, 14 Oct 2003 07:14:47 -0600 [thread overview]
Message-ID: <200310140714.47291.Herman@AerospaceSoftware.com> (raw)
In-Reply-To: <1066111459.2383.67.camel@alpha.newkirk.us>
On Tuesday 14 October 2003 12:04 am, Joel Newkirk wrote:
Have you checked lsmod, to make sure you have iptable_nat loaded? If
not, try "modprobe iptable_nat" then try your rule again.
The trouble was not iptable_nat, but rather iptable_mangle. It seems that nat
doesn't work if iptable_mangle is not loaded - who woulda thunkit?
I was mislead by a Rehat script, which stated that it isn't needed for nat,
but apparently it is indeed.
Cheers,
--
Herman
next prev parent reply other threads:[~2003-10-14 13:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 7:41 Invalid friggen argument Herman
2003-10-12 11:08 ` Willy TARREAU
2003-10-12 15:46 ` Herman
2003-10-12 17:44 ` Mark E. Donaldson
2003-10-12 18:18 ` Herman
2003-10-12 20:11 ` Port forwarding doesn't work Herman
2003-10-12 21:41 ` Gerd Zemella
2003-10-12 22:04 ` Herman
2003-10-12 23:00 ` Herman
2003-10-13 0:10 ` Philip Craig
2003-10-13 0:20 ` Herman
2003-10-13 0:40 ` Herman
2003-10-13 1:17 ` Arnt Karlsen
2003-10-13 13:06 ` Robert P. J. Day
2003-10-13 19:11 ` Arnt Karlsen
2003-10-13 18:05 ` Herman
2003-10-13 19:31 ` Jeffrey Laramie
2003-10-13 20:00 ` Jeffrey Laramie
2003-10-13 20:09 ` Arnt Karlsen
2003-10-13 20:47 ` Herman
2003-10-13 0:44 ` Chris Brenton
2003-10-13 1:17 ` Herman
2003-10-13 1:30 ` Herman
2003-10-13 1:52 ` Port forwarding now *almost* works Herman
2003-10-13 7:13 ` Port forwarding doesn't work Gerd Zemella
2003-10-13 14:32 ` Adam D. Barratt
2003-10-13 15:02 ` Gerd Zemella
2003-10-14 6:04 ` Invalid friggen argument Joel Newkirk
2003-10-14 13:14 ` Herman [this message]
[not found] <LFEHKEBEBHAFGJBMNKAOIELHCCAA.markee@bandwidthco.com>
2003-10-13 1:22 ` Herman
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=200310140714.47291.Herman@AerospaceSoftware.com \
--to=herman@aerospacesoftware.com \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.