address of the interface instead of the dest&mask, which was bogus
anyway, and now wrong in the presence of variable netmasks for the
destination.

changes; Print a warning when the DB slots are null, and return
standard 255.255.255.0. This is for the transition phase.

Also add version 12 modification to routerconfig; return the "src"
from the virt_routes table, so that the client side can figure out
what interface the route is associated with. There are associated
changes in libsetup to ifconfig,routerconfig,tunnelconfig.

file - if set, it means that the vnode is not allowed to have a
mix of trivial and 'real' links - all must be one type or the other.

your NS file:

	tb-set-netmask $lan0  "255.255.240.0"
	tb-set-netmask $link0 "255.255.255.248"
	tb-set-netmask $link1 "255.255.255.240"

Yep, more rope for the user to hang herself with. Notes:

* You are restricted to 255.255.XXX.XXX. I did not see a reason to
  allow the user that much rope.

* get_subnet can handle 10 or 192.168 addresses so that other sites
  can continue to operate without changing to 10 addresses, although
  they will still be able to change the netmask.

* I've changed the handling for widearea networks to use 192.168, but
  I force the netmask to 255.255.255.248 so that we are not restricted
  to just 255 networks (not that it really matters). To avoid possible
  confusion, the user is not allowed to choose their own IPs for
  widearea networks, and I actually set them to 1.1.x.x, and then
  patch it up later. This is to avoid conflict with existing
  experiments where people may have used tb-set-ip in their NS files.

* There are tmcd and staticroutes and image changes that are required
  to make this all work right!

configure.in.

people to change, and so I can suck it out of a bunch of defs files
cause I am about to change them all anyway!

from the virt_routes table for each lan). I had to add a hash to store
that for each lan, as well as another has to map a node:port back to
the lan so I could find the mask (this is needed in the code that adds
host routes for all the interfaces of a dst, which requires knowing
the mask. The mask has to carried along in the "packed" structures
that Shashi is using to save space.

Note, I have not changed the edgenode optimization code, which has a
255.255.0.0 netmask wired in. The edgenode stuff is turned off, so I
will wait until I hear from Shashi (and the new images are installed,
which is required to make that work anyway).

to treat the given slice as an NTFS.  Analogous to -b for bsd and -l
for linux.

Clean up a little lint in the NTFS code too

section.

I was checking against the idle threshold (ie 2hrs) when I meant to check
against the idle window (5 min), and the result was that no idleswap
warning emails were getting sent. Doh!

code (asking tmcd twice for routes, ifconfig, etc). Shashi will fix
later.

We have some evidence that some application is "chmod 600"-ing
/dev/console and, in the process, /dev/null.

Remove the code to create vn devices, bootvnodes does this now.

routing (-V option to vnodesetup).  I was going to do this just for
jails that used gated, but there is no efficient way to do this
(I don't want to make a redundent "tmcc routing" call for every jail
just for the very rare case they are using gated).

Since it is the Right Thing To Do anyway, I'll just go for it now
while we only have one external user.

There is a possibility of unexpected consequences on mini, but I'll
cross that bridge when I get to it (or more likely, when Leigh gets
to it :-)

The '-b' switch, which applies the filter to all interfaces
The '-t' switch, which allows you to give a list of alternating
   interface names and filters

revision.

are just the DB table changes, setting the mask based on the value
from the virt_lans table, which defaults to 255.255.255.0, so there
should no visible effects (tmcd changes not checked in yet).

or wait for them. I'll add this later.

that part out since it is not finished/tested.

inside, but rather I do just enough to get the card booted (using
Abhijeet's minicom/expect scripts, but with changes to support the
configuration coming from tmcd. I also create a file of interface and
routeadd directives, so that the network configures properly, but
thats about it. Getting a more complete client side environment that
includes perl and sshd for the arm will have to wait.

swamping tmcd.

variable netmask stuff to it, and probably break it.

have to change to an int format to save space. I'll probably make some
changes to the migrate code later, but I want to get the DB changes
checked in.

Add a -V option to mkjail.pl telling it to use the virtual control net
IP (172.16.0.1) for the default route instead of the real control net
IP (155.101.132.1).  In this case, it also assigns a virtual control net
IP alias (172.17.<pnode>.0) to the physical interface so that the
aforementioned routes can actually be installed.

Add the same -V option (only valid with -j) in vnodesetup so that we
can get it through from bootvnodes.  (Also cleaned up the usage message
some)

The virtual control net address/mask are currently constants in mkjail.pl.
At some point they can/should be changed to config time options so that we
can easily use this on minibed too.

In theory, this (-V) shouldn't be an option and we should just use
virtual control net routing all the time.  But I want to get some more
testing and we have to resolve the minibed conflicts first.  So for now,
this is an option and it is off by default.

Haven't tied this option in with gated yet, so creating a vnode experiment
with Session routing still won't work.  If you want to do that, create the
experiment, watch gated blow up right and left, login to all the physical
nodes and change bootvnodes to add -V to the invocation of vnodesetup,
and then reboot everything.  Now it should be working!

keeps boss from getting pummeled.

a correct final reading.

than imagename, and this ID is used in both tables. They should be the
same length in the DB, and I have added a TODO item for it.

a vnode to be rebooted.

which happens on lans of vnodes that are split between pnodes. assign
spits out trivial links for the nodes collocated on the pnodes, but if
there are two groups of vnodes on different pnodes, the connection is
not explicit in the link statements that assign gives (techinically,
they should not be trivial links, but Rob is still thinking that
over). Fortunately, I have enough info from assign to extend the vlan
and to patch the veth interfaces afterwards. Its god-awful stuff, and
I hope I can strip it out soon.

tarball.  It's horrible, but it works.  If this needs to be rebuilt
often, this should be turned into a makefile.

plabname file.

idle loop while waiting for a signal in a vserver.  Moved vnode
killing/halting into the signalling process for vservers, and made the
running vnodesetup just clean up after itself in these cases.  Rewrote
the process of killing a vserver to use proc to get the process list,
and to not kill any of its parent processes.  This was necessary to
make it possible to report back to Emulab when node teardown is
complete.