How to update the ns3.12 version to ns3.19?

[abdelwahed berguiga]

Currently, I am working on ns3.12 version which support Proxy Mobile IPv6 (PMIPv6) mobility protocol. 

I want to merge this version with the  ns3.19 version which supports 6lowpan protocol in order to test it with the PMIPv6 mobility protocol. 

Have you any idea how can I do it?

Thank you.

[AhlEM AhlAM]

i used ns3.15 and i have to use ns3.19
in case you have found solution to upgrade ns3 can please share it

many thanks

[AhlEM AhlAM]

i use Ubuntu OS

i'm ns3 rookie .... i have no modification at all

many thanks

Best regards

2014-05-30 19:11 GMT+01:00 Tommaso Pecorella <tomm...@gmail.com>:

Hi,

the howto is here: http://www.nsnam.org/wiki/User_FAQ#Upgrading_ns-3

However, the howto only considers the upgrade from 3.17 onward. For older ns-3 releases (heavily deprecated) things are more complex, and it all depends on the modifications the user did.

There are the following cases:

1. The user is "just" using ns-3. No modifications have been made under "src" and no custom scrips have been made.
2. The user is using ns-3. No modifications have been made under "src" but custom scrips have been made.
3. The user did modify the ns-3 "src" folder.

Case 1: trash your old ns-3 and do a clean install.

Case 2: save your scripts, trash your old ns-3 and do a clean install. Then move your scripts in the scratch directory and compile. Errors will be thrown, fix them.

Case 3: good luck.

In case 2, the errors thrown by the scrips will be mostly about include directives. The module names have been changed, so you'll need to find the new ones. It's easer than one may expect: "#include "ns3/csma-module.h" will include all the headers needed to use csma. It's much simpler than before.

In case 3, the problem is that the modifications to the src files and/or the custom modules may not work at all. From 3.12 or 3.15 a LOT of things have been changed, so upgrading old modules may be a real pain. The best suggestion is to take a deep breath, a lot of beers (enough for a week) and migrate the old modules one by one. You can also check if  the module has been updated by someone, maybe you're lucky enough.

In any case, I have to repeat myself. Using 2.3.years old software is definitely a bad idea. If changes have been made, there's a reason.

Good luck,

T.

--
You received this message because you are subscribed to a topic in the Google Groups "ns-3-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ns-3-users/PpagKDHV0nY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ns-3-users+...@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at http://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/d/optout.

[AhlEM AhlAM]

i delete ns3 folder to uninstall it
and download ns3.19

and move to forlder of ns3 and follow those steps
 
tar xjf ns-allinone-3.13.tar.bz2

Build the ns-3and configure with waf

./build.py
./waf distclean
./waf configure --enable-examples --enable-tests
./waf build

 Now test

./test.py

 To run a file it must be in the /scratch folder (example ../scratch/test.cc)

./waf -run scratch/test

and it seems it works fine

many thanks
Best regards

[Tommaso Pecorella]

Hi,

the howto is here: http://www.nsnam.org/wiki/User_FAQ#Upgrading_ns-3

However, the howto only considers the upgrade from 3.17 onward. For older ns-3 releases (heavily deprecated) things are more complex, and it all depends on the modifications the user did.

There are the following cases:

1. The user is "just" using ns-3. No modifications have been made under "src" and no custom scrips have been made.
2. The user is using ns-3. No modifications have been made under "src" but custom scrips have been made.
3. The user did modify the ns-3 "src" folder.

Case 1: trash your old ns-3 and do a clean install.

Case 2: save your scripts, trash your old ns-3 and do a clean install. Then move your scripts in the scratch directory and compile. Errors will be thrown, fix them.

Case 3: good luck.

In case 2, the errors thrown by the scrips will be mostly about include directives. The module names have been changed, so you'll need to find the new ones. It's easer than one may expect: "#include "ns3/csma-module.h" will include all the headers needed to use csma. It's much simpler than before.

In case 3, the problem is that the modifications to the src files and/or the custom modules may not work at all. From 3.12 or 3.15 a LOT of things have been changed, so upgrading old modules may be a real pain. The best suggestion is to take a deep breath, a lot of beers (enough for a week) and migrate the old modules one by one. You can also check if  the module has been updated by someone, maybe you're lucky enough.

In any case, I have to repeat myself. Using 2.3.years old software is definitely a bad idea. If changes have been made, there's a reason.

Good luck,

T.

On Friday, May 30, 2014 1:21:02 AM UTC+2, AhlEM AhlAM wrote:

[Segue Diallo]

Le jeudi 23 janvier 2014 15:01:51 UTC+1, abdelwahed berguiga a écrit :

[Segue Diallo]

This is an error on my part

--
Posting to this group should follow these guidelines https://www.nsnam.org/wiki/Ns-3-users-guidelines-for-posting
---
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.

To post to this group, send email to ns-3-...@googlegroups.com.

Visit this group at https://groups.google.com/group/ns-3-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ns-3-users/0d8cae1d-4c42-4c6b-9c70-1301db2bfc08%40googlegroups.com.