Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Cbr150 is a CBR file and scenario file is also correct. For both the files AODV ,DSR are running .
Could you please tell me what could be the reason of killed process.
Thanks definitely I will look into the examples.
I tried nn200-200wireless-gpsr.tcl with cbr200 and nn200. It creates the .tr file but there are no gpsr packets. then i copied first 2 lines from cbr100.tcl i.e. "ragent turnon" into cbr200. Its running successfully and creating gpsr packets also.
I also tried nn200-200wireless-gpsr.tcl with my cbr-150 and scen1. Its running successfully. But not with mygpsr.tcl ? Again the same error Killed.
Then i compared and after a lot of tries , I found error is because of Trans range 250m, not because of memory problem.
I commented 40m line and uncommented 250 m line . It gives the same error with nn200-200wireless-gpsr.tcl.
Does anyone ever faced this kind of problem i.e. GPSR with transmission range 250 m.
Kindly tell me How i can overcome this problem.
Plz help...........
I am running wireless-gpsr.tcl with 150 nodes and transmission range as 250m and time 1000 . It does not run completely. After SORTING LISTS ... DONE! It shows the message Killed.
If i run with the same parameters but with less number of nodes , like i have tried for 90 nodes then it runs completely.
I also tried with higher number of nodes , then it shows the message Killed even earlier. Like for 150 nodes , It runs till 650 secs
For 175 nodes , it runs till 505 simulation time.
For 200 , it runs till 400 secs only...............
I also tried with same no of nodes like 175 with Trans range as 100 with the same simulation time. Its running completely fine.
Could someone ever faced this kind of problem. Plz help.......................
May be the above problem is due to memory ........ still it is not solved but after a lot of tries , i found that GPSR is running successfully for 100 nodes , 250 transmission range and 1000 simulation time.
But now when i am running my awk files on gpsr trace file (.tr) it is showing division by zero error and no output.
I want to calculate Throughput, Delay, PDR and overhead . I have the awk files and they are giving correct output for AODV, DSR and LAR , but no output in case of GPSR.
Kindly help
What is the format of GPSR trace file?
There is no format_gpsr function in cmu-trace.cc file.
How can i calculate the above mentioned metrics values for GPSR.
What happened ? Did i do something wrong.
Sorry if i did something wrong but plz help..........
I tried on my other laptop but here i am facing another problem.
I successfully patched GPSR is ns-2.32 but when i am running wireless-gpsr.tcl
trace file does not have any gpsr packets instead it has all undefined packets........
plz see
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.