prevent 'interrupts' during message processing
cleanup _cb_olsr_forward_message
don't count hops manually, rely on proper 1-hop and 2-hop seed
don't print neighbors
don't be too eager in saying we did something when we actually didn't…
don't overwrite seq_no in writer (why is this even possible?)
store seq_nr in a sane way
update todo