[viff-devel] How to avoid the boring math

Hi friends of VIFF,
I've now played a little bit with artificial bandwidth limits and
artificial delays in order to be able to better analyze protocols.
(Actually, my motivation was to get the running time for AES matching my
analysis. It worked.)
I found out that setting a delay of 1 second for every packet gives a
running time matching the number of rounds quite well. On the other
hand, limiting the bandwidth gives at least a qualitative impression of
the number of elementary operations. Another observation is that one
could also have a look at the TCP sequence numbers to get an impression
of the number of elementary operations.
I've included to shell scripts for Linux: One delays the network traffic
to a given address space by 1 second, the other limits the traffic to
15kbit/s. They must be run as root.
If adding a delay, one should also apply the attached patch to avoid
strange results (longer running times for less traffic).
Best regards,
Marcel
Disclaimer: Hereby I reject to encourage anyone to replace serious
protocol analysis by heuristics.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: delay.patch
Type: text/x-patch
Size: 369 bytes
Desc: not available
URL: <http://lists.viff.dk/pipermail/viff-devel-viff.dk/attachments/20090424/ed4e8f0e/attachment-0006.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: delay.sh
Type: application/x-shellscript
Size: 276 bytes
Desc: not available
URL: <http://lists.viff.dk/pipermail/viff-devel-viff.dk/attachments/20090424/ed4e8f0e/attachment-0007.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: limit.sh
Type: application/x-shellscript
Size: 343 bytes
Desc: not available
URL: <http://lists.viff.dk/pipermail/viff-devel-viff.dk/attachments/20090424/ed4e8f0e/attachment-0008.bin>