From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@lists.netfilter.org
Subject: Re: missing module for tcp-flags match?
Date: Fri, 22 Sep 2006 16:45:41 +0200 [thread overview]
Message-ID: <4513F715.4090509@plouf.fr.eu.org> (raw)
In-Reply-To: <5bb00b3f0609220655n7a888c4bt4d1ed714f5193545@mail.gmail.com>
Hello,
Henning Sprang a écrit :
> Sorry for having posted this message twice. I did't see it coming back
> through the list, and realized I sent it from the wrong address.
Messages sent with an address which is not subscribed to the list must
wait to be approved by a list manager, this can take some time.
> I then sent it again from the address whic is actually subscribed.
> Now that I wondered why even the second mail didn't come back to me, I
> looked in the list archive and saw that the mail actually came through
> the list, even twice. I wonder why I didn't get a copy, because all
> other lists I know send copies of mails also to the sender himself -
> is the netfilter list different in this?
There is an option to not receive a copy of your own messages, maybe you
enabled it.
> When tyring to set up the rule:
>
> iptables -A INPUT --protocol tcp --tcp-flags ALL SYN,ACK -j DROP
>
> I only get the error:
>
> iptables: No chain/target/match by that name
>
> When I remove the tcp-flags part, the rules is accepted. I assume to
> be missing a kernel module for tcp-flags match, but have no idea which
> module this could be. Which Kernel module is required for getting
> tcp-flags matches?
AFAIK, there is no specific module for --tcp-flags. It is a standard tcp
match, like --dport and --sport. I see no reason why you get an error.
next prev parent reply other threads:[~2006-09-22 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 23:54 missing module for tcp-flags match? Henning Sprang
2006-09-21 7:13 ` Henning Sprang
2006-09-22 13:55 ` Henning Sprang
2006-09-22 14:45 ` Pascal Hambourg [this message]
2006-09-22 20:03 ` Henning Sprang
2006-09-22 16:36 ` Mike Wright
2006-09-22 19:07 ` Jan Engelhardt
2006-09-22 19:22 ` Mike Wright
2006-09-22 19:50 ` Henning Sprang
2006-09-22 21:04 ` Mike Wright
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=4513F715.4090509@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.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 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.