gmane.network.nmsg.devel

rsf-freebsd-ports 0.3 released

Robert Edmonds — 2013-04-30T00:54:12

http://rsfcode.isc.org/dist/rsf-freebsd-ports/rsf-freebsd-ports-0.3.tar.gz

http://rsfcode.isc.org/git/rsf-freebsd-ports/

this release updates the freebsd port for 'nmsg' to 0.7.3.

nmsg 0.7.3 released

Robert Edmonds — 2013-04-30T00:53:03

http://rsfcode.isc.org/dist/nmsg/nmsg-0.7.3.tar.gz

nmsg (0.7.3)

  * The rate-limiting function nmsg_rate_sleep() has been completely
    rewritten in order to sleep much more often and with shorter timeouts.
    At low to moderate event rates, nmsg_rate_sleep() will now result in a
    system-level sleep at almost every invocation.

  * If nmsg_output_set_rate() is used to attach an nmsg_rate_t object to an
    nmsg_output_t object, nmsg_output_close() will now no longer implicitly
    call nmsg_rate_destroy() on the associated nmsg_rate_t object.
    Additionally, internal calls to nmsg_rate_sleep() will now be performed
    while holding the stream output lock. These changes allow library users
    to share an nmsg_rate_t object across more than one output.

  * Rate-limiting in nmsg_output is now performed on a per-packet rather
    than on a per-payload basis.

  * If using rate-limiting on output sockets, nmsgtool will default to a
    "freq" setting of 10 rather than the previous value of 100.

  * I

rsf-freebsd-ports 0.2 released

Robert Edmonds — 2013-03-15T21:47:41

http://rsfcode.isc.org/dist/rsf-freebsd-ports/rsf-freebsd-ports-0.2.tar.gz

http://rsfcode.isc.org/git/rsf-freebsd-ports/

this release updates the freebsd port for 'nmsg' to 0.7.2.

sie-dns-sensor 0.7.2-1 released

Robert Edmonds — 2013-03-15T21:44:12

http://rsfcode.isc.org/dist/sie-dns-sensor/0.7.2-1/

https://kb.isc.org/article/AA-00535

this release is built against the latest nmsg 0.7.2 release, though
without libxs support, which is not needed for the SIE DNS sensor.  i've
also re-built the build environments that we use to compile the rpm and
deb packages for sie-dns-sensor.

the debian packages for sie-dns-sensor are now built on debian 6.0
"stable" (previously they were being built on debian 5.0 "oldstable").
support for "oldstable" has now been dropped, as this OS has been EOL'd
by the vendor.  (this allows us to avoid including a copy of libbind in
sie-dns-sensor on debian platforms now.)

the RPM packages for sie-dns-sensor are now built on centos 5 and 6.
previously we were also building on centos 4, but the centos 4 and RHEL 4
operating systems have since been EOL'd by their vendors.

nmsg 0.7.2 released

Robert Edmonds — 2013-03-15T21:23:19

http://rsfcode.isc.org/dist/nmsg/nmsg-0.7.2.tar.gz

nmsg (0.7.2)

  * Fix a segfault in nmsgtool when -U (--username) was specified on the
    command line without -P (--pidfile).

  * nmsg can now be built without libxs support by specifying
    "--without-libxs" to configure.

  * Build system: the directory to install the libnmsg pkg-config file to can
    now be overridden by specifying the --with-pkgconfigdir parameter to
    configure.

  * Build system: add "make check" target that runs tests.

  * Build fix: explicitly link examples/nmsg-dnsqr2pcap against libpcap.

  * Portability: use fallback htole32()/le32toh() functions on old systems.

 -- Robert Edmonds <edmonds< at >isc.org>  Tue, 12 Mar 2013 17:33:22 -0400

Re: pywdns and dnsdedupe

Robert Edmonds — 2013-01-22T20:25:05

    Python 2.7.3 (default, Sep  9 2012, 17:41:34) 
    [GCC 4.7.1] on linux2
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import wdns
    >>> rdata_bytes = '\x7f\x00\x00\x01'
    >>> rrtype = 1
    >>> repr(wdns.rdata(rdata_bytes, wdns.CLASS_IN, rrtype))
    '127.0.0.1'
    >>>

pywdns and dnsdedupe

Mert Kara — 2013-01-22T20:16:39

What would be the best way to parse rdata field in the presentation format of rrtype?

Thanks,

MK


_______________________________________________
nmsg-dev mailing list
nmsg-dev< at >lists.isc.org
https://lists.isc.org/mailman/listinfo/nmsg-dev

