know the two links being connected together, and add an isbridge
flag.

in the NS file (which is in TCL is derived from the node class). For
example.

set nodea    [$ns node]
set bridge1  [$ns bridge]
set bridge2  [$ns bridge]
set nodec    [$ns node]

set link0 [$ns duplex-link $nodea $bridge1 * 0ms DropTail]
set link1 [$ns duplex-link $nodec $bridge1 * 0ms DropTail]

With changes to the mapper, this allows the mapper to map multiple
bridge nodes to a single physical node, like we do for delay nodes
when there are enough interfaces.

As a convenience to users, now named_setup adds CNAMES for the
additional multiple mapped nodes.

We now make a pass through the implemented_by tree setting port speeds
that the user left up to assign (i.e., that are 0).  We start at the
lowest level links and assign default speeds.  Then the speed values for
the start and end segments for each path get propagated to the link
being implemented by the path.  Should be pretty generic for any number
of layers.  We warn if the higher level links don't support those speed
settings (if they don't, we're gonna have a problem; but I think assign
protects this from happening).

is to prevent assign from putting the lan node on a pc; always prefer
a real switch. To do this, use a feature on the real switches called
real-switch:0 and when we mix pnodes and vnodes, ask for that feature
on the fake lan nodes; real-switch:1.0

for LM.

properly. Now able to allocate and redeem tickets at PLC via cooked
mode.

encapsulated link; the vinterfaces were not getting updated properly.

I am not happy with the change mentioned above, but I needed it to
make vlan tag pre-reservations work; the encapsulation vlan has a
generated name, and that is hard to match up with the tag that is
reserved before the experiment is created, as from the protogeni
interface when stitching. I plan to come back and redo this after the
GEC.

Cleanup the debugging output in nodejailosid.
Make sure that virtnodes get a reasonable default osid
based on the node type info.

be generalized in some fashion.

Change to how vlan ecapsulation links are represented in the lans
table. Formerly, we had two links; one was the underlying vlan and the
other was the ecapsulated link running over it. This is required when
*not* using vlan encapsulation since there might be multiple emulated
networks on top of the vlan network.

However, when using vlan ecapsulation, this strictly one to one; there
are multiple vlan links, with the ports in trunk mode. There is no
reason to have two entries in the lans table, and in fact was causing
me grief wrt vlan tag reservations in protogeni, since the name of
link is not the same as the name of the underlying vlan link that was
getting created. And so it was impossible to match up the
reservations.

I pray this does not break 10 other things.

reported by Hussam.

although the default is currently to do cooked mode in "basic" mode,
rather then "full" mode.

should retry another time.

operational and may never be so. Just want to get it into the
repo.

I had done this a while ago, but broke it slightly when I added MLE
stuff.

as Node->CreateVnodes() instead of Node::CreateVnodes().

vlans.