From: Shawn <core@enodev.com>
To: Harald Welte <laforge@netfilter.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: iptables & 2.5 problem
Date: 04 Jun 2003 13:22:00 -0500 [thread overview]
Message-ID: <1054750920.6370.10.camel@localhost> (raw)
In-Reply-To: <20030604180726.GG29818@sunbeam.de.gnumonks.org>
This would be great, except for iptables does not build against
linux-2.5.70-mm3 due to lack of IPT_PHYSDEV_OP_MATCH_IN and
IPT_PHYSDEV_OP_MATCH_OUT.
For that matter, there is no IPT_PHYSDEV_OP_MATCH* at all in the kernel
source.
On Wed, 2003-06-04 at 13:07, Harald Welte wrote:
> On Wed, Jun 04, 2003 at 12:26:38PM -0500, Shawn wrote:
> > 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.
next prev parent reply other threads:[~2003-06-04 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 17:26 iptables & 2.5 problem Shawn
2003-06-04 18:07 ` Harald Welte
2003-06-04 18:22 ` Shawn [this message]
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=1054750920.6370.10.camel@localhost \
--to=core@enodev.com \
--cc=laforge@netfilter.org \
--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 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.