Support port ranges in the TCPMonitor

The total possible range is 1-65536. But the total used ports should
always be something way south of that :-)

In fact, range="1-65536" should be a great test case... As long as
networking is up and running, monitoring that range should always keep
a system awake, as long as there's traffic somewhere, on some TCP
port.

In shell:
 netstat -nt | col4 | col2 : | sort -nu

That's a rough look at your open, used, tcp ports, sorted by unique,
and numerically. I'd think we should iterate over those, and compare
those with the user's configuration.

The user should be able to configure it like this:

tcp = "1,2,30-100,4780,8000-10000"

Your config processing would split this string and handle it
appropriately. Right?

(We ***really*** need to move this to a bug discussion, please).