pywdns and dnsdedupe

Mert Kara — 2013-01-22T20:18:36

What would be the best way to parse rdata field in the presentation format of rrtype?

Thanks,

MK


_______________________________________________
nmsg-dev mailing list
nmsg-dev< at >lists.isc.org
https://lists.isc.org/mailman/listinfo/nmsg-dev

Re: nmsg msgmod version mismatch error

Dan Brodsky — 2012-11-14T17:46:25

Running ldconfig and passing it the directory libnmsg was in (/usr/local/lib) fixed the problem. Thank you, I would not have thought to do that.


On Wednesday, November 14, 2012 at 11:56 AM, Robert Edmonds wrote:



_______________________________________________
nmsg-dev mailing list
nmsg-dev< at >lists.isc.org
https://lists.isc.org/mailman/listinfo/nmsg-dev

Re: nmsg msgmod version mismatch error

Robert Edmonds — 2012-11-14T16:56:11

./conftest: error while loading shared libraries: libnmsg.so.6: cannot open shared object file: No such file or directory

did you run 'ldconfig' after installing libnmsg?

do you have /usr/local/lib on the dynamic linker search path?

Re: nmsg msgmod version mismatch error

Dan Brodsky — 2012-11-14T16:50:58

Sure thing. Here's a paste.

http://paste.ee/p/PPoCO

On Wednesday, November 14, 2012 at 11:47 AM, Robert Edmonds wrote:



_______________________________________________
nmsg-dev mailing list
nmsg-dev< at >lists.isc.org
https://lists.isc.org/mailman/listinfo/nmsg-dev

Re: nmsg msgmod version mismatch error

Robert Edmonds — 2012-11-14T16:47:37

hi, dan:

please send the entire config.log.

nmsg msgmod version mismatch error

Dan Brodsky — 2012-11-14T13:31:20

Greetings, 

I am trying to build the sie-nmsg-0.14 package on a RHEL x86_64 system. I have previously built and installed wdns-0.4 and nmsg-0.7.1 (which also involved installing protobuf-2.4.1 and protobuf-c-0.15).

When I run the configure script, it will not complete, and I get the following error in config.log:

------ snip ------
| #define HAVE_NMSG_MSGMOD_PLUGIN 1
| /* end confdefs.h.  */
| 
|             #include <nmsg/msgmod_plugin.h>
| 
| int
| main ()
| {
| 
|             if (NMSG_MSGMOD_VERSION == 8)
|                 return (0);
|             else
|                 return (1);
| 
| 
|   ;
|   return 0;
| }
| 
configure:13123: error: in `/home/dbrodsky/sie-nmsg-0.14':
configure:13125: error: nmsg msgmod version mismatch

------ snip ------

In /usr/local/lib/nmsg I have nmsg_msg8_isc.a, nmsg_msg8_isc.la, and nmsg_msg8_isc.so files. Is there a flag I need to pass into the configure script to get it to read these? Or perhaps another config parameter or prerequisite I am missing?

I'm installing this

reading dnsdedupe message

A. Mert Kara — 2012-10-16T20:48:55

I figured out the problem. I could read the presentation of the nmsg  
file. However I have another problem with parsing dnsdedupe msgs with  
libnmsg. I am having trouble to read the field value of rdata from  
dnsdedupe.

first I get the field value:
result = nmsg_message_get_field(msg, "rdata", 0, (void **)&_uint8_tmp,  
&_tmp_len);

then I try to parse it with wdns. the result returns as HEX value.
   char *buf = wdns_rdata_to_str(_uint8_tmp, _tmp_len,  
*(dnsdedupe.rrtype),*(dnsdedupe.rrclass));

Am I missing something here?

Thanks

MK

reading dnsdedupe message

Mert Kara — 2012-10-14T21:01:29

Hi,

I am trying to read the output of channel 204 with nmsgtool and I keep getting empty results. Initially I tried to read it with -r flag however it returns the messages with empty cells and <UNKNOWN NMSG 2:1>. Then I thought, perhaps I can pass the message type (-T dnsdedupe) and vendor Id (-V SIE) with it and I got "nmsgtool: usage error: invalid vendor ID" result. 

How can I output the presentation of the channel 204 data file that I captured by nmsgtool (version:0.6.17).

Thank you,

MK_______________________________________________
nmsg-dev mailing list
nmsg-dev< at >lists.isc.org
https://lists.isc.org/mailman/listinfo/nmsg-dev

Re: nmsg moved to rsfcode site, 0.7 releases

Robert Edmonds — 2012-08-07T16:34:15

cool.  yes, freebsd did switch their implementation from pkg-config to
pkgconf.


yes, it has changed since then.  you can see the changes in the revision
history (uploaded to the site just now):

    http://rsfcode.isc.org/git/sie-update/

you can pull down the latest version of the script directly from this
URL:

    http://rsfcode.isc.org/git/sie-update/plain/sie-update

Re: nmsg moved to rsfcode site, 0.7 releases

Jeff Chan — 2012-08-07T11:31:44












Thanks much Robert,
It built successfully after I forced a delete of the old
pkg-config so it could be replaced by the newer pkgconf-0.8.5 :

pkg_delete -f pkg-config-0.25_1

Now we just need to figure out how to get the SIE switch talking
with our server again.

Did sie-update change from the October 2010 version?  If so,
where should I get the current version from?

Cheers,

Jeff C.

Re: nmsg moved to rsfcode site, 0.7 releases

Robert Edmonds — 2012-08-07T01:59:07

hi, jeff:

wdns is the DNS message parsing library that we use:

    http://rsfcode.isc.org/git/wdns/

it's used by various RSF projects (nmsg, sie-nmsg, nmsg-dns-cache, etc.)
so it was split out from the nmsg distribution tarball and has to be
installed beforehand.

unfortunately, looking closer at the build issues on freebsd, it turns
out the freebsd version of pkg-config has been modified to look in
another, non-default directory for .pc files:

    https://bugs.freedesktop.org/show_bug.cgi?id=48743

so i've built freebsd ports for the current version of nmsg and its
dependencies that have been patched to use the freebsd-specific
pkg-config directory.  they're available here:

    http://rsfcode.isc.org/git/rsf-freebsd-ports/

if you have an up-to-date ports tree, you should be able to run the
following commands and get a complete nmsg installation:

    # pkg_add -r git
    # git clone git://rsfcode.isc.org/rsf-freebsd-ports
    # cd rsf-freebsd-ports
    # cd sie-nmsg
    # make install

i've attached

Re: nmsg moved to rsfcode site, 0.7 releases

Jeff Chan — 2012-07-31T02:42:55








Hi Robert,
I think there may be other folks using FreeBSD besides me, for
example several of the other ISC folks.  I put up a fresh FreeBSD
installation and am trying to bring up nmsgtool, etc., on it, but
getting errors about libwdns missing, etc.

Not asking for a primer on git (which I've not used), but is
there an easy way to build a relatively complete nmsg listener
installation, for example from the new repository (or other
means)?

Cheers,

Jeff C.

nmsg moved to rsfcode site, 0.7 releases

Robert Edmonds — 2012-07-25T21:59:49

hi,

nmsg has been moved to a new "RSF software repository" site:

    http://rsfcode.isc.org/

the new site distributes tarballs, debian packages, and git repositories
for nmsg as well as other RSF software projects.

nmsg 0.7.0 was tagged and released a while back, but i forgot to send a
release announcement.  that release contains some significant
refactoring work which should be largely invisible to users; support for
Crossroads I/O transports, which allows transferring NMSG payloads over
TCP and unix sockets; a new ingress byte rate limit for file inputs
(nmsgtool -B); and a new DNSQR_CAPTURE_QR mode for the ISC/dnsqr module
which can be used to disable state reconstruction in dnsqr and capture
DNS queries only or DNS responses only.

nmsg 0.7.1 is a minor bugfix release due to API changes in the latest
version of libxs (Crossroads I/O).

the latest nmsg is available from:

    http://rsfcode.isc.org/git/nmsg/

Re: SIGSEGV when serializing string fields in nmsg (was "Re: nmsgtool --readpres, which message types?")

Robert Edmonds — 2012-05-03T22:14:28

ok, i'm familiar with POLA :)


hm, well, 4 out of 13 of the names for nmsg_msgmod_field_type values
have no protobuf equivalents (mlstring, ip, uint16, int16).  they're
built on top of protobuf fields, granted.


yes, i guess there should be an assertion that prevents
PROTOBUF_C_TYPE_STRING from being used as a field type in transparent
message modules.


well, what's not to like is that it's a C "string".  the protobuf
"bytes" type is better because it is represented, in protobuf-c, as a
ProtobufCBinaryData structure:

    typedef struct _ProtobufCBinaryData ProtobufCBinaryData;
    struct _ProtobufCBinaryData
    {
      size_t len;
      uint8_t *data;
    };

that makes it possible to interoperate with other languages (e.g.,
python) where strings can contain embedded NULs.