All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Eric Leblond <eric@inl.fr>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	nufw-devel@nongnu.org
Subject: Re: [PATCH 2/3] [libnetfilter_conntrack] fixed duration connection
Date: Sat, 08 Apr 2006 21:58:58 +0200	[thread overview]
Message-ID: <44381602.5090105@trash.net> (raw)
In-Reply-To: <4436E0B6.9040602@inl.fr>

Eric Leblond wrote:
> Hi,
> 
> This patch add support for the IPS_FIXED_TIMEOUT state.
> 
> BR,
> --
> Regit
> 
> 
> ------------------------------------------------------------------------
> 
> Index: include/libnetfilter_conntrack/linux_nfnetlink_conntrack.h
> ===================================================================
> --- include/libnetfilter_conntrack/linux_nfnetlink_conntrack.h	(révision 6576)
> +++ include/libnetfilter_conntrack/linux_nfnetlink_conntrack.h	(copie de travail)
> @@ -29,6 +29,7 @@
>  	CTA_HELP,
>  	CTA_NAT,
>  	CTA_TIMEOUT,
> +	CTA_FIXED_TIMEOUT,
>  	CTA_MARK,
>  	CTA_COUNTERS_ORIG,
>  	CTA_COUNTERS_REPLY,

I didn't see the patch adding support for this in the kernel. Since
there is no seperate fixed timeout anymore, this also looks obsolete.
The way I understood the kernel patch, you would just do two netlink
operations:

- set flag FIXED_TIMEOUT
- change timeout using CTA_TIMEOUT

Am I missing something?

  reply	other threads:[~2006-04-08 19:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04  8:33 [PATCH 0/3] [RFC] fixed duration connection Eric Leblond
2006-04-04  8:36 ` [PATCH 1/3] " Eric Leblond
2006-04-04  8:38 ` [PATCH 2/3] " Eric Leblond
2006-04-04  8:41 ` [PATCH 3/3] [RFC] " Eric Leblond
2006-04-04  8:43 ` [PATCH 2/3] " Eric Leblond
2006-04-04  8:43 ` [PATCH 3/3] [RFC] " Eric Leblond
2006-04-05 13:57 ` [PATCH 0/3] " Patrick McHardy
2006-04-05 14:41   ` Eric Leblond
2006-04-07 21:53   ` Eric Leblond
2006-04-07 21:57     ` [PATCH 1/3] [kernel patch] " Eric Leblond
2006-04-08 19:56       ` Patrick McHardy
2006-04-08 20:55         ` Eric Leblond
2006-04-11 16:22           ` Patrick McHardy
2006-04-11 20:20             ` Eric Leblond
2006-04-12  8:38         ` Harald Welte
2006-04-12 10:48           ` Harald Welte
2006-04-12 19:06             ` Patrick McHardy
2006-04-13 16:17               ` Eric Leblond
2006-04-21  2:30                 ` Patrick McHardy
2006-04-21 20:53                   ` Eric Leblond
2006-04-22  0:02                     ` Patrick McHardy
2006-04-07 21:59     ` [PATCH 2/3] [libnetfilter_conntrack] " Eric Leblond
2006-04-08 19:58       ` Patrick McHardy [this message]
2006-04-08 20:23         ` Eric Leblond
2006-04-07 22:01     ` [PATCH 0/3] [conntrack] " Eric Leblond
2006-04-07 22:08       ` [PATCH 3/3] " Eric Leblond

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=44381602.5090105@trash.net \
    --to=kaber@trash.net \
    --cc=eric@inl.fr \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=nufw-devel@nongnu.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.