From: Patrick McHardy <kaber@trash.net>
To: Jonas Berlin <jberlin@niksula.hut.fi>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: iptables compile error: NFC_IP_TOS undeclared
Date: Thu, 10 Feb 2005 18:50:08 +0100 [thread overview]
Message-ID: <420B9ED0.1020303@trash.net> (raw)
In-Reply-To: <420B8623.9050308@niksula.hut.fi>
Jonas Berlin wrote:
> Alexander Piavka wrote:
>
>>
>> actually there is no match from NFC_IP_TOS in the whole
>> /usr/src/linux-2.6.10-ct_sync-rc1/include subtree
>>
>>
> Ok, I'm not that familiar with different kernel versions, but my
> 2.6.10 at least has that one. Could it be that the ct_sync patch takes
> it away? Do you have ct_sync as a patch or did you get the kernel
> pre-patched?
Yes, it reuses the bits to record state changes. The nfcache bits
don't affect any functionality, just define it to anything you want
or remove it.
Regards
Patrick
next prev parent reply other threads:[~2005-02-10 17:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 7:50 netfilter & ipv6 Jonas Berlin
2005-02-10 14:07 ` Jonas Berlin
2005-02-10 14:41 ` Samuel Jean
2005-02-10 15:10 ` iptables compile error: NFC_IP_TOS undeclared Alexander Piavka
2005-02-10 15:18 ` Jonas Berlin
2005-02-10 16:00 ` Alexander Piavka
2005-02-10 16:04 ` Jonas Berlin
2005-02-10 17:50 ` Patrick McHardy [this message]
2005-02-10 23:16 ` [PATCH] kill NFC_* stuff in iptables [was Re: iptables compile error: NFC_IP_TOS undeclared] Pablo Neira
2005-02-11 19:07 ` Patrick McHardy
2005-02-11 21:47 ` Pablo Neira
2005-02-12 1:32 ` Patrick McHardy
2005-02-12 22:25 ` Pablo Neira
2005-02-12 23:34 ` Patrick McHardy
2005-02-10 17:20 ` netfilter & ipv6 Jonas Berlin
2005-02-10 21:36 ` Sven-Haegar Koch
2005-02-15 1:29 ` Jonas Berlin
[not found] ` <53965.213.236.112.75.1107867276.squirrel@213.236.112.75>
2005-02-10 23:15 ` ULOG target for ipv6 Jonas Berlin
2005-02-11 22:10 ` netfilter question Pedro Fortuna
2005-02-14 23:25 ` ULOG target for ipv6 Harald Welte
2005-02-15 0:11 ` Jonas Berlin
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=420B9ED0.1020303@trash.net \
--to=kaber@trash.net \
--cc=jberlin@niksula.hut.fi \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).