GitLab

detects that at least one of the nodes in the lan includes a remote
node. Of course, on links can include remote nodes, but thats okay.

1) Removed the ten iterations limit from main daemon loop I had set during
testing a while back (duh).  This was why slothd was mysteriously disappearing
after half a day.

2) Updated the makefile to produce static slothd binaries

3) Added a locking mechanism to avoid accidentally starting two slothd's
simulatneously.

Checks to make sure that all ports for an experiment are in the
correct switch state. If they are enabled, they should have
carrier.

Note that enough code is shared between checkports and portstats
that some of it could probably be moved to a library at this
point.

than rc.testbed.  Since rc.testbed calls cvsup, modifications to this file
do not take effect until the next reboot occurs.  This is why slothd was not
starting on many nodes.

an experiment fails to setup properly (we were leaving them running).

First, gives us a handy way to build all the tools, if there
is ever more than one.

Second, it's a workaround for a really annoying problem with
configure. Since there was nothing in the tools/ directory itself,
it wasn't getting created, so configure could not make
tools/pcapper (since the parent directory didn't exist.)

Section mentioning non-default daemons started by testbed scripts updated
with slothd info, and corrections were made to the healthd info.

request.

recommendation by Dave in email to testbed-ops).

(punting for today on indicating directions for non-symmetric attributes,
though both are listed.)

Now, due to changes in the parser, lans must have $'s before the name of each node.
(shashi says this is the proper ns syntax) Changed java code to do this.

Event system:

When compiled with -DEVENTSYS, can be made to wait for time to start
in an experiment before starting to count packets. Times are also
reported relative to experiment time start. Use the '-e' flag to
enable.

SUID support:

If compiled with -DDROPROOT, and it seems that pcapper was started
setuid root (euid == 0, and ruid != 0), drops root permissions after
opening BPF (or raw socket in Linux.) This allows it get permissions
to read packets, but still be killed by the user. This is particularly
useful with the testbed's program objects.

New command-line options:

-s: Print out packet counts to stdout, in addition to listening
        on a socket ('-f -' does the same thing, too)
-p: Count only payload sizes, not header sizes
-e: Wait for event system time to start in pid/eid
-z: Don't count zero-length packets in the packet counts (useful
        with '-p')

Also, now creates a GNUmakefile the _right_ way.

Refer http://www.isi.edu/nsnam/ns/doc/node125.html

* Cleanup! A lot of the structure derived from the early frame days,
  which had a noticable (and bad) effect on how I wrote the stuff.  I
  cleaned up most of that yuckyness.

* In process, optimize a little bit on the queries. The old code did
  about 9 queries just to write out the menu options, and then
  repeated most of those queries again in the page guts. I've
  consolidated the queries as much as possible (to 3) and cache all
  the results.

* Fix up problem with users who forget their passwords before
  verification. Basically, I fixed the more general problem of not
  being able to update your user info before verification/approval;
  users now get that menu option no matter their status.

* Fix up problem of users being able to access pages before
  verification (but after approval) by going around the menu options.
  The page level check (after the menu is drawn) now checks all
  conditions (password expired, unverified, unapproved, timedout, and
  also nologins()).

* Minor change in approveuser; do not show the new account to the
  project leader until the new user has verified his account.

* Change verification method, as reqwuested by Dave.  In addition to
  providing the key, also provide a web link to take the user straight
  to verification. I actually take them direct to the login page, and
  pass the key in as an argument. If the user is already logged in,
  bypass and go directly to the verify page (not the form page of
  course).  If the user is not logged in, let him log in, and then
  forward the key onward to the verify page. Basically, bypass the
  form all the time, and just do the verification.

* Minor change in showuser; Do not show pid/groups not approved in,
  and if the count is zero, do not draw the table headings.

database (iddata_clean), and a script to generate fake idle entries for
testing scripts on the minibed (idloadup.pl).

iddata_clean, by default, removes all idle entries older than 36 hours.
This can be changed by providing -m <maxage> (in seconds) to it.

idloadup.pl adds random idle data at time offsets from now, to 5 days
prior (1 sec granularity).  It adds anywhere from 1 to 10 entries per
PC to the node_idlestats page, and from 1 - 10 x # interfaces to
the iface_counters table.

of "fast insert" mode. That option plus a couple of others makes
duplicating the DB 3-4x faster.

Add a DB table of tables to prune out of the copy before creating the
clean DB. There is a lot of stuff in the DB that is not needed for the
testsuite, and the constant copies churn the DB for little reason.

various redundant spots though.

return value on VLAN creation. If it reports success, we look for the
VLAN with findVlan(), to make sure it's really there. We retry a
couple times if it didn't work. This will add a small (sub-second)
time penalty per VLAN created.

We ran into one instance, that we've noticed, where the switch
reported that VLAN creation succeeded, but the VLAN did not actually
get created on the switch.

Change default idledays from 3 to 2, and don't show the swap request button if the expt is marked unswappable. (I'll mark things unswappable as necessary for special expts, even if the original creator doesn't.

size. Works nicely!

again. No biggie.

(Added for my timing tests.)

limited to 31 characters, so we can't give commands with more than 8
outlets. So, we split up the outlets into groups of 8, and issue
multiple commands, if we are passed too many outlets.

Took some minor re-structuring, since we now may need to sync up with
the RPC prompt more than once.

a new hack for remote nodes! All remote node solving is done in the
new wanassign script. That script deals with both phys (ron) and
virtual (vrons), as well as fixed nodes of either type. The solution
is returned to assign_wrapper, which still does the tunnel stuff.
At some point it would be nice to get general purpose virtual nodes
(multiplex) working on either local or remote nodes, but thats a ways
off cause it means too many changes in assign_wrapper, which really
needs a total rewrite.

tb- command passed along in the DB). Add check to make sure no mixed
use of types and classes since. Change solver invocation. Was trying
to use IPC goo to pipe in input to solver and read back results,
abd tee off the input file for debugging. That does not work cause the
tee never exits, and so the child never exits. Reorg slightly; write
the input file to a temp file and pipe in later. I need to kill off
the IPC goo though, since its no longer needed, but its harmless as it
is.

used when the virtual topology does not include any link to the
testbed, but consists only of remote links.