From: Patrick McHardy <kaber@trash.net>
To: Marcus Sundberg <marcus@ingate.com>
Cc: Harald Welte <laforge@netfilter.org>,
netfilter-devel@lists.netfilter.org
Subject: Re: ctnetlink unique id size?
Date: Sun, 20 Feb 2005 05:47:26 +0100 [thread overview]
Message-ID: <4218165E.1060300@trash.net> (raw)
In-Reply-To: <4214D75D.5070005@ingate.com>
Marcus Sundberg wrote:
> Hi,
>
> isn't an unsigned int a bit (or rather about 32 bits) small for
> keeping the id field of the ip_conntrack struct? It's bound to wrap
> around, and with things like long-lived ssh sessions it's even
> possible for two connections to be assigned the same id after a
> wrap-around.
>
> Am I missing something obvious when I think ctnetlink_dump_table()
> will break down when the wrap-around occurs?
>
> Using an uint64_t would on the other hand guarantee that each
> connection really get a unique id.
We had a long discussion about this an the result was that it has to
be 64 bit. Search the archives if you are interested, the subject
is "ctnetlink questions". I'm surprised too that it now is 32 bit.
Maybe Harald knows the reason.
Regards
Patrick
next prev parent reply other threads:[~2005-02-20 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 17:41 ctnetlink unique id size? Marcus Sundberg
2005-02-20 4:47 ` Patrick McHardy [this message]
2005-02-20 12:28 ` 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=4218165E.1060300@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=marcus@ingate.com \
--cc=netfilter-devel@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 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.