How can I add olsr protocol to ns2 ? please help me
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
it works Thank you so much.
After executing the .tcl file, I have two files .tr and .nam files. How do I know the results of the execution?
can you help me please?
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,516
Rep:
Re #3.
"NAM file is a separate program which is distributed with NS2 simulator to read an input file and draw the network events graphically. It is used to visualize the progression of packets through the Network."
When I execute the tcl file in the olsr protocol and specify the number of nodes to 80 or more, it shows the following error:
Segmentation fault (core dumped)
What is the solution to this problem? Please help me.. thank you very much
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,516
Rep:
Re #6.
`Segmentation faultī happens more often when ns2 has been built with an "after year 2020 OS".
Critical code / old code is suggested built with an older ns2 friendly OS such as CentOS 6.10 .
`Segmentation faultī can also be caused by a too complex simulation.tcl .
Or by expecting an impossible situation.tcl to run.
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,516
Rep:
Re #6
`Segmentation faultī
I get Segmentation fault with 80 nodes (Not with 50 nodes)
The example was DSR__routingprotocolforFANET.tcl edited to
New file name = o-80-OLSR__routingprotocolforFANET.tcl
Code:
set val(adhocRouting) OLSR
set val(nn) 80
set val(stop) 50.0
.... but the trace files have reached reasonable sizes, so `Segmentation faultī may be ignored.
50 nodes : o-50-OLSR__routingprotocolforFANET.tcl
Code:
set val(adhocRouting) OLSR
set val(nn) 50
set val(stop) 100.0
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,516
Rep:
Re #10
The supplied file is setdest3D, therefore the command starts with ./setdest3D
.... Alternatively you can rename to setdest3d and do ./setdest3d -options
I create a 3D movement But when I run the tcl file, the following error appears:
Loading scenario file...
Load complete...
Starting Simulation...
ns: _o14 setdest3d 148.377446425732 445.558487129436 441.150568136787 50.000000000000:
(_o14 cmd line 1)
invoked from within
"_o14 cmd setdest3d 148.377446425732 445.558487129436 441.150568136787 50.000000000000"
invoked from within
"catch "$self cmd $args" ret"
invoked from within
"if [catch "$self cmd $args" ret] {
set cls [$self info class]
global errorInfo
set savedInfo $errorInfo
error "error when calling class $cls: $args" $..."
(procedure "_o14" line 2)
(SplitObject unknown line 2)
invoked from within
"_o14 setdest3d 148.377446425732 445.558487129436 441.150568136787 50.000000000000"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.