Resolved

seems Monowall isn't liking the dual-port load-balancing ethernet on my new Server... my Log is completely filled with these two messages:

kernel: arp: x.x.x.3 moved from 00:e0:81:56:c6:ae to 00:e0:81:56:c6:ad on sis0
kernel: arp: x.x.x.3 moved from 00:e0:81:56:c6:ad to 00:e0:81:56:c6:ae on sis0

I have doubts its a "bug", but the log filling up with these notices makes finding important things in the Log difficult

seems Monowall isn't liking the dual-port load-balancing ethernet on my new Server... my Log is completely filled with these two messages:

kernel: arp: x.x.x.3 moved from 00:e0:81:56:c6:ae to 00:e0:81:56:c6:ad on sis0
kernel: arp: x.x.x.3 moved from 00:e0:81:56:c6:ad to 00:e0:81:56:c6:ae on sis0

I have doubts its a "bug", but the log filling up with these notices makes finding important things in the Log difficult

It just means you have two devices claiming to have the same IP address, so yes it is a big deal that should be resolved unless the load balancing switch is actually just *alternating* the IP rather than both claiming the IP at the same time.  If it's the latter, then it's just a function of m0n0wall to log MAC changes for the same IP.

execute

sysctl -w net.link.ether.inet.log_arp_movements=0

from /exec.php

should stop it logging all arp movements.

or turn of the aggregation feature of your NIC if it's not 802.3ad and just use the fault tolerant feature or turn of receive aggregation :-)

or turn of the aggregation feature of your NIC if it's not 802.3ad and just use the fault tolerant feature or turn of receive aggregation :-)

I never really found a way "around" the error (nothing in the config for "Aggregation"?) so I just reverted the gang to failover, I'll revisit the issue when I finally get the server on a gigabit switch