Have you tried to "reduce" the AOMDV to the AODV disabling the multi- path feature?
PS I've started the thread for you. Check here to subscribe http:// www.isi.edu/nsnam/ns/ns-users-list.html ----------------------------------------- Marcello Caleffi Department of Electronic and Telecommunication Engineering University of Naples "Federico II" 21 Claudio street - 80125 Naples ITALY Tel +39-(0)81-7683810. Fax +39-(0)81-7683149 http://wpage.unina.it/marcello.caleffi/ Il giorno 11/apr/08, alle ore 11:34, Siddharth Khimsara ha scritto: > Hi Marcello.. > Thats a great idea.. How do i start a thread on the mailing list? Do i > need to register anywhere? > > I have made all possible changes in aomdv.h but havent got much > difference in the packet loss.. I even bypassed the disjointness logic > in the code to find all possible paths but that didnt help either. > > Sid > > On 4/11/08, Marcello Caleffi <[EMAIL PROTECTED]> wrote: >> Siddharth, >> I've noted the same in my simulations. Have you looked at the >> aomdv.h? There are some parameters to set. Just one: to use link >> disjoint or node disjoint paths. >> I think that we should look at this. >> >> PS maybe we should continue this conversation on the ns2 mailing >> list? >> >> Il giorno 09/apr/08, alle ore 03:55, Siddharth Khimsara ha scritto: >>> Hi Marcello, >>> >>> I have been running the simulations on the new code and I tried >>> comparing it with pure AODV. I can see that the packeloss is much >>> more in AOMDV (16%) than pure AODV (3%). I was wondering what that >>> is so. Could you give me some idea as to what that must happen? >>> I am currently trying to get results similar to the AOMDV journal >>> paper by Samir Das and Mahesh Marina but I am not able to >>> understand whats going wrong in my simulations. I am using the >>> exact scenarios as described in their paper. >>> I also saw that you updated your website by including the >>> aomdv.tcl script. Thanks for the same. >>> >>> Awaiting your reply. >>> Thanks in advance. >>> >>> Siddharth >>> >>> On Sat, Apr 5, 2008 at 1:39 PM, Siddharth Khimsara >>> <[EMAIL PROTECTED]> wrote: >>> Hi Marcello, >>> >>> Thanks for your reply. >>> I did figure that out when I saw the difference between the old and >>> the new aomdv.diff files. However, I am not able to figure out >>> why the packetloss has increased. In fact I have kept all the other >>> parameters same (as in aomdv.h) . >>> >>> Cheers, >>> Siddharth >>> >>> >>> On Sat, Apr 5, 2008 at 5:17 AM, Marcello Caleffi >>> <[EMAIL PROTECTED]> wrote: >>> Siddharth, >>> the difference between the last and the previous patch is that in >>> the latter I forgot to initialize the ifqueue (AOMDVifqueue) object >>> in the mobilenode.tcl. (tcl/lib/ns-mobilenode.tcl): >>> >>> diff -ruN ./ns-2.32/tcl/lib/ns-mobilenode.tcl ./ns-2.32 modified/ >>> tcl/lib/ns-mobilenode.tcl >>> --- ./ns-2.32/tcl/lib/ns-mobilenode.tcl 2007-01-30 >>> 06:00:51.000000000 +0100 >>> +++ ./ns-2.32 modified/tcl/lib/ns-mobilenode.tcl 2008-04-04 >>> 12:26:12.000000000 +0200 >>> @@ -186,6 +186,14 @@ >>> [$self set imep_(0)] rtagent $agent >>> } >>> >>> + # Begin Marcello Caleffi, <[EMAIL PROTECTED]>, 08-04-01 >>> + # Special processing for AOMDV >>> + set aomdvonly [string first "AOMDV" [$agent info class]] >>> + if {$aomdvonly != -1 } { >>> + $agent if-queue [$self set ifq_(0)] ;# ifq between LL and MAC >>> + } >>> + # End Marcello Caleffi, <[EMAIL PROTECTED]>, 08-04-01 >>> + >>> # Special processing for AODV >>> set aodvonly [string first "AODV" [$agent info class]] >>> if {$aodvonly != -1 } { >>> >>> This could help you? >>> >>> >>> Il giorno 05/apr/08, alle ore 00:05, Siddharth Khimsara ha scritto: >>> >>>> Hi Marcello, >>>> >>>> The code is working fine now. No segmentation fault. >>>> However, I just ran a 100 node (1000x1000 area) - Random Waypoint >>>> model, 50 CBR/UDP connections of 1 packets/sec and mean node >>>> speed 10 m/s and I see a increase in data packet loss from 28% >>>> (when i used the old AOMDV code) to 37% (when i use the new >>>> code) .. >>>> since I had commented the part where it drops HELLO packets in >>>> nb_delete() , I did the same in the new code, but it doesn't >>>> help. :( anyway..i will figure out what the problem is. :) >>>> hey ..btw... the route table dump function is an awesome addition. >>>> I had added a similar function when I was using Ahmad Kayyat's >>>> code for ns 2.29 :) .. >>>> >>>> Regards, >>>> Siddharth >>>> >>>> On Fri, Apr 4, 2008 at 1:46 PM, Siddharth Khimsara >>>> <[EMAIL PROTECTED]> wrote: >>>> Hi Marcello, >>>> >>>> thanks a lot. I will try it right now and let u know immediately :) >>>> >>>> Regards, >>>> Siddharth >>>> >>>> On Fri, Apr 4, 2008 at 1:38 PM, Marcello Caleffi >>>> <[EMAIL PROTECTED]> wrote: >>>> I upload the new one today. >>>> Try the last one and let me know what happens without commenting >>>> anything! >>>> >>>> >>>> Il giorno 04/apr/08, alle ore 19:21, Siddharth Khimsara ha scritto: >>>> >>>>> Hi Marcello, >>>>> >>>>> Thanks for your quick reply. >>>>> I did use the most recent patch as you mentioned. I patched it >>>>> again yesterday. However I am still having the same problems. :( >>>>> >>>>> For now I have commented that part of the nb_delete() function >>>>> because it is just concerned with dropping the HELLO packets. >>>>> >>>>> Regards, >>>>> Siddharth >>>>> >>>>> On Fri, Apr 4, 2008 at 5:28 AM, Marcello Caleffi >>>>> <[EMAIL PROTECTED]> wrote: >>>>> Hi Siddharth, >>>>> try to use the last patch available on my web site. The old one >>>>> lacked of some instructions in the mobilenode.tcl. >>>>> >>>>> Let me know if everything will gone ok. >>>>> >>>>> >>>>> >>>>> ----------------------------------------- >>>>> >>>>> Marcello Caleffi >>>>> Department of Electronic and Telecommunication Engineering >>>>> University of Naples "Federico II" >>>>> 21 Claudio street - 80125 Naples ITALY >>>>> Tel +39-(0)81-7683810. Fax +39-(0)81-7683149 >>>>> http://wpage.unina.it/marcello.caleffi/ >>>>> >>>>> >>>>> Il giorno 03/apr/08, alle ore 22:04, Siddharth Khimsara ha >>>>> scritto: >>>>> >>>>>> Hi Marcello, >>>>>> >>>>>> I found the place where it is giving a Segmentation Fault. It >>>>>> happens in nb_delete() function inside the AOMDVIfqueue->filter >>>>>> () function. Could you please tell me what could be the problem? >>>>>> >>>>>> Any help would be really appreciated.. >>>>>> Thanks in advance :) >>>>>> >>>>>> Regards, >>>>>> Siddharth >>>>>> >>>>>> On Wed, Apr 2, 2008 at 8:59 PM, Siddharth Khimsara >>>>>> <[EMAIL PROTECTED]> wrote: >>>>>> Hi Marcello, >>>>>> >>>>>> This is with reference to our last conversation regarding your >>>>>> version of AOMDV for ns 2.32. I have successfully patched it. >>>>>> However, do I need to make any specific changes in my simulation >>>>>> TCL Script to be able to run it? I am getting this weird >>>>>> Segmentation Fault. >>>>>> ..... >>>>>> SORTING LISTS DONE >>>>>> sendError: node=1 >>>>>> Segmentation fault. >>>>>> >>>>>> I am using my TCL file to read a scenario file generated using >>>>>> setdest utility in ns-2.32/indep-utils/cmu-scen-gen/ and a >>>>>> connection file of 50 CBR/UDP connections using cbrgen.tcl in >>>>>> the same folder. >>>>>> >>>>>> I am actually trying to simulate the exact senarios as mentioned >>>>>> in the AOMDV paper by Samir Das. >>>>>> >>>>>> I would be really thankful if you could just let me know how to >>>>>> get rid of this segmentation fault. I have attached my TCL >>>>>> script, the movement senario (random waypoint model) and the >>>>>> connection pattern file for your reference. >>>>>> >>>>>> Thanks in advance. Awaiting your reply. >>>>>> >>>>>> Regards, >>>>>> Siddharth >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Mar 11, 2008 at 1:44 AM, Marcello Caleffi >>>>>> <[EMAIL PROTECTED]> wrote: >>>>>> Hi Sid, >>>>>> thanks for informing me. >>>>>> I've patched the patch :-) or at least I hope it. You can >>>>>> download from my site. >>>>>> Please let me know if it's all right. >>>>>> >>>>>> Good work, Marcello. >>>>>> >>>>>> >>>>>> >>>>>> Il giorno 11/mar/08, alle ore 02:45, Siddharth Khimsara ha >>>>>> scritto: >>>>>> >>>>>>> Hi Marcello, >>>>>>> I tried patching AOMDV into ns2 2.32. However, it patches the >>>>>>> Makefiles properly but when it comes to aomdv.h it gives this >>>>>>> maformed patch error. >>>>>>> I tired renamed the aodv folder as aomdv but it didn't help >>>>>>> either. >>>>>>> Please help :) >>>>>>> >>>>>>> Regards, >>>>>>> Siddharth >>>>>>> >>>>>>> >>>>>>> [EMAIL PROTECTED]:~/ns2-installation/ns-allinone-2.32/ns-2.32 >>>>>>> $ patch -p2 < ./aomdv.diff >>>>>>> patching file Makefile >>>>>>> Reversed (or previously applied) patch detected! Assume -R? >>>>>>> [n] y >>>>>>> patching file Makefile.in >>>>>>> The next patch would create the file aomdv/aomdv.cc, >>>>>>> which already exists! Assume -R? [n] y >>>>>>> patching file aomdv/aomdv.cc >>>>>>> patch: **** malformed patch at line 1946: diff -ruN ./ns-2.32/ >>>>>>> aomdv/aomdv.h ./ns-2.32-aomdv/aomdv/aomdv.h >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Feb 29, 2008 at 2:18 AM, Siddharth Khimsara >>>>>>> <[EMAIL PROTECTED]> wrote: >>>>>>> Hi Marcello, >>>>>>> >>>>>>> Thanks for the quick response. :) >>>>>>> i will definitely post that question on the mailing list. >>>>>>> >>>>>>> Regards, >>>>>>> Siddharth >>>>>>> >>>>>>> >>>>>>> On Fri, Feb 29, 2008 at 12:25 AM, Marcello Caleffi >>>>>>> <[EMAIL PROTECTED]> wrote: >>>>>>> Siddharth, >>>>>>> I've update the web page, 'cause there was an error on that >>>>>>> line (wget ..). >>>>>>> The second question can be posted on ns2 mailing list. >>>>>>> >>>>>>> Regards, Marcello. >>>>>>> >>>>>>> ----------------------------------------- >>>>>>> >>>>>>> Marcello Caleffi >>>>>>> Department of Electronic and Telecommunication Engineering >>>>>>> University of Naples "Federico II" >>>>>>> 21 Claudio street - 80125 Naples ITALY >>>>>>> Tel +39-(0)81-7683810. Fax +39-(0)81-7683149 >>>>>>> http://wpage.unina.it/marcello.caleffi/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> Il giorno 29/feb/08, alle ore 01:32, Siddharth Khimsara ha >>>>>>> scritto: >>>>>>> >>>>>>>> Hi Marcello, >>>>>>>> >>>>>>>> Thanks for your response. Really appreciate it :) >>>>>>>> I am using Ubuntu 7.10. I tried following the instructions on >>>>>>>> how to install AOMDV code in ns2. 2.32 but it gave me this >>>>>>>> error >>>>>>>> >>>>>>>> >>>>>>>> [EMAIL PROTECTED]:~/ns2-installation/ns-allinone-2.32/ >>>>>>>> ns-2.32$ wget http://wpage.unina.it/marcello.caleffi/ns-2/ >>>>>>>> aomdv.diff >>>>>>>> >>>>>>>> --16:28:27-- http://wpage.unina.it/marcello.caleffi/ns-2/ >>>>>>>> aomdv.diff >>>>>>>> => `aomdv.diff' >>>>>>>> Resolving wpage.unina.it... MailScanner ha rilevato un >>>>>>>> possibile tentativo di frode proveniente da "192.132.34.19" >>>>>>>> MailScanner warning: numerical links are often malicious: >>>>>>>> 192.132.34.19 >>>>>>>> Connecting to wpage.unina.it|192.132.34.19|:80... connected. >>>>>>>> HTTP request sent, awaiting response... 404 Not Found >>>>>>>> 16:28:27 ERROR 404: Not Found. >>>>>>>> >>>>>>>> Please let me know what is wrong >>>>>>>> >>>>>>>> I had yet another question. I have actually successfully >>>>>>>> ported AOMDV into ns2 2.29 like mentioned by Ahmad Khayyat. >>>>>>>> However I find that when I use UDP, AOMDV protocol just >>>>>>>> blindly drops the packets. Is there any restriction or >>>>>>>> something. Ideally the routing protocol should not care what >>>>>>>> kind of transport layer packets its handling..but here i am >>>>>>>> foxed as to why this is happening. I was wondering if you >>>>>>>> could advice me on this. >>>>>>>> >>>>>>>> Looking forward to your response. >>>>>>>> >>>>>>>> Cheeers, >>>>>>>> Siddharth Khimsara >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Feb 27, 2008 at 5:05 AM, Marcello Caleffi >>>>>>>> <[EMAIL PROTECTED]> wrote: >>>>>>>> Hi to everyone, >>>>>>>> here http://wpage.unina.it/marcello.caleffi/ns2/aomdv.html you >>>>>>>> can find my personal 2-cents-AOMDV-code for the current >>>>>>>> release (2.32). >>>>>>>> I've updated an older version of AOMDV code, by merging it >>>>>>>> with the current AODV code and adding some personal >>>>>>>> contributes. I don't remember who gave me the original code; >>>>>>>> if someone knows who are the autors, please let me know. This >>>>>>>> code, differently from the original one, add the AOMDV as a >>>>>>>> new protocol in the ns tree and each code line which "adds the >>>>>>>> M to AODV" is indicated. Clearly, there is no guarantee about >>>>>>>> this code, however I've used it in the last year for my >>>>>>>> research activities without any troubles. >>>>>>>> Feedbacks and bug reports are welcome. >>>>>>>> >>>>>>>> Best regards, Marcello. >>>>>>>> >>>>>>>> ----------------------------------------- >>>>>>>> >>>>>>>> Marcello Caleffi >>>>>>>> Department of Electronic and Telecommunication Engineering >>>>>>>> University of Naples "Federico II" >>>>>>>> 21 Claudio street - 80125 Naples ITALY >>>>>>>> Tel +39-(0)81-7683810. Fax +39-(0)81-7683149 >>>>>>>> http://wpage.unina.it/marcello.caleffi/ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Il giorno 22/feb/08, alle ore 23:55, Siddharth Khimsara ha >>>>>>>> scritto: >>>>>>>> >>>>>>>>> Hi Marcello, >>>>>>>>> >>>>>>>>> I am Masters in Electrical Engg student from San Diego State >>>>>>>>> University. I am currently working on multpath wireless ad >>>>>>>>> hoc routing and as a part of my research I am trying to >>>>>>>>> integrate AOMDV code into ns 2.31. I was going through the >>>>>>>>> posts on ns2 in mailman.isi.edu and I found your post on >>>>>>>>> it. I was wondering if you could please help me with my >>>>>>>>> doubts regarding porting AOMDV code to 2.31 >>>>>>>>> >>>>>>>>> googling for AOMDV code, I found two different sets of code >>>>>>>>> for AOMDV. One is from Mahesh Marina which is actually for >>>>>>>>> ns 2.21, so its the older version. >>>>>>>>> http://www.icis.ntu.edu.sg/wagio/campus/research/codes/aomdv- >>>>>>>>> code-ns2.tar.tar >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> The other one i found is for ns 2.29 which is actually the >>>>>>>>> above code ported to 2.29 by Ahmad Khayyat but he claims >>>>>>>>> that it is not the complete port. >>>>>>>>> http://www.ccse.kfupm.edu.sa/~akhayyat/aomdv-ns-2.29.zip >>>>>>>>> >>>>>>>>> I have the following doubts regarding this. >>>>>>>>> 1. Should i be using Ahmad's code to integrate into 2.31 or >>>>>>>>> should I use the original code (the first one). Which one did >>>>>>>>> you use? >>>>>>>>> 2. If possible, could you walk me briefly thru the process of >>>>>>>>> porting the AOMDV code into 2.31 the way you did it. >>>>>>>>> 3. There is an aodv.tcl file in the original /aodv folder in >>>>>>>>> ns2 . I have been trying to figure out the purpose of this >>>>>>>>> file. Do I have to copy those procedures into my tcl script >>>>>>>>> or does it get called from .cc files? I have been trying to >>>>>>>>> figure this out for a long time but I am getting nowhere. >>>>>>>>> >>>>>>>>> Thanks in advance :) looking forward to your reply. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> siddharth >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Hello Macello, >>>>>>>>> >>>>>>>>> Can you please tell me how did you patch the AOMDV code with >>>>>>>>> the AODV in >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ns2.3? I would very much appreciate if you can give me some >>>>>>>>> tips on that! >>>>>>>>> :-) >>>>>>>>> >>>>>>>>> Also, I have bumped into problems with low packet delivery >>>>>>>>> ratio of AODV in >>>>>>>>> ns2.30. I have tested the AODV when its link layer detection >>>>>>>>> is on and off. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> But both of them give me pretty low ratio when the number of >>>>>>>>> CBR source is >>>>>>>>> only 20 to 30. Would you happen to know the reason why this >>>>>>>>> is happening? >>>>>>>>> >>>>>>>>> Really looking forward to your reply. >>>>>>>>> Thank you very much in advance, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Martin >>>>>>>>> >>>>>>>>> marcello.caleffi wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> I'm working on AOMDV in order to compare with ATR. >>>>>>>>>> Currently, I'm patching the AOMDV code with the AODV >>>>>>>>> ns-2.31 one >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> (each single function :-| ). In this way one could compare >>>>>>>>>> the >>>>>>>>>> results of AOMDV simulations with which of another protocol >>>>>>>>> (say ATR, >>>>>>>>>> DART and AODV) implemented in ns-2.31. Then I will change >>>>>>>>> every >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> reference to AODV in AOMDV code, in order to could mantain >>>>>>>>> both the >>>>>>>>>> protocols in the same ns folder structure. >>>>>>>>>> I think you could not simply put the older AOMDV code in >>>>>>>>> the ns >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> folder structure, aso if it looks working. This is my >>>>>>>>>> opinion. >>>>>>>>>> >>>>>>>>>> Best regards, Marcello. >>>>>>>>>> >>>>>>>>>> ----------------------------------------- >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> Marcello Caleffi, Ph.D. student >>>>>>>>>> Department of Electronic and Telecommunication Engineering >>>>>>>>>> University of Naples "Federico II" >>>>>>>>>> Via Claudio 21 >>>>>>>>>> 80125 Naples ITALY >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> http://wpage.unina.it/marcello.caleffi/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Hello everyone in ns2, >>>>>>>>>>> >>>>>>>>>>> I am currently working on a load balancing strategy on the >>>>>>>>> AOMDV >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>> protocol. I'm using ns2 and I am not able to find the >>>>>>>>> AOMDV (Ad-hoc >>>>>>>>>>> Multipath Distance Vector) source code within the ns2 >>>>>>>>> directory? After >>>>>>>>>>> hours of googling, I managed to find a copy of AOMDV >>>>>>>>> source code for >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>> older version of ns2. >>>>>>>>>>> http://www.icis.ntu.edu.sg/wagio/campus/research/codes/ >>>>>>>>> aomdv-code- >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>> ns2.tar.tar >>>>>>>>> >>>>>>>>>>> However, the installation steps provide with the source code >>>>>>>>>>> require me >>>>>>>>>>> to install an older version of AODV onto the new ns2 and >>>>>>>>>>> some >>>>>>>>>>> overriding >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>> of ns2 original source code. Does anybody able to install >>>>>>>>> AOMDV into >>>>>>>>>>> ns2.3x ? I will be very grateful if you can teach me how >>>>>>>>> to do it >>>>>>>>>>> correctly. >>>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>> Thanks in advance. >>>>>>>>>>> Martin >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> View this message in context: http://www.nabble.com/AOMDV- >>>>>>>>> implementation-for-ns2.30-tf3657075.html#a10287090 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Sent from the ns-users mailing list archive at Nabble.com. >>>>>>>>> >>>>>>>>> >>>>>>>>> ==================================== >>>>>>>>> View my profile on LinkedIn.com >>>>>>>>> <http://www.linkedin.com/in/skhimsara> >>>>>>>>> ==================================== >>>>>>>>> >>>>>>>>> "This e-mail and any files transmitted with it are for the >>>>>>>>> sole use of the intended recipient(s) and may contain >>>>>>>>> confidential and privileged information. >>>>>>>>> If you are not the intended recipient, please contact the >>>>>>>>> sender by reply e-mail and destroy all copies of the original >>>>>>>>> message. >>>>>>>>> Any unauthorized review, use, disclosure, dissemination, >>>>>>>>> forwarding, printing or copying of this email or any action >>>>>>>>> taken in reliance on this e-mail is strictly >>>>>>>>> prohibited and may be unlawful." >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ==================================== >>>>>>>> View my profile on LinkedIn.com >>>>>>>> <http://www.linkedin.com/in/skhimsara> >>>>>>>> ==================================== >>>>>>>> >>>>>>>> "This e-mail and any files transmitted with it are for the >>>>>>>> sole use of the intended recipient(s) and may contain >>>>>>>> confidential and privileged information. >>>>>>>> If you are not the intended recipient, please contact the >>>>>>>> sender by reply e-mail and destroy all copies of the original >>>>>>>> message. >>>>>>>> Any unauthorized review, use, disclosure, dissemination, >>>>>>>> forwarding, printing or copying of this email or any action >>>>>>>> taken in reliance on this e-mail is strictly >>>>>>>> prohibited and may be unlawful." >>>>>>>> >>>>>>>> Save the environment. Please don't print this email unless you >>>>>>>> really need to. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ==================================== >>>>>>> View my profile on LinkedIn.com >>>>>>> <http://www.linkedin.com/in/skhimsara> >>>>>>> ==================================== >>>>>>> >>>>>>> "This e-mail and any files transmitted with it are for the sole >>>>>>> use of the intended recipient(s) and may contain confidential >>>>>>> and privileged information. >>>>>>> If you are not the intended recipient, please contact the >>>>>>> sender by reply e-mail and destroy all copies of the original >>>>>>> message. >>>>>>> Any unauthorized review, use, disclosure, dissemination, >>>>>>> forwarding, printing or copying of this email or any action >>>>>>> taken in reliance on this e-mail is strictly >>>>>>> prohibited and may be unlawful." >>>>>>> >>>>>>> Save the environment. Please don't print this email unless you >>>>>>> really need to. >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ==================================== >>>>>>> View my profile on LinkedIn.com >>>>>>> <http://www.linkedin.com/in/skhimsara> >>>>>>> ==================================== >>>>>>> >>>>>>> "This e-mail and any files transmitted with it are for the sole >>>>>>> use of the intended recipient(s) and may contain confidential >>>>>>> and privileged information. >>>>>>> If you are not the intended recipient, please contact the >>>>>>> sender by reply e-mail and destroy all copies of the original >>>>>>> message. >>>>>>> Any unauthorized review, use, disclosure, dissemination, >>>>>>> forwarding, printing or copying of this email or any action >>>>>>> taken in reliance on this e-mail is strictly >>>>>>> prohibited and may be unlawful." >>>>>>> >>>>>>> Save the environment. Please don't print this email unless you >>>>>>> really need to. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ==================================== >>>>>> View my profile on LinkedIn.com >>>>>> <http://www.linkedin.com/in/skhimsara> >>>>>> ==================================== >>>>>> >>>>>> "This e-mail and any files transmitted with it are for the sole >>>>>> use of the intended recipient(s) and may contain confidential >>>>>> and privileged information. >>>>>> If you are not the intended recipient, please contact the sender >>>>>> by reply e-mail and destroy all copies of the original message. >>>>>> Any unauthorized review, use, disclosure, dissemination, >>>>>> forwarding, printing or copying of this email or any action >>>>>> taken in reliance on this e-mail is strictly >>>>>> prohibited and may be unlawful." >>>>>> >>>>>> Save the environment. Please don't print this email unless you >>>>>> really need to. >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ==================================== >>>>>> View my profile on LinkedIn.com >>>>>> <http://www.linkedin.com/in/skhimsara> >>>>>> ==================================== >>>>>> >>>>>> "This e-mail and any files transmitted with it are for the sole >>>>>> use of the intended recipient(s) and may contain confidential >>>>>> and privileged information. >>>>>> If you are not the intended recipient, please contact the sender >>>>>> by reply e-mail and destroy all copies of the original message. >>>>>> Any unauthorized review, use, disclosure, dissemination, >>>>>> forwarding, printing or copying of this email or any action >>>>>> taken in reliance on this e-mail is strictly >>>>>> prohibited and may be unlawful." >>>>>> >>>>>> Save the environment. Please don't print this email unless you >>>>>> really need to. >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> >>>>> >>>>> ==================================== >>>>> View my profile on LinkedIn.com >>>>> <http://www.linkedin.com/in/skhimsara> >>>>> ==================================== >>>>> >>>>> "This e-mail and any files transmitted with it are for the sole >>>>> use of the intended recipient(s) and may contain confidential and >>>>> privileged information. >>>>> If you are not the intended recipient, please contact the sender >>>>> by reply e-mail and destroy all copies of the original message. >>>>> Any unauthorized review, use, disclosure, dissemination, >>>>> forwarding, printing or copying of this email or any action taken >>>>> in reliance on this e-mail is strictly >>>>> prohibited and may be unlawful." >>>>> >>>>> Save the environment. Please don't print this email unless you >>>>> really need to. >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> >>>> ==================================== >>>> View my profile on LinkedIn.com >>>> <http://www.linkedin.com/in/skhimsara> >>>> ==================================== >>>> >>>> "This e-mail and any files transmitted with it are for the sole >>>> use of the intended recipient(s) and may contain confidential and >>>> privileged information. >>>> If you are not the intended recipient, please contact the sender >>>> by reply e-mail and destroy all copies of the original message. >>>> Any unauthorized review, use, disclosure, dissemination, >>>> forwarding, printing or copying of this email or any action taken >>>> in reliance on this e-mail is strictly >>>> prohibited and may be unlawful." >>>> >>>> Save the environment. Please don't print this email unless you >>>> really need to. >>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> >>>> ==================================== >>>> View my profile on LinkedIn.com >>>> <http://www.linkedin.com/in/skhimsara> >>>> ==================================== >>>> >>>> "This e-mail and any files transmitted with it are for the sole >>>> use of the intended recipient(s) and may contain confidential and >>>> privileged information. >>>> If you are not the intended recipient, please contact the sender >>>> by reply e-mail and destroy all copies of the original message. >>>> Any unauthorized review, use, disclosure, dissemination, >>>> forwarding, printing or copying of this email or any action taken >>>> in reliance on this e-mail is strictly >>>> prohibited and may be unlawful." >>>> >>>> Save the environment. Please don't print this email unless you >>>> really need to. >>> >>> >>> >>> >>> -- >>> >>> >>> >>> >>> ==================================== >>> View my profile on LinkedIn.com >>> <http://www.linkedin.com/in/skhimsara> >>> ==================================== >>> >>> "This e-mail and any files transmitted with it are for the sole use >>> of the intended recipient(s) and may contain confidential and >>> privileged information. >>> If you are not the intended recipient, please contact the sender by >>> reply e-mail and destroy all copies of the original message. >>> Any unauthorized review, use, disclosure, dissemination, >>> forwarding, printing or copying of this email or any action taken >>> in reliance on this e-mail is strictly >>> prohibited and may be unlawful." >>> >>> Save the environment. Please don't print this email unless you >>> really need to. >>> >>> >>> >>> -- >>> >>> >>> >>> >>> ==================================== >>> View my profile on LinkedIn.com >>> <http://www.linkedin.com/in/skhimsara> >>> ==================================== >>> >>> "This e-mail and any files transmitted with it are for the sole use >>> of the intended recipient(s) and may contain confidential and >>> privileged information. >>> If you are not the intended recipient, please contact the sender by >>> reply e-mail and destroy all copies of the original message. >>> Any unauthorized review, use, disclosure, dissemination, >>> forwarding, printing or copying of this email or any action taken >>> in reliance on this e-mail is strictly >>> prohibited and may be unlawful." >>> >>> Save the environment. Please don't print this email unless you >>> really need to. >> >> > > -- > Sent from Gmail for mobile | mobile.google.com > > > > > > ==================================== > View my profile on LinkedIn.com > <http://www.linkedin.com/in/skhimsara> > ==================================== > > "This e-mail and any files transmitted with it are for the sole use of > the intended recipient(s) and may contain confidential and privileged > information. > If you are not the intended recipient, please contact the sender by > reply e-mail and destroy all copies of the original message. > Any unauthorized review, use, disclosure, dissemination, forwarding, > printing or copying of this email or any action taken in reliance on > this e-mail is strictly > prohibited and may be unlawful." > > Save the environment. Please don't print this email unless you > really need to.
