In a question on Stackoverflow the question was raised wether influxd
would communicate with 104.131.151.204 despite
reporting-disabled
was set to true.
This gist contains all the data required to replicate my check on this.
- docker
- influxdb:1.7.7 docker image (sha256:38bc51a4a606e4c91e6adc475d28398bee05ae271102cc3e26ddbabe25cb3f71)
- influxdb.conf included in this gist
- tcpdump
- coreutils (on Mac via macports or brew)
$ curl -O -L https://gist.github.com/mwmahlberg/62762432bfa45cca45a6ec62848f86ed/raw/8e1e72a372b1b76253dcaab8cfeffb6768f58747/influxdb.conf
$ docker pull influxdb:1.7.7@sha256:38bc51a4a606e4c91e6adc475d28398bee05ae271102cc3e26ddbabe25cb3f71
$ docker run -d --name influxdb-sec -p 8086:8086 -v $(PWD)/influxdb.conf:/etc/influxdb/influxdb.config influxdb:1.7.7 influxd -config /etc/influxdb/influxdb.config
Note that I chose to use non-standard names to make positively sure the configuration as below is used.
$ [sudo] sudo [g]timeout -s SIGTERM 2h tcpdump -i en0 dst 104.131.151.204 -s 0 -w capture
In my case, en0
is the interface leasing to the default gateway. Your value might differ.
If you use a Mac, you need to call the coreutil timeout
utility as gtimeout
.
You do not need to call sudo
in case you already are root.
This will run tcpdump
for 2h. Increase if you want to make double-sure. For thorough testing, I would suggest running this setup for one week.