From: steve@perfectpc.co.nz
To: Phil Oester <kernel@linuxace.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: iptable_nat: Unknown symbol need_ip_conntrack
Date: Tue, 4 Jan 2005 08:38:22 +1300 (NZDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0501040830080.1409@localhost> (raw)
In-Reply-To: <20050103050001.GA12500@linuxace.com>
>> Kernel 2.6.10-ac2 . Apart from this, the system appears to be normal;
>
> Looks like a problem with your configuration/kernel build...I have no
> such problems here on 2.6.10.
Me too, on the other two machine doesn't have ; only the firewall box has. It seems
to be related to iproute2 or MARK target? as only the firewall box uses
iptables to mark packets and then use iproute2 to route it.
I am pretty sure the config and kernel build are correct.
I will try to find out how to reproduce the problem with the other two machine I have here
prev parent reply other threads:[~2005-01-03 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 3:52 iptable_nat: Unknown symbol need_ip_conntrack steve
2005-01-03 5:00 ` Phil Oester
2005-01-03 19:38 ` steve [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=Pine.LNX.4.60.0501040830080.1409@localhost \
--to=steve@perfectpc.co.nz \
--cc=kernel@linuxace.com \
--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