Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ted Kaczmarek <tedkaz@optonline.net>
To: Cedric Blancher <blancher@cartel-securite.fr>
Cc: Goetz Bock <netfilter@blacknet.de>,
	netfilter <netfilter@lists.netfilter.org>
Subject: Re: conntrack for samba/netbios-ns
Date: Wed, 05 Nov 2003 07:30:58 -0500	[thread overview]
Message-ID: <1068035458.14617.13.camel@tarkus> (raw)
In-Reply-To: <1068017027.807.15.camel@elendil.intranet.cartel-securite.net>

Ah, just like the Checkpoint implementation.
So their is still no state tracking per say, but a hash table
based on SA/port DA/port, and a 180 second timer.

Doesn't 180 seconds seem a tad long?
I kinda vaguely remember Checkpoint default on this being 40 seconds.

I remember being in a discussion with some developers on this and the
consensus was 30 second heartbeats ( strange, they almost always end up
with 30 second heartbeats for everything, hehe ).

Could the developers enlighten me as to why they ended up with 180?
Not a big deal, but it never hurts to learn something :-)

Thanks,
Ted

PS By the way your tutorials are great.

On Wed, 2003-11-05 at 02:23, Cedric Blancher wrote:
> Le mer 05/11/2003 à 03:30, Ted Kaczmarek a écrit :
> > udp is connectionless, not sure where you can get a state on it.
> 
> Connection <> state
> 
> State tracking applies to UDP and is based on timers. See Iptables
> Tutorial for UDP state tracking :
> 
> http://iptables-tutorial.frozentux.net/chunkyhtml/udpconnections.html




  reply	other threads:[~2003-11-05 12:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05  0:34 conntrack for samba/netbios-ns Goetz Bock
2003-11-05  2:30 ` Ted Kaczmarek
2003-11-05  2:58   ` Goetz Bock
2003-11-05  7:23   ` Cedric Blancher
2003-11-05 12:30     ` Ted Kaczmarek [this message]
2003-11-05 13:04       ` Cedric Blancher
2003-11-05 13:05       ` Chris Brenton
2003-11-07 16:48 ` Harald Welte

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=1068035458.14617.13.camel@tarkus \
    --to=tedkaz@optonline.net \
    --cc=blancher@cartel-securite.fr \
    --cc=netfilter@blacknet.de \
    --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