Hi,
I have posted some questions for mesh protocol but this one, I keep it like a QA black box report coz I think I need help in adjusting sub-protocol settings(may be HWMP?...):
By default, it is placing nodes in a 3X3 grid and the horizontal&vertical distance between each node is 100 meters(Note: isn't 100m too long?)
- Default number of nodes(9)
I just added (ns-3.27) so that I can see some results:
LogComponentEnable ("UdpEchoClientApplication", LOG_LEVEL_INFO);
LogComponentEnable ("UdpEchoServerApplication", LOG_LEVEL_INFO);
~/Downloads/ns-allinone-3.27/ns-3.27 $ ./waf --run "src/mesh/examples/mesh" &> mesh_s100.log
The log says the packet loss is just too much. Visually I can see half of the packets never reached the destination. Is there any config issue other than step size(100 to change internally?)
Note:
- Tested with (ns-3.25) and the packet loss was 100%.
- Changed the distance from default(100) to 10 (--step=10) and things work satisfactorily.
- More nodes(50) and less distance(10)
run:
./waf --run "src/mesh/examples/mesh --step=10 --x-size=10 --y-size=5"
Took a tea break, came back, it was still in the first couple of seconds of the simulation, and 100% packet loss. Ctrl-C.
- Tried with 25 nodes and same lesser distance(10) , same, 100% packet loss. Ctrl-C.
- Tried with even lesser distance (./waf --run "src/mesh/examples/mesh --step=5 --x-size=5 --y-size=5"), same issue.
- Strange case!
- If previous case was slow, using default distance between nodes makes the simulation run fast! While the step ariable(distance) is used only in Grid's position allocator. Any hints?
- packet loss still 100%(not working).
I can see some attributes are default set in internal protocols like retry and timeout values in HWMP.
If someone please have a quick look at thecode and tells me me which attributes to touch, I can report back.
Thank you.
Vahid