Known bugs in 2.00
------------------

Prints previous snoop output after current packet has been captured. The 
reason tcpdump2ascii is doing this is due to the way it parses the output
from tcpdump.

This was intentional, because I needed a quick and dirty fix. Next version 
will probably have this fix unless someone fixes it before I do (which would 
be nice, because then I don't have to do it).

Instead of:

	loop {
		<wait for input and parse it>
	}

tcpdump2ascii should probably do:

	loop {
		<wait for tcpdump info line>
		loop {
			<gobble hex>
		}
		<print snoop details>
	}





