Control: tags -1 + confirmed
Hi again,
I can confirm that arpwatch does indeed start too early when capturing
on bridge devices. I have also verified that adding $network to the
Required-Start field in the LSB header fixes the problem.
I will push the fix into our git repository soon, but I
Hi,
thanks for reporting this issue.
On Mon, 08 May 2017 21:40:06 -0700
jmol...@swoncology.net wrote:
> Arpwatch seems to start before the networking is really ready. In this
> case, we are listening on a bridge interface, so that might have
> something to do with it.
>
> This might be a
Package: arpwatch
Version: 2.1a15-2+b1
Severity: important
Arpwatch seems to start before the networking is really ready. In this
case, we are listening on a bridge interface, so that might have
something to do with it.
This might be a problem with systemd/networking/bridging/etc. Feel free
to
3 matches
Mail list logo
