Axel Beckert

Thanks for trying to reproduce and for these suggestions! I think the `strace` found something: ``` […] [pid 24096] write(1, "\33[33m00:00:00:00:00:00 -> 00:00:"..., 14500:00:00:00:00:00 -> 00:00:00:00:00:00, [udp ] 127.0.0.1:56349 ->...

> Try this: https://github.com/kalamlacki/ipt-netflow "Update ipt_NETFLOW.c" is a very bad style for commit messages. 😞 Please put the relevant part like "update for >= 6.4.0" into the _first_ line of...

> I have one remark, you should take my last 2 commits not only one, the path for sysctl should be net/netflow and not net.netflow Thanks, will have look at...

Relevant commit in Linux seems to be torvalds/linux@0199849acd07d07e2a8e42757653ca8b14a122f5.

> I have one remark, you should take my last 2 commits not only one, the path for sysctl should be net/netflow and not net.netflow Indeed, it compiles fine without,...

> You were testing the commit with net.netflow right? Yes, I wanted to understand why a slash instead of the expected dot was necessary.

This also affects [liboping in Debian](https://bugs.debian.org/997189), but there are actually more such issues than this pull request fixes. The remaining issues are: ``` oping.c: In function ‘update_graph_prettyping’: oping.c:1159:25: error: format...

@cron2: > if I have two hosts "heise.de" in the noping output, it's not easy to see whether v4 or or v6 ping is failing, so I modify the hostname...

Same issue on Debian Unstable: https://bugs.debian.org/897790 Seems to happen if liboping is compiled with GCC 8.

Hi Florian, thanks for the fix! Mind doing a new release with that fix?