FIXME: looks like setsockopt behaves asynchronously

Setting it in a tight loop doesn't pass it through everytime
(or I have a bug in header parsing)

d@puck:~/git/isochronous$ ./udpburst -f localhost -c 100 -C -d -s 1000
1000 bytes -- received 100 of 100 -- 100 consecutive 0 ooo 0 dups 0 ect

........................................................................
...........................
82c2 2 2 2 2 2 2 2a242 2 2 22282c2 2 2 2 2 2 2 2a242 2 2 22282c2 2 2 2 2
 2 2 2a242 2 2 22282c2 2 2 2 2 2 2 2a242 2 2 22282c2 2 2 2 2 2 2 2a242 2
 2 22282c2 2 2 2 2 2 2 2a242 2 2 22282c2 2 2 2 2 2 2 2