Commit 0d6e2480 authored by Robert Ricci's avatar Robert Ricci
Browse files

Updated the tmcd 'hostname' documentation to match the way we

acually do it now.
parent 19aadc7a
...@@ -369,35 +369,39 @@ experiments to operate using the symbolic names of the nodes (as ...@@ -369,35 +369,39 @@ experiments to operate using the symbolic names of the nodes (as
defined in the NS file), instead of IP addresses, which are generally defined in the NS file), instead of IP addresses, which are generally
assigned by the configuration software, not the experimentor. Since assigned by the configuration software, not the experimentor. Since
nodes can use multiple experimental interfaces, the reply gives the IP nodes can use multiple experimental interfaces, the reply gives the IP
address for each interface on each node. An additional alias is address for each interface on each node. Additional aliases can be returned
returned for nodes that are directly connected to the node making the for nodes that are directly connected to the node making the hostnames
hostnames request. Secondary interfaces, and interfaces that are not request, or that the requesting node has a route to. Secondary interfaces,
directly connected are named with a -X suffix, where X is the ordinal and interfaces that are not directly connected are named with a suffix
number of the interface. The reply to this request is one or more indicating the link or LAN that interface belongs to. For historical
lines in the following format: reasons, we provide an additional alias in the form 'node-X' where X is
the ordinal number of the interface. The reply to this request is one or
more lines in the following format:
<code><pre> <code><pre>
NAME=nodeA LINK=X IP=X.X.Y.A ALIAS=nodeA NAME=nodeA-linkX IP=X.X.Y.A ALIASES='nodeA nodeA-0'
NAME=nodeB LINK=Y IP=X.X.Y.B ALIAS=nodeB NAME=nodeB-linkY IP=X.X.Y.B ALIASES='nodeB nodeB-0'
NAME=nodeC LINK=Z IP=X.X.Z.C ALIAS= </code></pre> NAME=nodeC-lanZ IP=X.X.Z.C ALIASES='nodeC-0'
</code></pre>
The <tt>LINK</tt> field is the number of the network interface on the ALIASES is a space-separated list of aliases. The /etc/hosts file that
destination node, that this node is connected to. The /etc/hosts file would be created for this response is:
that would be created for this response is:
<code><pre> <code><pre>
X.X.X.A nodeA-X nodeA X.X.X.A nodeA-linkX nodeA nodeA-0
X.X.X.B nodeB-Y nodeB X.X.X.B nodeB-linkY nodeB nodeB-0
X.X.Z.C nodeC-Z </code></pre> X.X.Z.C nodeC-lanZ nodeC-0
</code></pre>
Say that nodeA is making this request. NodeA is obviously connected to Say that nodeA is making this request. NodeA is obviously connected to
itself, so it gets an alias pointing to its own interface. NodeA is itself, so it gets an alias pointing to its own interface. NodeA is
directly connected to NodeB on NodeB's <tt>Y</tt> interface, so it to directly connected to NodeB on NodeB's <tt>linkY</tt> interface, so it too
gets an alias so that an application running on nodeA can just use the gets an alias so that an application running on nodeA can just use the name
name NodeB. NodeC is not directly connected to NodeA (perhaps it is NodeB. NodeC is not directly connected to NodeA, and nodeA does not have a
connected to NodeB on one of NodeB's other interfaces), so it does not route to it (perhaps the network toplogy is disjoint, or perhaps routing
get an alias. Refering to nodeC on nodeA would be confusing and was not enabled in the NS file,) so it does not get an alias. Note that, in
possibly incorrect. the case of nodes that are not directly connected, no guarantee is made
that the alias is picked for the 'nearest' interface.
<p> <p>
<li> <a NAME="REF-LOG"></a> <li> <a NAME="REF-LOG"></a>
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment