From: Shawn <core@enodev.com>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Harald Welte <laforge@netfilter.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: iptables & 2.5 problem
Date: 04 Jun 2003 13:31:52 -0500 [thread overview]
Message-ID: <1054751512.6371.21.camel@localhost> (raw)
In-Reply-To: <1054751234.692.75.camel@tux.rsn.bth.se>
Awesome, thanks.
On Wed, 2003-06-04 at 13:27, Martin Josefsson wrote:
> On Wed, 2003-06-04 at 20:22, Shawn wrote:
> > 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.
>
> Use development iptables for a development kernel.
>
> See http://netfilter.org/downloads.html#cvs
prev parent reply other threads:[~2003-06-04 18:18 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
2003-06-04 18:27 ` Martin Josefsson
2003-06-04 18:31 ` Shawn [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=1054751512.6371.21.camel@localhost \
--to=core@enodev.com \
--cc=gandalf@wlug.westbo.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox