From: Harald Welte <laforge@netfilter.org>
To: Hubert Tonneau <hubert.tonneau@fullpliant.org>
Cc: linux-kernel@vger.kernel.org, netfilter@lists.netfilter.org
Subject: Re: failed to configure iptables with 2.6.16 kernel
Date: Tue, 28 Mar 2006 10:09:26 +0200 [thread overview]
Message-ID: <20060328080925.GE28782@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <064FKGY12@briare1.heliogroup.fr>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
On Tue, Mar 28, 2006 at 04:00:33AM +0000, Hubert Tonneau wrote:
> When upgrading from 2.6.15 to 2.6.16 I noticed iptables not working anymore.
>
> I traced the problem down to a new 'CONFIG_NETFILTER_XTABLES' compile option
> that must be set, but I still get some rules rejected as soon as
> '--destination-port' option is used.
>
> As an example, the following command:
> iptables -A eth0in -p udp --destination-port 111 -j DROP
this sounds like you're missing support for the tcp/udp match.
This functionality is implemented in xt_tcpudp.{c,ko}, which is compiled
as soon as x_tables is compiled.
What does cat /proc/netip_tables_matches show before and after executing
your iptables command, and before/after manually executing modprobe
xt_tcpudp.
Also, what is your iptables program version?
Please follow-up-to netfilter@lists.netfilter.org, but keep me in Cc
--
- Harald Welte <laforge@netfilter.org> http://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: 191 bytes --]
next prev parent reply other threads:[~2006-03-28 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 4:00 Hubert Tonneau
2006-03-28 8:09 ` Harald Welte [this message]
2006-03-28 13:10 Hubert Tonneau
2006-03-28 10:23 ` Harald Welte
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=20060328080925.GE28782@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=hubert.tonneau@fullpliant.org \
--cc=linux-kernel@vger.kernel.org \
--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 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®