to libvtop.

People try to fix pc433 to pc433. The former is a node in the topo,
the later is a physical node. Causes confusion, breaks. Look for
this corner case.

Allow lans that use shared lans, to have more then one port. So now
you can do this in your rspec:

   <link client_id="link0">
     <vlan:link_shared_vlan name="openflow-mesoscale" />
     <interface_ref client_id="node1:if" />
     <interface_ref client_id="node2:if" />
   </link>

The GPO wants this for the protogeni racks. We now build reverse
map files for the 172.16 subnet, although we do it on a /16 boundry
to avoid a zillion zone files.

I am not planning to write an update script for this, since it would
require scripting changes to named.conf, which I am loath to do. So I
will do it by hand in Utah, and new sites (racks) will get it. If a
site wants it:

	boss> cd obj/named

Copy all of the 172 files to /etc/named/reverse
Copy all of the 172 zone entries from named.conf to /etc/named/named.conf

	boss> named_setup

Did the pubsub one a long time ago, but added a frisbee one as well.

The pubsub dissector has not been tested in its wireshark 1.8 incarnation,
I just converted it from the 1.2.10 version and made sure it compiled.
The frisbee dissector just supports the base UDP protocol (not the TCP
master server protocol) and doesn't implement wireshark conversations.

This last few commits were the result of a two-day trip into the weeds.
This started out as getting a hack shared 10Gb LAN working on the new 820
nodes. Then I decided to test it out by running frisbee at high bandwidth
over that LAN. Next thing you know, I'm out in the fields, looking at
frisbee traces and tweaking Linux sysctls...

In at least the Linux 3.2 kernel on Ubuntu 12, setsockopt to set the socket
buffer size does not return an error if you try to set a value higher than
the kernel max. So we do an immediately following getsockopt to verify.

This will prevent the server from over-driving the send socket (leading to
re-requests of blocks from clients) for really high bandwidth values (i.e.,
with large burst sizes).

Sort them by the node_id the admins assigned, rather than by the
order they were added in.

avoid warnings from the Frontier library.

Til we have snmpit working on the Arista, we statically configure a single
10Gb LAN and put one interface from each of the d820s into it.

This is controlled by setting the node_attribute.shared_lan_* attributes
for each node (ip,mask,mac,speed).

In particular, if $options->{'vlist'} is not present or too short,
do not attempt to look up any virt_node_attributes.

we can use it to create a bridge, as for openvz containers that
use routable IPs.

places.

Documentation to follow.