[IBR DTN] Notification about at the beginning of a bundle reception
Hello all,
I am using a scenario in which there are 2 nodes (node 1 and node 2) running the IBR DTN project. In this scenario, I have node 1 will send a bundle for node 2 at instant "t1". Suppose, that the bundle will be received by node 2 at instant "t1+Δt".
My question is, is it a way for the node 2 to know at an instant 't2' if it is receiving a bundle from a neighboring node (node 1 in this case)?
So in this scenario, I want to get these information :
1/ at t2 ∉ [t1,t1+Δt] ==> node 2 checks and discovers that it is not receiving bundles from neighboring nodes 2/ at t2 ∈ [t1,t1+Δt] ==> node 2 checks and discovers that it is receiving a bundle from neighboring nodes
Best Regards, Farouk
Hello,
I am not 100% sure I understand what you are trying to achieve. Times when Bundles are received/forwarded/sent can be seem from the daemons logfile if enabled. (start the daemon manually with dtnd -c /path/to/config -v to get a feeling, what kind of data can be expected). If it is about the application knowing, isn’t it easy for the application to perform some form of housekeeping, e.g. remembering when it received the last bundle from the daemon?
Sebastian
On 17 Apr 2015, at 15:38, Farouk Mezghani mezghani.f@gmail.com wrote:
Hello all,
I am using a scenario in which there are 2 nodes (node 1 and node 2) running the IBR DTN project. In this scenario, I have node 1 will send a bundle for node 2 at instant "t1". Suppose, that the bundle will be received by node 2 at instant "t1+Δt".
My question is, is it a way for the node 2 to know at an instant 't2' if it is receiving a bundle from a neighboring node (node 1 in this case)?
So in this scenario, I want to get these information :
1/ at t2 ∉ [t1,t1+Δt] ==> node 2 checks and discovers that it is not receiving bundles from neighboring nodes 2/ at t2 ∈ [t1,t1+Δt] ==> node 2 checks and discovers that it is receiving a bundle from neighboring nodes
Best Regards, Farouk
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to ibr-dtn-request@ibr.cs.tu-bs.de !! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.
@Sebastian : When a bundle is received, a BundleReceivedEvent is raised by the TCPConnection (if the two nodes communicate with TCP). Farouk wants to know when a bundle is being received. @Farouk : what do you want to do with this information ?
2015-04-18 13:04 GMT+02:00 Sebastian Schildt schildt@ibr.cs.tu-bs.de:
Hello,
I am not 100% sure I understand what you are trying to achieve. Times when Bundles are received/forwarded/sent can be seem from the daemons logfile if enabled. (start the daemon manually with dtnd -c /path/to/config -v to get a feeling, what kind of data can be expected). If it is about the application knowing, isn’t it easy for the application to perform some form of housekeeping, e.g. remembering when it received the last bundle from the daemon?
Sebastian
On 17 Apr 2015, at 15:38, Farouk Mezghani mezghani.f@gmail.com wrote:
Hello all,
I am using a scenario in which there are 2 nodes (node 1 and node 2)
running the IBR DTN project.
In this scenario, I have node 1 will send a bundle for node 2 at instant
"t1". Suppose, that the bundle will be received by node 2 at instant "t1+Δt".
My question is, is it a way for the node 2 to know at an instant 't2' if
it is receiving a bundle from a neighboring node (node 1 in this case)?
So in this scenario, I want to get these information :
1/ at t2 ∉ [t1,t1+Δt] ==> node 2 checks and discovers that it is not
receiving bundles from neighboring nodes
2/ at t2 ∈ [t1,t1+Δt] ==> node 2 checks and discovers that it is
receiving a bundle from neighboring nodes
Best Regards, Farouk
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or
adjust
!! your settings, send a mail message to <
ibr-dtn-request@ibr.cs.tu-bs.de>
!! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to ibr-dtn-request@ibr.cs.tu-bs.de !! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.
Hello Farouk,
the best way to achieve what you explained depends on your intention.
One way would be to start the daemon in debug mode with a level of at least 70 and watch out for "MSG_DATA_SEGMENT received". This indicates an ongoing transfer. It does not tell you if the bundle will be accepted by the daemon or if the data is being received by a TCP-CL or the API. If you plan to measure performance this way, you'll have to consider that debug output will slow down the overall performance of the daemon.
If you plan to implement some feature within the daemon, you could integrate some indicator within the function:
void BundleCore::validate(const dtn::data::PrimaryBlock &p)
This function is called on every bundle processed by the daemon as soon as the primary bundle header is available. Be aware that this is not only the case if a bundle is received by the API or a convergence-layer. This function is also called if a bundle is restored from a file within the storage.
I hope this information is useful for you.
Kind regards, Johannes
Am 18.04.2015 um 15:11 schrieb Mathias Brulatout:
@Sebastian : When a bundle is received, a BundleReceivedEvent is raised by the TCPConnection (if the two nodes communicate with TCP). Farouk wants to know when a bundle is being received. @Farouk : what do you want to do with this information ?
Hello all,
Thank you all for your answers.
My scenario only includes two nodes. The goal of this task is to select a forwarder from two nodes. That means, at an instant 't' only one node (node1 or node2) will send its bundles to its neighboring nodes.
To do that, I use timers 'T1' and 'T2' for node1 and node2, respectively. At the same time 't', both nodes initiate their timers. Suppose that T1 > T2, that means node1 should be the forwarder and node2 will be a receiver.
When T1 expires, node1 check if it is receiving bundles from neighbors ==> No, Then node1 sends its bundles for its neighbors. When T2 expires, node2 check if it is receiving bundles from neighbors ==> Yes, Then node2 does not send its bundles and act as receiver.
Best Regards, Farouk
On Sun, Apr 19, 2015 at 9:22 AM, Johannes Morgenroth < morgenroth@ibr.cs.tu-bs.de> wrote:
Hello Farouk,
the best way to achieve what you explained depends on your intention.
One way would be to start the daemon in debug mode with a level of at least 70 and watch out for "MSG_DATA_SEGMENT received". This indicates an ongoing transfer. It does not tell you if the bundle will be accepted by the daemon or if the data is being received by a TCP-CL or the API. If you plan to measure performance this way, you'll have to consider that debug output will slow down the overall performance of the daemon.
If you plan to implement some feature within the daemon, you could integrate some indicator within the function:
void BundleCore::validate(const dtn::data::PrimaryBlock &p)
This function is called on every bundle processed by the daemon as soon as the primary bundle header is available. Be aware that this is not only the case if a bundle is received by the API or a convergence-layer. This function is also called if a bundle is restored from a file within the storage.
I hope this information is useful for you.
Kind regards, Johannes
Am 18.04.2015 um 15:11 schrieb Mathias Brulatout:
@Sebastian : When a bundle is received, a BundleReceivedEvent is raised by the TCPConnection (if the two nodes communicate with TCP). Farouk wants to know when a bundle is being received. @Farouk : what do you want to do with this information ?
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to ibr-dtn-request@ibr.cs.tu-bs.de !! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.
Hello all,
Thank you all for your answers.
My scenario only includes two nodes. The goal of this task is to select a forwarder from two nodes. That means, at an instant 't' only one node (node1 or node2) will send its bundles to its neighboring nodes.
To do that, I use timers 'T1' and 'T2' for node1 and node2, respectively. At the same time 't', both nodes initiate their timers. Suppose that T1 > T2, that means node1 should be the forwarder and node2 will be a receiver.
When T1 expires, node1 check if it is receiving bundles from neighbors ==> No, Then node1 sends its bundles for its neighbors. When T2 expires, node2 check if it is receiving bundles from neighbors ==> Yes, Then node2 does not send its bundles and act as receiver.
Best Regards, Farouk
On Mon, Apr 20, 2015 at 1:22 PM, Farouk Mezghani mezghani.f@gmail.com wrote:
Hello all,
Thank you all for your answers.
My scenario only includes two nodes. The goal of this task is to select a forwarder from two nodes. That means, at an instant 't' only one node (node1 or node2) will send its bundles to its neighboring nodes.
To do that, I use timers 'T1' and 'T2' for node1 and node2, respectively. At the same time 't', both nodes initiate their timers. Suppose that T1 > T2, that means node1 should be the forwarder and node2 will be a receiver.
When T1 expires, node1 check if it is receiving bundles from neighbors ==> No, Then node1 sends its bundles for its neighbors. When T2 expires, node2 check if it is receiving bundles from neighbors ==> Yes, Then node2 does not send its bundles and act as receiver.
Best Regards, Farouk
On Sun, Apr 19, 2015 at 9:22 AM, Johannes Morgenroth < morgenroth@ibr.cs.tu-bs.de> wrote:
Hello Farouk,
the best way to achieve what you explained depends on your intention.
One way would be to start the daemon in debug mode with a level of at least 70 and watch out for "MSG_DATA_SEGMENT received". This indicates an ongoing transfer. It does not tell you if the bundle will be accepted by the daemon or if the data is being received by a TCP-CL or the API. If you plan to measure performance this way, you'll have to consider that debug output will slow down the overall performance of the daemon.
If you plan to implement some feature within the daemon, you could integrate some indicator within the function:
void BundleCore::validate(const dtn::data::PrimaryBlock &p)
This function is called on every bundle processed by the daemon as soon as the primary bundle header is available. Be aware that this is not only the case if a bundle is received by the API or a convergence-layer. This function is also called if a bundle is restored from a file within the storage.
I hope this information is useful for you.
Kind regards, Johannes
Am 18.04.2015 um 15:11 schrieb Mathias Brulatout:
@Sebastian : When a bundle is received, a BundleReceivedEvent is raised by the TCPConnection (if the two nodes communicate with TCP). Farouk wants to know when a bundle is being received. @Farouk : what do you want to do with this information ?
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to <ibr-dtn-request@ibr.cs.tu-bs.de
!! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.
participants (4)
-
Farouk Mezghani -
Johannes Morgenroth -
Mathias Brulatout -
Sebastian Schildt