Markus Lude schrieb:
On Fri, Aug 01, 2008 at 07:07:11PM +0200, Michael wrote:
Sorry, I don't understand what you mean. Arpwatch doesn't use Berkeley
db at all.
Thats why I asked if it might be related. Maybe bad wording, english
isn't my mother language. Similar would probably have been a better
word. The dovecot issue probably isn't related to Berkeley-DB either,
but its a similar issue. The author is checking it out.
Works as expected. Do you run any programs which need your network card
running in promiscuous mode?
Hmm, actually...
<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST>
What kind of applications would make it run in PROMISC mode? Would an
IPv6 tunnel suffice? spamd? ftp-proxy? dhclient? or arpwatch itself?
What do you reproduce? What exactly did you do, what did you get and
what did you expect?
Start arpwatch, wait, normally the arp.dat gets > 0 bytes but it
doesn't. It does on all other machines (i386) I tested/run arpwatch on,
just not on those two sparc64.
