You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Re conversation with Jason.
Count the number of messages being sent as if they were uni-cast messages as opposed to broadcast. (alternatively actually send them as uni-cast) this will allow the detection of dropped packets when a message is sent but all of the other nodes do not receive it. currently I have no way to know this.
given the current implementation mun sent != mun received because of the broadcasts
Since I am currently using a fixed range wifi model, I can get the nodes mobility model and find the number of nodes that are within the specified range. However this will not work for other communication models. A better approach will be to add a callback to the routing table and have the application maintain a list of all one hop nodes.
This has some other implications but it should work best.
The text was updated successfully, but these errors were encountered:
Re conversation with Jason.
Count the number of messages being sent as if they were uni-cast messages as opposed to broadcast. (alternatively actually send them as uni-cast) this will allow the detection of dropped packets when a message is sent but all of the other nodes do not receive it. currently I have no way to know this.
given the current implementation mun sent != mun received because of the broadcasts
Since I am currently using a fixed range wifi model, I can get the nodes mobility model and find the number of nodes that are within the specified range. However this will not work for other communication models. A better approach will be to add a callback to the routing table and have the application maintain a list of all one hop nodes.
This has some other implications but it should work best.
The text was updated successfully, but these errors were encountered: