Go to file
Jean-Louis Huynen 12cdeabfb6
Merge pull request #21 from D4-project/dependabot/go_modules/golang.org/x/net-0.17.0
build(deps): bump golang.org/x/net from 0.12.0 to 0.17.0
2023-10-12 08:01:55 +02:00
conf.sample chg: [input] d4 redis input config sample 2020-04-08 15:02:53 +02:00
media Improves README 2019-02-14 08:37:22 +01:00
.gitignore chg: [mod] bump d4-golang-util 2020-02-12 15:03:46 +01:00
LICENSE Relicensing to MIT 2019-01-07 10:25:49 +01:00
Makefile chg: [mkf] - 2020-04-27 14:47:28 +02:00
README.md Update README.md 2020-04-27 14:40:07 +02:00
d4-goclient.go chg: [filewatcher] daily rotation of watched folder - fixed 2021-03-03 12:10:46 +01:00
d4-goclient_test.go Fix #4 2019-04-01 15:01:01 +02:00
go.mod build(deps): bump golang.org/x/net from 0.12.0 to 0.17.0 2023-10-11 22:52:51 +00:00
go.sum build(deps): bump golang.org/x/net from 0.12.0 to 0.17.0 2023-10-11 22:52:51 +00:00



Release Software License Go Report Card

d4-goclient is a D4 project client (sensor) implementing the D4 encapsulation protocol.

The client can be used on different targets and architectures to collect network capture, logs, specific network monitoring and send it back to a D4 server.

For more information about the D4 project.


Fetch d4-goclient code and dependencies

go get github.com/D4-project/d4-goclient


  • golang 1.13 (tested)


Launch a d4-server (if you don't have a server)

See https://github.com/D4-project/d4-core/tree/master/server $IP_SRV being the d4-server's address, $PORT its listening port

Configuration files

Part of the client configuration can be stored in folder containing the following files:

  • key: your Pre-Shared-Key
  • snaplen: default is 4096
  • source: stdin or d4server
  • destination: stdout, [fe80::ffff:ffff:ffff:a6fb]:4443,
  • type: D4 packet type, see types
  • uuid: generated automatically if empty
  • version: protocol version
  • rootCA.crt: optional : CA certificate to check the server certificate
  • metaheader.json: optional : a json file describing feed's meta-type types

If source is set to d4server, then one also 2 additional files:

  • redis_queue: redis queue in the form analyzer:typeofqueue:queueuuid, for instance analyzer:3:d42967c1-f7ad-464e-bbc7-4464c653d7a6
  • redis_d4: redis server location:port/database, for instance localhost:6385/2


  -c string
    	configuration directory
    	Check TLS certificate against rootCA.crt
    	Set to True, true, TRUE, 1, or t to enable TLS on network destination (default true)
  -cka duration
    	Keep Alive time human format, 0 to disable (default 30s)
  -ct duration
    	Set timeout in human format
  -rl duration
        Rate limiter: time in human format before retry after EOF (default 200ms)
  -rt duration
    	Time in human format before retry after connection failure, set to 0 to exit on failure (default 30s)
  -v	Set to True, true, TRUE, 1, or t to enable verbose output on stdout

Pipe data into the client

In the followin examples, destination is set to stdout.

Some file

cat /proc/cpuinfo | ./d4-goclient -c conf.sample/ |  socat - OPENSSL-CONNECT:$IP_SRV:$PORT,verify=0

tcpdump (libpcap) output, discarding our own traffic

$IP being the monitoring computer ip

tcpdump not dst $IP and not src $IP -w - | ./d4-goclient -c conf.sample/ |  socat - OPENSSL-CONNECT:$IP_SRV:$PORT,verify=0

Forwarding data from a D4 server to another D4 server

Add two files to you configuration folder: redis_d4 and redis_queue:

  • redis_d4 contains the location of the source d4's redis server database, for instance
  • redis_queue contains the queue to forward to the other D4 server, for instance analyzer:3:d42967c1-f7ad-464e-bbc7-4464c653d7a6