zrp installation in ns-2.35 on Fedora 19
Trying to patch zrp using similiar steps as for ns-2.34. but the error is there related to - ./common/packet.h:329:10: error: ‘PT_ZRP’ was not declared in this scope
|
Quote:
did you install gcc 3.4-compt on fedora 19 ? the DEFAULT version 4.8 is WAY TO NEW to use to build ns2 and ARE you exporting cc=gcc34 or set alternatives to use 3.4 ? or created sim-links to use 3.4 |
@bitsandeep : Welcome to LQ.
Please make sure that you do the ns-allinone build with .. $ cd ns-allinone-2.33/ && export CC=gcc34 CXX=g++34 && ./install .. The text in the (ZRP) ns-2.33/Makefile, line 37, must be : CPP = g++34 P.S. : There is no ZRP for ns-2.35 ! The good news : You can have as many versions of ns-allinone-2.xx as you want, installed at the same time. But : Do not add any *PATH text to .bashrc : * Not required, when it's your computer ! ZRP info http://www.linuxquestions.org/questions/tags/zrp/ - |
3 Attachment(s)
# 201, @knudfl.
Here is the code TCL file, traffic and scenario file for reference. |
Ref. #4 , and post #200 here
http://www.linuxquestions.org/questi...25/page14.html From e-zrp.tcl : "Usage: ns-zrp energy-zrp.tcl -scen <cp> -tfc <tfc> -tr <tr> -rpr <rpr>" .. Which means you will also have to inform about all the commands you are using for various simulations with <energy-zrp.tcl> (? alias e-zrp.tcl ?) |
#5
I am using the following command to run the simulation: ns-zrp e-zrp.tcl.txt -scen movement/scenRWP-75.ns_movements -tfc traffic/cbr-75-40 -tr e-zrp.tr -rpr ZRP |
#6 and #200 http://www.linuxquestions.org/questi...25/page14.html
Some hints about "Client Xx: Handoff Attempted" https://www.google.com/webhp?hl=all#...andoff+attempt > example http://mailman.isi.edu/pipermail/ns-...ly/068524.html Quote:
- |
I am again trying to implement ZRP in NS-2.34 on Fedora 19. Patch was not successful, I have done the steps manually, but in order to do it, it was AOMDV patch, which was a hurdle. So I made comment over PT_AOMDV, wherever it was in packet.h and other related files like cmu-trace. Now example zrp script is running, but in trace it is showing AOMDV instead of ZRP. Can you suggest the solution?
|
1 Attachment(s)
# 8 .
@bitsandeep : Probably tell what you are doing / trying to do ! Looks like you want to add two patches at the same time ? AOMDV + ZRP ? ZRP : Meant for ns-2.33 . AOMDV : This code is for ns-2.33 → NS-2.33-AOMDV-Multiple-Interface.patch → http://205.196.123.186/jo1im19xaq0g/...nterface.patch Quote:
! The most common is that one patch cancels the previous patching ! ... But most often it's easy to combine two »extra protocols« : Write new patch / files. ... So which aomdv is it about ? A link please. . |
#9
I don't want to add two patches. In fact AOMDV patch is already there in Ns-2.34. I have made a fresh installation of NS-2 and tried to patch ZRP. Automatically it didn't work, since some hunks were failed during patching. So I did the steps mentioned in ZRP patch file, manually in files like packet.h, cmu-trace.cc and other files mentioned in the patch. Now during manual patching I found AOMDV in packet.h particularly this line: static const packet_t PT_AOMDV = 61 so i had commented the above line and inserted the following line as mentioned in patch static const packet_t PT_ZRP = 61 Likewise at all other related places, I had inserted the ZRP lines and commented the AOMDV lines. ZRP example script executed finally. But in trace it is showing AOMDV instead of ZRP. This is the case. Now please let me know: 1. Should I change the line in packet.h as static const packet_t PT_ZRP = 62 - will it work 2. Whether there is any other file, where AOMDV is still alive and affecting the trace, 3. Can we have AOMDV and ZRP simultaneously in NS-2.34? |
# 10 .
The ZRP code is for ns-2.33 . Do not expect it to work with other versions. Latest install instructions, with a new "patch package" zrp-ns233-patching.tar.gz, .. to make it impossible to fail : http://www.linuxquestions.org/questi...-4175495477/#2 - |
All times are GMT -5. The time now is 02:56 PM. |