Skip to content

RFC fixed duration connection

Eric Leblond netfilter-devel 1 version Applied

Status from this message: Applied, thanks. Both your patches had whitespace damage I

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest3 patches 20 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/3fixed duration connectioninclude/linux/netfilter/nfnetlink_conntrack.h include/linux/netfilter_ipv4/ip_conntrack.h include/net/netfilter/nf_conntrack.h +6 more+174 -70 replies
2/3fixed duration connectionlibnetfilter_conntrack.c libnetfilter_conntrack/libnetfilter_conntrack.h libnetfilter_conntrack/linux_nfnetlink_conntrack.h+37 -60 replies
3/3fixed duration connectionconntrack.c conntrack.h+27 -120 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] [RFC] fixed duration connection

Hi,

While working on NuFW development branch, we have had to implement policy just as :
* connection to server is authorised from 08h to 18h and connection must be switched off at 18h.

Such features are frequently asked by customers or netfilter addicts but even with current conntrack related code, it can not be done cleanly.

Thus, we've added the notion of fixed duration before expiration to connection in the conntrack. (See extended information on bottom for details)

The following set of patches is against kernel (linus git tree), libnetfilter_conntrack, and conntrack tool.

-- Extended --

When trying to implement this feature with current connection tracking code, we have faced some issues :
1. userspace code has to duplicate conntrack entries, thus it's complex and uses memory
2. there is no hope to have it done by a simple command line (because of 1.)
3. if replication of conntrack in userspace is needed there will be many synchronisation problems : stop and start of an hypothetical "expiration" daemon would cause conntrack duplication and/or loss of information ...

For this reason, we've worked on a simple kernel level implementation. This is done via a second "struct timer" that is added in connection structure. Activation of the timer, is for now done via userspace by using libnetfilter_conntrack or by using new option -T of the conntrack tool.

This kernel implementation could easily lead to a new iptables target in the future.

This is a resend of patch :
http://patchwork.netfilter.org/netfilter-devel/patch.pl?id=3289
It adds support for nf_conntrack.

Best regards,
--
Eric Leblond <[email protected]> for the NuFW Core Team NuFW : http://www.nufw.org/