rejecting UDP requests as NON-SSL, due to removing some code that used to
skip around the TCP checks.

the queues for fake planetlab (so it's easier to experience loss).

out the time (likely) spent on the return path. We figure this out
from the minimum delay, so the MaxDelay sensor now depends on the
MinDelay sensor.

that clients and servers can avoid using hardwired ports on those
experimental nodes. I have added the following tmcd operation:

	tmcc portregister <service> [<port>]

where we assume its the control network IP (from the DB), and the pid/eid
of the node the experiment belongs to. The given port is entered into
the port_registration table for the experiment, using the service as the
tag. Supplying port=0 clears the registration from the table.

When called like:

	tmcc portregister <service>

we return the registered port, or nothing.

I hacked up a little C library module in libtb so that there is something
that looks like a C interface to this:

 	int
 	PortRegister(char *service, int port);

 	int
 	PortLookup(char *service, char *hostname, int namelen, int *port);

The above routines call out to tmcc of course.

Lastly, I changed the sync server and client to use the new port
registration, via the library calls above.

There are other emulab services that need to be changed as well, but
they can be done on an as needed basis.

More tbreport changes from Mike Kasick <mkasick@andrew.cmu.edu>:

- Added tblog support to nscheck.

- Added ns_parse_failed error to nscheck.

- Added invocation column to report_errors to differentiate between assign
  runs in infeasible resource assignments.

Added a replay-sensor=<type> option. This allows a different set of sensors at replay time than at original run time. Use one option per type. This new list replaces the list at run time.

Quick fix so that command output logs will be printed during replay when the actual messages are blocked.

Added ewma for throughput. Various fixes. Various additional logging. Simplified saturation calculation and moved it to StateSensor

First, we can't use logWrite() in processArgs(), because it has not
been initialized yet. (And, presumably, the log writer *has* to be
initialized later, because at some point we will want to add command
line args to control its behavior).

Second, actually exit if there are any errors, instead of proceeding
to do the wrong thin.

(Gotta dead horse, must keep beating it...)

The problem is that, if you want to do anything--change the stub name,
add a command line argument--you have to replace the whole command line
and that requires knowing the rest of the default/previous command line
that has not changed.

Fix experiment event stream unsubscribe bug.

rows pushed across to the DP.

Fixed the traffic model so that it is now in line with what Rob and I discussed. Delays are before the write with the write size cached. Writes expire based on an expiration date.

Miscellaneous fixes. Open problem: PacketSensor does not deal correctly with zero-sized packets. I changed KernelTcp to pass such packets because otherwise there is no way to do state changes based on SYN/FIN/other packets. SYN is handled ok for now because of a change noted below. FIN is not.

Added a StateSensor. As I discovered, using the kernel tcp_info data structure isn't useful when dealing with fields that change on a packet by packet basis because the kernel information is retrieved at processing time and not capture time. For instance, it is useless when trying to determine whether a connection was established by the time a particular packet was sent (to determine whether it is part of the three-way-handshake). The StateSensor keeps track of the state machine and correlates it to the packet involved. This allows the other sensors to rely on it to distinguish between connection setup and the rest of the connection traffic. Added references to it in the PacketSensor, the DelaySensor and the ThroughputSensor.

Changed the way packet information was transmitted to the sensors to make it easier to add new packet types (as will be necessary when accept()s are handled).

Fixed all outstanding flaws in the basic feedback mechanism. In short, "Its alive!". Currently the only data being transmitted is the base rtt (MinDelay). Now that the feedback is working in a basic form, it will be easier to get the other characteristics online.

Fix up the /etc/passwd file creation process to work correctly when
the slice is rebooted (i.e., when rc.inplab gets re-run, don't append
all the existing service slice user entries - exponential blowup!).

This is what caused the bgmon sliver on the German node to go haywire with
memory - the sliver was rebooted many times.

Remove debug output in cloudinfo-set.

Fix type info cloudinfo.txt

Modified cloudinfo to dump output in the form cloudinfo-set can use.

Fixed bugs in cloudinfo-set

Added documention (well, relevent email messages) on cloudinfo and
cloudinfo-set.

Some bugfixes and updates to the monitor.

* Added load average monitoring and initial test startup randomization

The load the monitor was exerting, especially at startup, was pretty high.
This change appears to have brought that under control.

* Fixed window size bug(s)

There were a few bugs related to tracking the outstanding child process
window that are corrected by this checkin.

Change dbmonitor to, by default, use the latest of A->B and B->A
values when setting characteristics on site A.  Do this for both latency
and bandwidth values, though should probably allow BW values to continue
to be asymmetric.

list, which could happen if we somehow saw an ack for a packet whose
send() we missed (ie. the kernel dropped it on the way in to pcap).

Fix range check - this was necessary because of my change to the
ackFor calculation.

Tricky detail about STL list.erase() - it does *not* erase the end iterator,
which meant that we were failing to remove the packet being acked (we were
removing all packets up to that one). So, we have it increment the iterator
in localAck() even if we find the one we're looking for.

Tested well for lossless connections - still needs testing for lossy
connections and SACK (see below). Hopefully, it works for the former,
but I know it doesn't work for the latter.

Added more debugging output to localAck()

Added a check which should warn us if we see any SACKS, though I
can't be sure it works, because I haven't seen any yet (that I know
of! :)

Small script to set the cloudinfo from an input file.  Only works
on elab experiments for now.

usage: showsamples.pl [-Bbdl] <srcix>|all <dstix>|all
   show database records for given site indices
       -B        show both srcix -> dstix and dstix -> srcix
       -b        show bandwidth
       -d        show delay (the default)
       -l        show loss
       -n <num>  show only the last <num> records
       -S <time> show records no later than unix timestamp <time>

usage: showsamples.pl -e pid/eid
   show mapping of name->ix for all plab nodes in <pid>/<eid>

wrong interpretation of how part of TCP works.

Being an ACK and being a data packet are *not* mutually exclusive,
though the old code assumed that they were.

There are basically four things we might need to do:
If outgoing
    (a) Handle an outgoing ACK
    (b) Handle an outgoing data packet
If incoming
    (c) Handle an incoming ACK
    (d) Handle an incoming data packet

Note that a and b can be done on the same packet, as well as c and d. Right
now, however, our code only handles b and c. We will need to support a and
d before we can model real applications, I think!

Also, make handleTcp() more robust.

Avoid counting planetlab vnodes twice.

tbreport related changes from Mike Kasick <mkasick@andrew.cmu.edu>:

- assign_wrapper2 now passes violations to the tbreport error parser.

- Fixed improper regexp in assign_wrapper2 tbreport error parser.

- Readded create_vlan_failed error in snmpit (left out of original commit
  for unknown reason).

- Modified endexp to use libtblog, added tbswap_out_failed error.