TWiki > Simulation > IPv6Suite > QuestionsAndAnswers	TWiki webs: Main | TWiki | Know | Sandbox
	Simulation . { Changes | Index | Search | Go }

IPv6Suite Questions and Answers

• Tutorial
  • Quick start to build a network topology
  • How to create a topology?
• Useful Tips
  • A straight way to run different scenerio in a project
  • XML validation
  • (OMNET)nedc
• Problem Solving
  • "CMake Error: Please set the option BOOSTROOT to correct value"
  • MIPv6Network example is non-executable
  • Failed build dependencies
  • XMLParser Unable to find attribute
  • (OMNET)BLT Tcl/Tk extension NOT FOUND
  • Ambiguous conversion error
• Infomations
  • Wireless AccessPoint Gates
  • Current MIPv6 Implimentation Version
  • Generate Files

All questions and answers were collected from the OMNeT++ mailing list, If you come across to a problem about IPv6Suite that is not listed on this section, try to subscribe to mailing list and don't hesitate to ask.

The Questions with "(OMNET)" prefix means they are basically OMNeT++ questions...

Tutorial

Quick start to build a network topology

Q: I have just installed the IPv6 Suite and would like to know how to start it to build my network topology?

A: Step1. You can try looking at one of the simpler examples say Examples/TunnelNet and copy that over to a new subdirectory say Examples/TestNetwork.

Step2. Go into your new directory. Start renaming the files to the way you want.

Step3. Change the topology to the one you want and also the omnetpp.ini would need to be change as your network name may be different.

Step4. Then modify CMakeLists.txt so that it corresponds to your filename. Then modify Examples/CMakeLists.txt and add your directory to the list of directories in the SUBDIRS directive.

Step5. Now you can simply type make from the top level directory IPv6Suite and it should start building your network too.

How to create a topology?

A: If you are using omnetpp 3 this is probably simpler. No changes are required in CMakeLists.txt as you will not need to compile myHMIPv6.ned. By adding the following into your myHMIPv6.ini it will use omnet's dynamic loading of ned files.

[General] preload-ned-files = *.ned

As for the xml file you can specify it in your myHMIPv6.ini as

.*.IPv6routingFile = myHMIPv6.xml

Useful Tips

A straight way to run different scenerio in a project

A: Try ./HMIPv6Network -f myHMIPv6.ini

If you just put your ned/ini/xml files into an existing directory like MIPv6Network or HMIPv6Network then you can simply run your network via e.g.

./MIPv6Network -f your.ini

where your.ini would load your ned file dynamically etc. (refer to omnetp doc)

When you want to simply gather data without the GUI try turning off OPP_USE_TK from ccmake. This does not require typing make clean as it simply changes what libraries are linked and will create two executables in each directory i.e. for HMIPv6Network you'll get an executable of the same name as well as tkHMIPv6Network.

Then you can also specify the run number on the command line too #./HMIPv6Network -f myHMIPv6.ini -r 3 However this only works for the cmdenv interface i.e. non tk version though.

XML validation

A: Well the error you see is XML document xxx.xml fails to validate

visual inspection is probably not enough. You can try running this command to pinpoint the error

xmllint --noout --valid xxx.xml

(OMNET)nedc

Q:I have read omnet++(2.3v) manual and came to know that nedc compiler can be found in the omnet++ directory. I searched for it.But I didn't get it.Where can I get it?

A:nedc is under the bin directory, as the other executables. nedc is required to convert your NED code to C++. You must then compile and link those C++ files. This is the old way.

If you use OMNeT++ 3 (not 2.3), you don't really need nedc. You may simply keep a list of ned files in nedfiles.lst (1 per line) and add the following line to omnetpp.ini of your project, inside the [General]section:

preload-ned-files = *.ned @nedfiles.lst

This is called dynamic loading of NED files. It is much easier.

Problem Solving

"CMake Error: Please set the option BOOSTROOT to correct value"

Q: The very first specific error message in cmake was: "CMake Error: Please set the option BOOSTROOT to correct value"

Running rpm -q boost shows that I have boost-1.31.0-1 installed

A: Check if there are files in /usr/include/boost if not then install a package called boost-devel which matches your version of boost exactly. Or download our boost srpm and build from that see Installing Boost section at InstallationProcedureIfYouHaveRootAccess for details.

MIPv6Network example is non-executable

Q: When I execute MIPv6Network example with #./MIPv6Network command, it pop up the err message:

can't open ini file "param.ini"

A: Please remove the line "include param.ini" in omnetpp.ini, which in the same example folder.

Failed build dependencies

 [root@localhost]# rpmbuild --rebuild --define "cvsdate 20040730"
 omnetpp-3.0pre_20040730-11.src.rpm
 error: Failed build dependencies:
        tk >= 8.3 is needed by omnetpp-3.0pre_20040730-11
 [root@localhost]# 

A: you can edit /etc/ld.so.conf you add /usr/local/lib and do command ldconfig.

if you want rpm -ivh omnetpp after build, you copy that library such as libBLT2.4 , libtcl and libtk in /usr/X11R6/lib/.

XMLParser Unable to find attribute

Q: When I try to run an example, the XMLParser dies with "Unable to find attribute with name careofTestOnly".

A:If you are using the latest omnet (available from same place you got ipv6suite) I think by default it will choose the omnet++ parser. In ccmake under advanced mode, check that both USE_XMLWRAPP and USE_XERCES are off.

(OMNET)BLT Tcl/Tk extension NOT FOUND

* BLT Tcl/Tk extension NOT FOUND -- please install it

A: To check if BLT is installed correctly into Tcl/Tk, start "wish" (the Tcl/Tk shell), and type "package require BLT 2.4" -- the answer should be "2.4". Basically, OMNeT++ does the same: it issues the above package require command, and if it fails it prints the "NOT FOUND" warning and decides to cut features that'd require BLT.

Basically, Tcl is looking for a "pkgIndex.tcl" file which would tell it how

to load BLT. This file is best placed in a "blt2.4" subdirectory under Tcl's library directory (usually /usr/lib/tcl8.4, or the value of the TCL_LIBRARY environment var), so: /usr/lib/tcl8.4/blt2.4/pkgIndex.tcl. Tcl should also find it at /usr/lib/blt2.4/pkgIndex.tcl. My copy of the BLT pkgIndex.tcl file is about 40 lines, and contains a LoadBLT? proc, and (at the end) a "package ifneeded" command.

Details about Tcl's package loading mechanism can be found here: http://www.tcl.tk/doc/tea/tea_tcl2k.pdf, "The Package Mechanism"

Ambiguous conversion error