From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Leblond <eric@inl.fr>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [ULOGD PATCH 1/4] Fix SQL field naming.
Date: Wed, 09 Apr 2008 15:46:32 +0200 [thread overview]
Message-ID: <47FCC8B8.1010104@netfilter.org> (raw)
In-Reply-To: <46021.62.160.220.138.1207748382.squirrel@mail.inl.fr>
Eric Leblond wrote:
> Hi,
>
>> Eric Leblond wrote:
>>> diff --git a/doc/mysql-ulogd2.sql b/doc/mysql-ulogd2.sql
>>> index 304173b..6368dc7 100644
>>> --- a/doc/mysql-ulogd2.sql
>>> +++ b/doc/mysql-ulogd2.sql
>>> @@ -297,8 +297,8 @@ DROP VIEW IF EXISTS `conntrack`;
>>> CREATE SQL SECURITY INVOKER VIEW `conntrack` AS
>>> SELECT _ct_id,
>>> oob_family,
>>> - orig_ip_saddr AS orig_ip_saddr_raw,
>>> - orig_ip_daddr AS orig_ip_daddr_raw,
>>> + orig_ip_saddr AS orig_ip_saddr_bin,
>>> + orig_ip_daddr AS orig_ip_daddr_bin,
>>> orig_ip_protocol,
>>> orig_l4_sport,
>>> orig_l4_dport,
>> What do we gain with this renaming?
>
> This fix an inconsistency of field naming among the different tables and
> accross the stack NFCT IP2BIN MYSQL.In fact IP2BIN out .bin suffixed
> fields.
Makes sense. Applied. Thanks Eric.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
next prev parent reply other threads:[~2008-04-09 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 23:09 [ULOGD PATCH 0/4] Eric Leblond
2008-03-31 23:09 ` [ULOGD PATCH 1/4] Fix SQL field naming Eric Leblond
2008-04-09 13:28 ` Pablo Neira Ayuso
2008-04-09 13:39 ` Eric Leblond
2008-04-09 13:46 ` Pablo Neira Ayuso [this message]
2008-03-31 23:09 ` [ULOGD PATCH 2/4] Convert SQL procedure to function in MySQL plugins Eric Leblond
2008-04-09 13:36 ` Pablo Neira Ayuso
[not found] ` <47FCC654.7080900@netfilter.org>
2008-04-09 16:29 ` Eric Leblond
2008-03-31 23:09 ` [ULOGD PATCH 3/4] IPv6 compliance of NACCT output plugin Eric Leblond
2008-04-09 13:46 ` Pablo Neira Ayuso
2008-03-31 23:09 ` [ULOGD PATCH 4/4] Add some example to ulogd.conf.in Eric Leblond
2008-04-09 13:49 ` Pablo Neira Ayuso
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=47FCC8B8.1010104@netfilter.org \
--to=pablo@netfilter.org \
--cc=eric@inl.fr \
--cc=netfilter-devel@vger.kernel.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