Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: wang feng <feng.wangs@gmail.com>, netfilter-devel@vger.kernel.org
Subject: Re: wrong result with conntrack_create, expect_create
Date: Tue, 15 Jul 2008 12:33:39 +0200	[thread overview]
Message-ID: <487C7D03.30003@netfilter.org> (raw)
In-Reply-To: <487C7AB2.3050800@trash.net>

Patrick McHardy wrote:
> Pablo Neira Ayuso wrote:
>> wang feng wrote:
>>> Hello,
>>> I have done some test based on the
>>> libnetfilter_conntrack-0.0.96,something is
>>> wrong with the samples under utils:
>>>
>>> conntrack_create:
>>>  TEST: create conntrack (0)(Success)
>>> it should create a conntrack with src:1.1.1.1, dst:2.2.2.2
>>> but: conntrack_get:
>>> ipv4     2 tcp      6 98 src=0.0.0.0 dst=0.0.0.0 sport=0 dport=0
>>> packets=0
>>> bytes=0 [UNREPLIED] src=0.0.0.0 dst=0.0.0.0 sport=0 dport=0 packets=0
>>> bytes=0
>>> mark=0 use=2
>>>
>>> expect_create:
>>> TEST: add master conntrack (0)(Success)
>>> TEST: create expectation (-1)(Invalid argument)
>>
>> You probably forgot to insmod:
>>
>> * nf_conntrack_ipv4
>> * nf_conntrack_ftp, which is required to run the expect_create test.
>>
>> I'm going to add a note in the sources of the test now.
> 
> Ideally we would simply autoload the modules on create requests.
> That would also be a first step to fix the NAT dependencies.

I'll include that in my next patchset.

-- 
"Los honestos son inadaptados sociales" -- Les Luthiers

      reply	other threads:[~2008-07-15 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15  8:29 wrong result with conntrack_create, expect_create wang feng
2008-07-15 10:18 ` Pablo Neira Ayuso
2008-07-15 10:23   ` Patrick McHardy
2008-07-15 10:33     ` Pablo Neira Ayuso [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=487C7D03.30003@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=feng.wangs@gmail.com \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@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