All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Cc: Harald Welte <laforge@netfilter.org>, Patrick McHardy <kaber@trash.net>
Subject: [PATCH 0/3] change TCP protoinfo via netlink
Date: Thu, 25 Aug 2005 22:42:28 +0200	[thread overview]
Message-ID: <430E2D34.3030704@eurodev.net> (raw)

Taken from [1]:

I think that users must be able to set the TCP state of a conntrack,
otherwise if they create a conntrack via libnfnetlink_conntrack, the
state will be set to NONE. If users aren't able to set the state, I'd
consider that the library is kind of incomplete. I don't like the idea
of kidding with stuff that could be compromising either, but I don't
want to lose any features. So, I think that the solution is *remark* in
the documentation of libnfnetlink_conntrack and the conntrack manpage
that changing the protocol private information like the state could
result in problems, I'll to do such thing.

[1]https://lists.netfilter.org/pipermail/netfilter-devel/2005-August/020784.html

@Harald: I've reworked the patches as you suggested.

--
Pablo

                 reply	other threads:[~2005-08-25 20:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=430E2D34.3030704@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --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.