i did that yesterday, restarted all the bots
but when a netsplit happened, it started again
and which one should i restart, bot1 or bot2 in case the msg is as i put it
from the hub .unlink *, that should remedy the problem
basically, that err message shows up when a botnet message appears to be coming from a dcc index not associated with the source bot - a temporary situation which shouldn't happen too often, and which is normally resolved by unlink/relink or/and restart