From: Emmanuel Guiton <emmanuel@netlab.hut.fi>
Cc: netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: Side effect? - Re: Changing the content of tcp timeouts in ip_conntrack_proto_tcp.c
Date: Thu, 15 Jan 2004 16:19:08 +0200 [thread overview]
Message-ID: <4006A15C.7090908@netlab.hut.fi> (raw)
In-Reply-To: 1074172485.1305.21.camel@nienna.balabit
KOVACS Krisztian wrote:
> Are you sure iptable_nat is loaded in the kernel? And what does your
>kernel log say?
>
>
>
Well, as far as I've modified my sources I can't reproduce the error
immediately. But a good guess would be that the module was not loaded
and more specifically the problem may simply occured in the ip_conntrack
module, thus avoiding iptable_nat to work.
But the problem is now solved. I have not changed anything except the
name of my function which is much shorter than my original one. Now it's
working, even the execution produces the result I was expecting. Isn't
there a specific bound on the function's name? The first name I used was
44 characters long (it was in fact a longer version of the one I
indicated in my previous mail).
Tanks for your help anyway.
Emmanuel
next prev parent reply other threads:[~2004-01-15 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 10:34 Changing the content of tcp timeouts in ip_conntrack_proto_tcp.c Emmanuel Guiton
2004-01-14 11:11 ` Henrik Nordstrom
2004-01-14 12:39 ` Emmanuel Guiton
2004-01-14 12:50 ` KOVACS Krisztian
2004-01-14 13:23 ` Emmanuel Guiton
2004-01-15 8:26 ` Side effect? - " Emmanuel Guiton
2004-01-15 13:14 ` KOVACS Krisztian
2004-01-15 13:32 ` Userspace msg, hw_addr unused? Scott MacKay
2004-01-15 14:00 ` Scott MacKay
2004-01-15 14:19 ` Emmanuel Guiton [this message]
2004-01-15 14:29 ` Last minute erratum: I'm stupid. - Re: Side effect? - Re: Changing the content of tcp timeouts Emmanuel Guiton
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=4006A15C.7090908@netlab.hut.fi \
--to=emmanuel@netlab.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 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.