From: Eric Leblond <eric@regit.org>
To: xavier <list.netfilter@natch.dyndns.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: tcp & udp timeout hardcoding
Date: Mon, 17 Nov 2003 17:30:33 +0100 [thread overview]
Message-ID: <1069086632.2640.3.camel@tech004.alphalink.fr> (raw)
In-Reply-To: <20031117144208.GA22431@nest.8d.com>
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
Le lun 17/11/2003 à 15:42, xavier a écrit :
> Hello,
>
> I saw in the 2.4.22 kernel source :
>
> /usr/src/linux/net/ipv4/netfilter/ip_conntrack_proto_tcp.c
> Is there any plan to be able to set thoses values throught /proc ?
It is already available in P-O-M :
http://www.netfilter.org/documentation/pomlist/pom-combined.html#tcp-window-tracking
BR,
--
Eric Leblond
NuFW, Now User Filtering Works (http://www.nufw.org)
[-- Attachment #2: Ceci est une partie de message numériquement signée. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-11-17 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 14:42 tcp & udp timeout hardcoding xavier
2003-11-17 16:30 ` Antony Stone
2003-11-17 18:09 ` Ramin Dousti
2003-11-17 17:27 ` Antony Stone
2003-11-17 16:30 ` Eric Leblond [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=1069086632.2640.3.camel@tech004.alphalink.fr \
--to=eric@regit.org \
--cc=list.netfilter@natch.dyndns.org \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox