Ad hoc device send packet requirement

136 views
Skip to first unread message

李若瑄

unread,
Mar 5, 2024, 9:45:43 AM3/5/24
to ns-3-users
Hello everyone,
I've run into a bit of trouble sending packets from A to B using ad hoc devices. As the email mentioned, 1) use the correct destination IP/Port, 2) a valid route 3) within the radio range can send the packet. However, it seems I've made a mistake somewhere along the line. Some nodes are unable to receive the packet, while others can without any issue.

I've already checked the relative distances using GetDistanceFrom() and examined the routing table with PrintRoutingTableAllAt(), but everything seems to be in order. I'm starting to wonder if I missed something or did something wrong.

In this image, node 3 and node 4 should be exchanging packets, but for some reason, they are not. Distance is in left part, routing table in the middle, and flow monitor in the right.
圖片2.png

The attached file contains my code. Any suggestions or information would be appreciated.

Best regards!

code.cc

Tommaso Pecorella

unread,
Mar 8, 2024, 6:04:49 PM3/8/24
to ns-3-users
Without the mobility trace I can't run exactly your script.

However, the routing table output is strange, and it looks like one I've seen in an old ns-3 version.
Mind checking if the problem persists with 3.41 or ns-3-dev ?

李若瑄

unread,
Mar 12, 2024, 2:43:24 AM3/12/24
to ns-3-...@googlegroups.com
Hi, Tommaso.

Thanks for answering my question. I updated the version from 3.38 to 3.41. Routing table looks great now! However, a new issue appears : no packets are being received at any of the nodes.
圖片2.png
The attached file is the missing tracing file and required data. Thank you for your support.

Tommaso Pecorella <tomm...@gmail.com> 於 2024年3月9日 週六 上午7:04寫道:
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/ns-3-users/53110698-17ab-48cd-a594-fadffb278972n%40googlegroups.com.
172nodes_data.txt
172vanetmobility.tcl

Tommaso Pecorella

unread,
Mar 12, 2024, 6:08:06 AM3/12/24
to ns-3-users
The nodes are too far away. We improved the models and now they're more strict on packet reception. Note that the actual one is the "correct" behavior, meaning that it more closely matches the one of real devices.

李若瑄

unread,
Mar 14, 2024, 10:47:49 PM3/14/24
to ns-3-...@googlegroups.com
Got it. Thanks a lot for taking the time to answer my question, I really appreciate it.

Best regards!

Tommaso Pecorella <tomm...@gmail.com> 於 2024年3月12日 週二 下午6:08寫道:

Vikram Dubey

unread,
Mar 17, 2024, 7:01:58 AM3/17/24
to ns-3-...@googlegroups.com
can anyone send me the code with awk script file of TCP Reno , NewReno And Tahoe.

Tommaso Pecorella

unread,
Mar 17, 2024, 7:29:33 AM3/17/24
to ns-3-users
@vikam: do not spam or you'll "accidentally" trigger our user ban system.
Read the posting guidelines and follow them.
I don't feel responsible, and I won't feel sad, if someone is banned from the group by our "bot".

Reply all
Reply to author
Forward
0 new messages