In my environment wackamole runs on two hosts. However there are two
features which are strange (Ann.: my spread runs on port 4805)
When I start wackamole on the primary host it writes the following lines
into my syslog:
Jan 22 11:14:28 node1 wackamole[25506]: connecting to 4805
Jan 22 11:14:28 node1 wackamole[25506]: Dequeued arp spoof notifier.
Jan 22 11:14:28 node1 wackamole[25506]: No such interface
What does that mean "No such interface?". The return code of wackamole
is 1, indicating a startup failure. However all virtual interfaces
configured in /etc/wackamole.conf are taken over properly.
The second problem, when I run 'spuser -s 4805' and than join into the
group wack1 and leave the group wack1, sometime wackamole dies.
You may reproduce it like this:
Spread is running on both hosts and is able to communicate.
Run wackamole on the primary, assure that all virtual interfaces have
been taken over.
Run wackamole on the secondary.
Run spuser -s <your_spread_port> on the secondary.
Join the group wack1 (or whatever you configured in /etc/wackamole.conf
as Group)
Wait for a few seconds
Leave the group wack1
Sometime wackamole dies on the primary giving up all the virtual,
sometimes only the virtual interfaces are given up.
This bug can not be reproduced always, but quite often.
Jacob
features which are strange (Ann.: my spread runs on port 4805)
When I start wackamole on the primary host it writes the following lines
into my syslog:
Jan 22 11:14:28 node1 wackamole[25506]: connecting to 4805
Jan 22 11:14:28 node1 wackamole[25506]: Dequeued arp spoof notifier.
Jan 22 11:14:28 node1 wackamole[25506]: No such interface
What does that mean "No such interface?". The return code of wackamole
is 1, indicating a startup failure. However all virtual interfaces
configured in /etc/wackamole.conf are taken over properly.
The second problem, when I run 'spuser -s 4805' and than join into the
group wack1 and leave the group wack1, sometime wackamole dies.
You may reproduce it like this:
Spread is running on both hosts and is able to communicate.
Run wackamole on the primary, assure that all virtual interfaces have
been taken over.
Run wackamole on the secondary.
Run spuser -s <your_spread_port> on the secondary.
Join the group wack1 (or whatever you configured in /etc/wackamole.conf
as Group)
Wait for a few seconds
Leave the group wack1
Sometime wackamole dies on the primary giving up all the virtual,
sometimes only the virtual interfaces are given up.
This bug can not be reproduced always, but quite often.
Jacob