mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Shawn <core@enodev.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: iptables & 2.5 problem
Date: Wed, 4 Jun 2003 20:07:26 +0200	[thread overview]
Message-ID: <20030604180726.GG29818@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <1054747598.12295.5.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]

On Wed, Jun 04, 2003 at 12:26:38PM -0500, Shawn wrote:
> I really don't know how to track this problem to its source, so I was
> hoping someone could enlighten me.

Since this seems to be an iptables usage problem, please direct further
questions to netfilter@lists.netfilter.org (see 
http://www.netfilter.org/contact.html for more info)

> The problem illustrated here:
> # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
> iptables: Invalid argument
> 
> This box is a gentoo running iptables-1.2.8-r1 and linux-2.5.70-mm3.
> Config attached.

This sounds like your iptables userspace command was compiled for a
kernel with different headers.  Please rebuild iptables and make sure it
actually uses the headers of your 2.5.70-mm3 kernel.

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-04 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 17:26 Shawn
2003-06-04 18:07 ` Harald Welte [this message]
2003-06-04 18:22   ` Shawn
2003-06-04 18:27     ` Martin Josefsson
2003-06-04 18:31       ` Shawn

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=20030604180726.GG29818@sunbeam.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=core@enodev.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®