Question) I cannot compile ns-2 with your extension. What should I
do?
Answer) Your allinone version may be a newer version than the one we
are using. my suggestion is to install the snapshot
"ns-2.1b7-micro.tar.gz" which include NOAH and our mobility suite.
If you are not familiar with installing NS snapshot, my suggestion is to install
the allinone 2.1b6a version, then untar the ns-2.1b7-micro.tar.gz under the same
level as the ns-2.1b6/, then rename ns-2.1b7-micro/ to ns-2.1b6/ (rename
ns-2.1b6/ to something else first), then rerun "./install". It should
work!
Question) I have install your micromobility extension. The example can be
run successfully,but in nam I can not see the mobile node, Why?
Answer) This is a well known problem of NAM. The mobile host is not shown
when packets go through both wired and wireless domain. We not sure if the
latest NAM solve this problem. Anyway, it has nothing to do with micromobility
codes
Question) I am trying to run Hawaii using the micro mobility suite,
however the codes of hawaii are interwined with HFA and Cellular IP. I would be
grateful if you can provide me with a list of relevant files required for
installing hawaii only with NS-2.
Answer) Unfortunately, for the the maximum reuse of the codes,
micro mobility suite share a lot of common files which is very difficult to
provide you a separate list for each protocol.
Question) When I ran the Hawaii script, I got the following message. How
can I fix it?
------------------------------------------------------------------------------------------------------------
invalid command name "Agent/Hawaii"
while executing
------------------------------------------------------------------------------------------------------------
Answer) This usually means that the Agent is not correctly compiled in NS2 class
hierarchy; which should not happen if you successful
recompile NS2 after replacing the files in ns home directory with those in our directory C++. Make sure you make depend and then make again. Try to check the
Makefile to see if "hawaii.o" is included
Question) Why do you set variabels as following?
------------------------------------------------------------------------------------------------------------
Agent/TCP set sport_ 0
Agent/TCP set dport_ 0
Agent/TCP set packetSize_ 1460
------------------------------------------------------------------------------------------------------------
It doesn't affect to the compiled hierarchy, because theire not binded.
Answer) Those are the runtime variables defined in tcl space. Not
binded but used by the agents, check out "tcl/lib/ns-source.tcl".
Question) why do you set variables as following?
----------------------------------------------------------------------------------------------------------
Phy/WirelessPhy set CPThresh_ 10.0
Phy/WirelessPhy set CSThresh_ 1.559e-11
Phy/WirelessPhy set RXThresh_ 3.652e-10
----------------------------------------------------------------------------------------------------------
These are already set with the same values by the constructor.
Answer) Just an easier way to play with different values of those
wireless parameters. Surely you can get rid of them if you are using default
values.
Question) How can I find out which is the radius of the zone, in which a
BS affect?
Answer) As for the radio coverage of a Base Station, Two-ray-Ground
fading model is used in the simulation, you can calculate the radius by the
simple two-ray-ground formula, check out "tworayground.cc"
Question) How can I find out wich COA is associated with which node.
In the mip traces the node are discribed by their COA and not by their id.
Answer) The node id is different from it address in hierarchical
addressing scheme in NS2. You can map the two by simply print out the node id
and its hierarchical address by:
puts "[$node id] map to [$node address?]"
$node is your object name of your BS or whatever node you wish to know its
address.
