Linux Netfilter development
 help / color / mirror / Atom feed
From: Bryan Duff <bduff@ecessa.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: operation failure on delete
Date: Wed, 04 Mar 2009 13:01:14 -0600	[thread overview]
Message-ID: <49AECFFA.6030401@astrocorp.com> (raw)
In-Reply-To: <49AEC4A8.7020000@netfilter.org>

Thanks, the patch works.

Adding esp would be superfantabulous as well.

-Bryan

Pablo Neira Ayuso wrote:
> Bryan Duff wrote:
>   
>> //snip - conntrack search and attempted delete.
>> root@localhost / # conntrack -L -p gre  unknown  47 27 src=60.60.60.151
>> dst=192.168.2.2 packets=6 bytes=648 [UNREPLIED] src=10.10.10.100
>> dst=60.60.60.151 packets=0 bytes=0 mark=2 use=1
>> conntrack v0.9.11 (conntrack-tools): 1 flow entries has been shown.
>> root@localhost / # conntrack -D -p gre
>> conntrack v0.9.11 (conntrack-tools): Operation failed: invalid parameters
>> //end snip
>>
>> But I can delete tcp, udp, icmp conntrack entries.  I can only guess
>> that there is a problem with "unknown" protocols like gre (haven't
>> checked on esp, and so forth).  Using the protocol number (in this case
>> 47) also fails.
>>     
>
> No, it seems that the problem is that libnetfilter_conntrack-0.0.99 does
> not include support for GRE yet.
>
>   
>> I'm using  libnfnetlink-0.0.40 and libnetfilter_conntrack-0.0.99
>>
>> Kernel version 2.6.29-rc7.  The conntrack version is that released on
>> the website (md5sum: ae97d335ad44e9611adde881490c8ec9).
>>     
>
> The following patch should add it, it compiles, I didn't tested though.
> I'd appreciate if you call tell me how it goes with it.
>
>   


  reply	other threads:[~2009-03-04 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 16:16 operation failure on delete Bryan Duff
2009-03-04 18:12 ` Pablo Neira Ayuso
2009-03-04 19:01   ` Bryan Duff [this message]
2009-03-05 12:19     ` Pablo Neira Ayuso

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=49AECFFA.6030401@astrocorp.com \
    --to=bduff@ecessa.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@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