From mboxrd@z Thu Jan 1 00:00:00 1970 From: Filip Sneppe Subject: Re: trouble with expect_related Date: 07 Jan 2003 10:50:02 +0100 Sender: netfilter-devel-admin@lists.netfilter.org Message-ID: <1041933003.502.23.camel@xbox> References: <1041651291.1637.41.camel@exile> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: netfilter-devel@lists.netfilter.org Return-path: To: Rich Wellner In-Reply-To: Errors-To: netfilter-devel-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: netfilter-devel.vger.kernel.org On Mon, 2003-01-06 at 16:58, Rich Wellner wrote: > "Filip Sneppe (Cronos)" writes: > > > However, the oldnat stuff you based your conntracker > > on should be able to add your expectations without > > any problems, so your problem will probably not get > > solved by moving to the newnat API. > > Right, makes sense. I can't see what's wrong with my code, seems like it > should just work. Unfortunately, switching kernel isn't an option, I have to > support the 2.4 series with my module, not just the most current stuff. No problem. > Can anyone else comment? > Do you see the expected connection in /proc/net/ip_conntrack? It should be preceded by "EXPECTING:" if it hasn't seen any traffic yet. Regards, Filip